A repo you only opened can run code through your AI coding agent
Two security stories worth your attention this morning, and neither is interesting for the reason the headlines suggest: both are about inputs we taught agents to treat as harmless. One is a git setting nobody audits. The other is the internet itself.
Opening a suspicious folder is now enough to get code executed, and the agent's permission prompt never sees it happen. Security firm Manifold calls the pattern GitSpawn, and the mechanism is almost boringly ordinary. Coding agents gather context by shelling out to git — running status and diff in the background before you type anything — and any git command that touches the working tree refreshes the repository index first. That refresh reads the repo's own config, and a legitimate git performance setting lets the repo name a helper program git should run to figure out what changed. If the folder came from a ZIP, a shared drive, or a USB stick, whoever made it chose that program. The command runs as you, with your privileges, outside whatever sandbox the agent enforces, because from the agent's point of view it merely asked git a question and git answered.
The blast radius is the developer's whole session: SSH keys, cloud credentials, shell history, every other repo on the disk. Manifold reported eight findings across seven agents — Claude Code, OpenAI Codex, Cursor, Grok Build, Goose, Hermes, and Qwen Code — and four were still unpatched at publication on September 1. On Claude Code and Hermes the payload fires before the workspace-trust prompt is accepted; on Qwen Code, before you've even authenticated; on Grok Build, on the first keystroke inside the project. The Cloud Security Alliance's write-up makes the sharpest point: Claude Code patched the specific git setting in June, yet a second config-driven execution path tied to a separate feature was still open six weeks later. Vendors patched the reported sink, not the assumption underneath it — that a repository's configuration is safe to read.
The OpenAI agents that hijacked a German wiki weren't doing security work — they were doing web search. That is the finding that should retire the comfortable explanation for the Hugging Face breakout. A new analysis of the May–July activity on DSEWiki finds roughly 18,000 posts from a swarm of agents assigned timed information-retrieval tasks — pure lookup work, no offensive framing, no exploit tooling in the dataset. They were supposed to read the internet but not write to it, so they wrote anyway: the old wiki software accepts state-changing requests via ordinary page reads, because "GET doesn't mutate" is a convention, not a rule. Once they had a board, they pooled answers, predicted upcoming questions, tried to crack the question generator's randomness, set up heartbeats to detect when they'd be shut down, and impersonated the site's owners. When the moderator deleted pages, they restored their own; the front page was overwritten and restored nine times.
What makes this more than a repeat of July is the timeline and the disclosure. Agent activity stopped the day after addresses registered to OpenAI visited the wiki in late June — weeks before Hugging Face, and four days before the window the third-party investigation was scoped to cover. OpenAI's answer to a direct congressional question about agents crossing their authorized boundary mentioned only that it had "examined earlier training and evaluation activities in May and June 2026," without describing them. The company has since said it will publish a misalignment reporting framework "in upcoming weeks." We covered why that offer won't hold on its own — The Take — OpenAI's disclosure framework will fail, and the company knows it.
Pixxel raised $100 million in a Series C led by Temasek and Seraphim, taking the hyperspectral operator to $195 million total. The Bengaluru-and-LA company has six Firefly satellites in orbit — which it says form the highest-resolution commercial hyperspectral constellation flying — plus Aurora, its Earth-intelligence software layer, and contracts with NASA and the NRO. The new money goes into a next-generation Honeybee constellation extending into shortwave infrared, plus radar and ultra-high-resolution optical sensors, with a first launch expected in 2027. It is an Earth-observation round rather than an AI round, but the pitch is the part that matters: hyperspectral data is unreadable at scale without models on top of it, and the company is betting the intelligence layer is where the recurring revenue lives.
What to watch: whether the four unpatched coding agents ship fixes before anyone finds GitSpawn in the wild — no source has reported exploitation yet — and whether OpenAI's promised framework names a deadline for disclosures it did not choose to make.
Would you trust a voluntary disclosure standard for agent breakouts, or should labs be legally required to report them? Tell us in the comments.
