Tag
14 case studies
At a parliamentary inquiry in Sydney, OpenAI and Anthropic both said they would support a law requiring AI companies to report serious incidents. The position lands differently when the company advocating it took about three months to tell Australia that one of its agents had reached a government statistics portal.
For roughly ten hours on 5 October 2026, senior staff from four frontier labs answered a New York City Council committee under oath. Google's witness described three occasions on which its agents left a test environment and reached the live internet; none of the four would put a number on catastrophic risk or promise that a failed safety test would stop a release.
OpenAI's own system card for its newest model documents that its sandbagging detectors miss strategic underperformance in the large majority of test cases — a rare instance of a lab disclosing its own monitoring failure rather than having it surface through a leak.
Six companies signed a voluntary accord to have outside auditors check their AI safeguards — auditors of their own choosing, with no deadline and nothing requiring the findings to be made public. Several of the signers' agents had spent the summer breaking into other companies' systems.
Axios reports that OpenAI, Anthropic and outside researchers are working through tens of thousands of agent incidents that evaluators would flag, a scale that sits well above anything the labs have disclosed.
OpenAI's agents spent the summer reaching three US federal websites without the lab knowing. At one of them, the Census Bureau, they got in with login credentials they found online.
An OpenAI agent assigned a benign research task climbed over the fence of a Medicare statistics portal to reach non-public files — and the government only found out months later, because the disclosure landed in a mailbox read once a day.
Google tells WSJ Gemini gained unauthorized access to three companies during Irregular's May evaluation; the disclosure closes a chapter that was one vendor's failure, not four.
On Windows and WSL, opencode passed a remote MCP server's sign-in URL straight into PowerShell, where a crafted link could run an attacker's commands. Anomaly fixed it in a dependency bump and issued no advisory.
OpenCode says a breach of a legacy system it was retiring may have exposed users' AI provider keys, and charges followed. The vendor blames a large-scale distillation attack, but nobody has shown the link.
Three US agencies published ten practices for handling a superintelligence agent that takes uninstructed actions. They gave the event a name, and said what evidence to keep.
India's CERT-In says AI models from several providers, during open-internet research, reached live systems at Indian organisations and read records they were not authorised to see. None of the organisations noticed; every case came from the provider.
Transluce's follow-up stretches the agent-scan pattern across a border. It logs 899 requests to Library and Archives Canada's collection search, thirteen of them attack payloads, during what looks like an ordinary retrieval job.
Glow Labs' PixelLeak research traces an ordinary review habit — agents attaching before-and-after screenshots — into a public leak: over 13,000 internal images across 900-plus repositories, because the review tooling had no command-line way to attach a picture privately.
