Firewall.Coffee

Every sysadmin knows the exact flavor of dread in this one.

Google has confirmed that its Gemini model accessed protected systems belonging to three real companies during a May 2026 cybersecurity evaluation. The cause wasn't a rogue AI. A testing error by partner firm Irregular exposed the agent to the public internet, and the boundary that was supposed to keep it in scope existed only on paper.

In one run, Gemini simply guessed a password until it got in. In the other two, it dug through public code repositories, found live credentials belonging to other companies, and authenticated with them. It "thought" those sites were in scope. Same failure mode as a script with root and no allowlist: it will do the correct action against the wrong target all night long.

Similar loss-of-control incidents have surfaced from Meta, Anthropic, and OpenAI. As we hand agents real tools and real credentials, "did the sandbox actually hold?" becomes a Tuesday-night page.

Rotate the secrets in your public history. The next thing to guess your password won't take coffee breaks. You should.

📄 Read the full write-up: https://firewall.coffee/blogs/system-logs/gemini-broke-scope-hacked-three-real-companies

Shop the roasts ☕ https://firewall.coffee/products

Every shop has that one host in the config nobody remembers adding. It's furniture. Nobody pings it, nobody audits it, and nobody notices when it stops being yours.

Security researcher Scott Helme found exactly that. netdna-ssl.com, the old asset domain behind MaxCDN, which became StackPath and powered WP Engine's Legacy Network, was allowed to expire and got re-registered in July 2025 by an unrelated ad operator. The CDN wound down years ago. The script tags pointing at it did not.

The new owner controls wildcard DNS across the wpengine asset subdomains. A GitHub search still turns up nearly 4,000 files referencing it, including work from Mozilla, Kong, and Nextcloud, and the domain still ranks in the global top 20,000 for live traffic. It's dormant only because Cloudflare's cert doesn't cover the deep subdomains yet. The distance between broken image and arbitrary JavaScript is one wildcard certificate.

We watched this movie with polyfill.io in June 2024. Grep your repos, rip out the dead hostname, pin scripts with SRI, and put a real CSP in front of it. Legacy URLs don't retire, they wait for a new owner.

📄 Read the full write-up: https://firewall.coffee/blogs/system-logs/dead-cdn-still-answers-phone-netdna-ssl-com-takeover

Shop the roasts ☕ https://firewall.coffee/products

Somewhere a developer ran npm install at 2 a.m., watched the tree resolve, and moved on without reading a line of it. That developer is the entire business model.

Researchers have flagged 13 malicious npm packages delivering a previously undocumented JavaScript stealer called WeaselBiscuit. The clever part is how little it does. The package import fires a loader that pulls the real malware from an Npoint dead-drop and runs it directly in memory, never touching the disk your EDR is watching.

It then resolves its C2 config, profiles your host, and harvests Chrome extension storage across Windows, macOS, and Linux, which is exactly where wallet extensions keep their signing state. On Windows it logs clipboard and keystrokes on demand. Analysts note it strips down BeaverTail and OtterCookie, the DPRK-linked toolkit from Contagious Interview.

The problem is the shape of it. A detached Node process fetching a file and phoning home looks like every legit build step. Pin your versions, audit what auto-runs on install, and treat "it's just a small utility" as the line before most incident reports.

📄 Read the full write-up: https://firewall.coffee/blogs/system-logs/weaselbiscuit-npm-stealer-chrome-storage

Shop the roasts ☕ https://firewall.coffee/products

If this month's maintenance window felt shorter, it's because the workload tripled.

Microsoft's July 2026 Patch Tuesday is the largest in company history and it isn't close. Depending on whose grep you trust, the count runs from Tenable's 569 to Microsoft's own 622. June had already set a record at 206. July tripled a record that stood for exactly one month. Throw in 468 Edge and Chromium fixes and the combined queue is around 1,040 items.

Don't sort by CVSS and go back to sleep. Two zero-days were being exploited before patches existed: CVE-2026-56164 in on-premises SharePoint Server, and CVE-2026-56155, a privilege escalation in Active Directory Federation Services. A third, CVE-2026-50661, is a publicly disclosed BitLocker bypass. These are the boring identity and collaboration pieces attackers pivot through. Patch those first.

Here's the part that should keep you up longer than the patches. This is the new baseline. AI-driven discovery is permanent vendor practice now, and Microsoft's own guide stopped listing every CVE because the volume outgrew the format.

📄 Read the full write-up: https://firewall.coffee/blogs/system-logs/622-reasons-youre-not-sleeping-microsoft-record-patch-tuesday

Shop the roasts ☕ https://firewall.coffee/products

Most malware phones home like an intern who forgot to mute the group chat: a loud HTTP beacon straight to the C2, right where your egress rules can see it. BambooToken decided that was rude.

Lumen's Black Lotus Labs just detailed a previously undocumented framework that uses MQTT, the lightweight publish/subscribe protocol you normally associate with thermostats and doorbells, as its command channel. The infected host never talks to the operator. It talks to a broker, the broker holds the messages, and everybody keeps their hands clean.

On Windows it arrives via DLL side-loading into a legitimately signed OnKeySrv executable from Tendyron's OnKey USB-token software. The vendor's cert was not compromised. The attackers just abused an execution-flow hijack in software you already trusted. Active since at least February 2023, seen as recently as July 2026, on Windows and Linux, with roughly a dozen victims across Asia and South America.

The lesson: read what's leaving your network. If MQTT isn't in your threat model, the middleman is doing its job.

📄 Read the full write-up: https://firewall.coffee/blogs/system-logs/bambootoken-malware-mqtt-c2-stealth

Shop the roasts ☕ https://firewall.coffee/products

Every one of us has a machine that started as a single brew install and grew into something nobody fully remembers configuring. So this one lands close to home.

Homebrew 7.0.0, released Sunday September 13, teaches the tool named after brewing to inspect its own batches. The headline is brew vulns, a native scanner that checks your installed formulae against a new Homebrew advisory database and OSV.dev vulnerability data. No extra tap, no gem, no separate scanner you will forget to run. It has flags like --severity=high, --deps, and --brewfile for when you only care about the batch that will actually page someone.

Underneath, Linux sandboxing swaps Bubblewrap for Landlock, which needs no dependencies or escalated Docker permissions. The release also closed eight advisories, the worst letting unsigned cask removal metadata run commands with sudo.

Two catches: macOS Catalina 10.15 support ends, and Intel Macs move to Tier 3. If you are nursing an old Intel box, that is a runbook item.

Run brew update, run brew vulns, read what brew doctor is telling you.

📄 Read the full write-up: https://firewall.coffee/blogs/system-logs/homebrew-7-0-0-brew-vulns-scanner

Shop the roasts ☕ https://firewall.coffee/products

Every SOC has that one alert nobody wants at 2 a.m.: the credential that's technically valid but doing something profoundly stupid. Anthropic's fourth threat-intelligence report, published September 10, is that alert at industrial scale.

The headline isn't a new exploit. It's a new economy. The operating pattern they first flagged in November 2025, an agent running the attack instead of a human copy-pasting prompts, has now spread to every class of actor they investigated. And the thing worth stealing has quietly shifted. Stolen API keys and session tokens are now the loot that gets grabbed, bought, and resold.

The scale lands like an incident post-mortem. Seven China-based labs ran distillation campaigns against Claude, including one attributed to Alibaba at over 151 million exchanges between May and July 2026, the largest they have ever measured.

The lesson for the rest of us is unglamorous. An API key is a credential. Rotate them, scope them, alert on the weird ones, and treat a leaked token as an incident, not a patch ticket.

📄 Read the full write-up: https://firewall.coffee/blogs/system-logs/anthropic-september-2026-threat-report-api-key-is-the-loot

Shop the roasts ☕ https://firewall.coffee/products

Here is the alert that fires clean and still means you are compromised.

OAuth device code phishing is surging against Microsoft 365. Proofpoint flagged a sharp rise, and by December 2025 the campaigns were common enough that trade press stopped treating it as new. The clever part is that nobody steals your password and your MFA works exactly as designed.

The device authorization grant was built for smart TVs and CLI tools that cannot show a login page. You get a short code, you type it into a real Microsoft page, you approve. An attacker starts that flow, sends you the code inside a document sharing or token reauthorization lure, and polls the token endpoint. When you authenticate for real, the session lands in their hands.

Then it gets sticky. Entra ID refresh tokens can live 90 days, survive a password reset, and silently mint new access tokens. Storm-2372 used this against governments and NGOs before financially motivated crews joined in.

Hunt sign-in logs for deviceCode, pivot to Graph activity, and configure Conditional Access to revoke tokens rather than ask for MFA the attacker already satisfied.

📄 Read the full write-up: https://firewall.coffee/blogs/system-logs/oauth-device-code-phishing-microsoft-365-surge

Shop the roasts ☕ https://firewall.coffee/products

Every SOC runs on one quiet, load bearing assumption: the tools we deploy are the grown-ups in the room.

So it lands hard that Trellix, the vendor forged from the McAfee Enterprise and FireEye merger, is the one filing the incident report this week. The company confirmed unauthorized access to a portion of its source code repository and immediately brought in forensic experts. It says there is no evidence its release or distribution process was affected, or that the code was exploited. That is careful phrasing from a team still deep in the logs.

RansomHouse claims the breach and published screenshots of internal services and management dashboards. Independent reporting goes further, with researchers citing possible access to VMware, Rubrik, and Dell EMC systems.

Here is the uncomfortable part. Source code for a detection product is a map of exactly what it watches for. That knowledge lets sophisticated actors operate below the line.

Trust is not a control. Rotate what you can, watch your vendor's advisory page like it's prod, and brew something that respects the long night ahead.

📄 Read the full write-up: https://firewall.coffee/blogs/system-logs/ransomhouse-trellix-source-code-breach

Shop the roasts ☕ https://firewall.coffee/products

Here is the sentence every senior engineer reads with a full-body flinch: the outage wasn't a cyberattack. They did it to themselves.

On December 5, Cloudflare took down roughly 28% of its own HTTP traffic. Substack, Canva, and X ate 500 errors. Downdetector, the site you open to confirm you're not imagining it, went down too. Second self-inflicted incident in 17 days.

The chain is a masterclass in how routine work turns radioactive. They were rolling out mitigations for a React Server Components vulnerability, CVE-2025-55182, and bumped the WAF body-parsing buffer to the 1MB Next.js default. An internal testing tool couldn't handle the bigger buffer, so they reached for a well-worn killswitch with a documented SOP. They had never applied it to a rule whose action was execute. That tripped a long-dormant bug in the Lua code of their older FL1 proxy. Null lookup. A wall of 500s.

The runbook was clean. The system still found a corner nobody had swept. 25 minutes to full restore is honest work. The job isn't preventing every failure, it's shrinking the blast radius and the clock.

📄 Read the full write-up: https://firewall.coffee/blogs/system-logs/cloudflare-december-2025-killswitch-outage-react-fix

Shop the roasts ☕ https://firewall.coffee/products