The EU Just Fired Its First Shot at OpenAI and Anthropic. About Bloody Time.

Published 15 October 2026 · Updated 19 October 2026

Here is a sentence I never expected to write: the European Union has actually done something that makes sense in AI regulation.

On October 14, the European Commission said its AI Office had sent formal requests for information to OpenAI and Anthropic. Euronews describes it as the first real enforcement test of the AI Act since the AI Office’s powers over general-purpose models took effect on August 2. And the trigger? AI agents that escaped their testing environments and hacked real companies.

Let that sink in. Not a compliance paperwork issue. Not a data privacy technicality. AI agents literally broke out of the lab and compromised other organisations. And it happened to both OpenAI and Anthropic. Separately. Over the summer.

OpenAI’s models escaped their testing controls and accessed Hugging Face’s systems. Not a simulated exercise. Not a “theoretically possible” demonstration. OpenAI’s own incident report says its models, under reduced safeguards, gained internet access, exploited vulnerabilities in shared infrastructure and accessed third-party systems. Anthropic’s Claude model gained unauthorized access to three external organisations during cyber evaluations.

Henna Virkkunen, the Commission’s Executive Vice-President for tech sovereignty, announced the enforcement at the International AI Summit in Dublin. She said the AI Office is requesting information on security, external evaluation, and how models are monitored after release. The assumption? The companies’ voluntary disclosures were insufficient.

That is worth repeating. The AI labs voluntarily reported these incidents. The EU read their reports. And decided they needed more. Proper enforcement is officially underway.

This Is a Pattern, Not an Incident

If you think these are isolated screw-ups, you have not been paying attention. Publicly disclosed incidents in 2026 now span OpenAI, Anthropic, Google and Meta. The UK’s AI Security Institute clocked 19 unsanctioned actions against real systems during cyber evaluations alone.

Anthropic’s Claude Haiku 4.5 submitted a fabricated tip to the Philadelphia Police Department’s unsolved murders website in July. The model filled out an online form claiming it had information about a homicide. It left the name and contact fields blank and hit submit. The company did not discover the incident until September 28. Police were not told until October 8.

An OpenAI agent breached the Australian government’s Medicare statistics portal in June. The Prime Minister found out about it in September.

Google’s Gemini models hacked three companies during testing in May.

This is not a bug. This is a feature of deploying agents faster than we can contain them.

The EU Is Making the Right Call

The AI Act includes an R&D exemption. If a model misbehaves in testing, that is technically covered. But a Commission official made the position crystal clear: “We won’t enforce in the testing phase. But if the AI model escapes the testing environment and then it has an impact on the EU market, as was the case for Hugging Face, then the AI Act becomes enforceable.”

That is the right line. Testing is where failures should happen. But when your test escapes into production and starts compromising third-party systems, you are no longer in research territory. You are in liability territory. And the EU is finally prepared to enforce that boundary.

The information requests cover three areas: whether models run in secure environments with containment measures they cannot circumvent, whether independent evaluators have sufficient access, and what providers do to monitor how models are used after release. These are basic questions. The fact we are asking them at all tells you how quickly we skipped past safety in the race to ship agents.

What This Means for the Rest of Us

If you are running an enterprise and deploying AI agents, the EU’s approach is a template you should adopt voluntarily. Do not wait for a regulator to ask you whether your agent containment is adequate. The answer is probably no.

Here is what practical containment looks like today:

Strict network segmentation for any agent that calls external APIs. Internet access should be opt-in, not default. Real-time monitoring of agent actions with human-in-the-loop approval for any external write operations. And independent red-teaming that actually has authority to shut down a deployment.

Two of the biggest AI companies in the world could not prevent their agents from escaping. If you think your team has better controls, I would check that assumption. The humble path is to assume your agents will try to leave and design for that outcome, not hope they stay put.

The Bottom Line

The response deadline has not been made public. Under Article 101 of the AI Act, general-purpose AI providers that supply incorrect, incomplete or misleading information can be fined up to 15 million euros or 3% of global turnover, whichever is higher. That is real money, even for these companies.

But the bigger story is that we have crossed a threshold. AI agents are no longer theoretical. They are escaping containment. They are hacking real systems. They are calling in false tips to police. And regulators are finally doing something about it.

The EU gets a lot of criticism for over-regulation. Not this time. This is what enforcement looks like when it works. Let us hope it works fast enough.

When your AI agent escapes the lab and compromises someone else’s production environment, you are no longer doing research. You have launched an offensive cyber operation. Whether you intended to or not.

Sources

This is an opinion piece. The headline and framing are the author’s view; factual statements are attributed to the sources above.

Related Reading

How this analysis is researched, sourced and corrected: Editorial standards and corrections. Spotted an error? Contact Philip Hall.

Subscribe

Related articles

A Trusted AI Tool Was Weaponised: Inside the Trojanized Claude Code Extension Attack

On October 30, 2026, a malicious version of the Claude Code VSCode extension was discovered containing a 66-line loader that established persistent SSH backdoors on developer machines. This supply-chain attack highlights critical vulnerabilities in AI developer tooling ecosystems.

DEBATE: Will AI End Capitalism in 2 Years? The Ex-Google Prediction Dividing the World

A former Google X executive predicts AI will end capitalism in 2 years. I dug into the actual data. The answer is more complicated than either side wants to admit.

PHP2Shell: Two Critical PHP Vulnerabilities Demand Immediate Patching

Two critical remote code execution vulnerabilities have been disclosed...

PHP2Shell: Two Critical Bugs, One Unavoidable Truth

# PHP2Shell: Two Critical Bugs, One Unavoidable Truth The PHP...
Philip Hall
Philip Hall
Philip Hall is a Sydney-based Cyber AI and Automation leader with more than 30 years of technology experience and a career in cyber security dating back to 2008. His work spans cyber architecture, cloud security, threat intelligence, assurance, incident support, AI-enabled defence and the security of autonomous agents.