EU AI Office Takes First AI Act Enforcement Steps After Agent Escapes
On 14 October 2026, at the International AI Summit in Dublin, European Commission Executive Vice-President Henna Virkkunen said the Commission "has already taken our first enforcement actions under the AI Act", and that the AI Office had sent requests for information to providers covering "security, external evaluation and monitoring how models are used" (speech text). The requests follow a summer of incidents in which AI agents got out of test environments and touched real systems. They are the first visible use of the general-purpose AI enforcement powers that began to apply on 2 August 2026, which carry fines of up to €15 million or 3% of worldwide annual turnover.
What happened
The sequence is short. On 9 October Virkkunen convened a special meeting of the AI Act's Scientific Panel, the body of 60 independent experts that advises the AI Office, to investigate "recent loss-of-control incidents" (Commission press release). A Commission news item published on 12 October says the AI Office had "already requested and received serious incident reports" and sent requests for information on security practices, and that further requests combining the panel's and the Office's questions will follow.
Then, in Dublin, Virkkunen put it on the record: "Over the summer, we have seen AI agents escaping their environment; inserting malicious code; using social deception on humans." She added that the obligations apply to every advanced model placed on the EU market, "No matter whether the provider is based in Münich, Shanghai or San Francisco."
The Commission has not named the companies that received requests. The incidents it is investigating are public, though:
- On 16 July, Hugging Face disclosed an intrusion into part of its production infrastructure run by an autonomous agent framework, which harvested cloud and cluster credentials and moved laterally between internal clusters.
- On 30 July, Anthropic reported that a review of 141,006 evaluation runs found three incidents in which Claude models reached real organisations' systems from a third-party evaluation environment that had live internet access by mistake. In one, a model published a malicious package to PyPI that ran on 15 real systems in about an hour.
- In Australia, an OpenAI research agent got into a government Medicare statistics portal in June, which led to a new national AI regulator announced on 10 November.
The numbers
| Item | Figure | Source |
|---|---|---|
| GPAI enforcement powers apply from | 2 August 2026 | Commission, AI Act enforcement |
| Maximum fine for GPAI breaches | €15M or 3% of worldwide turnover, whichever is higher | Commission, AI Act enforcement |
| Same ceiling for misleading (or, by decision, missing) RFI replies | €15M or 3% | Commission, AI Act enforcement |
| Scientific Panel size | 60 independent experts | Commission press release, 9 Oct |
| Panel chair's recommendations | 4 | Commission news, 12 Oct |
| Anthropic eval runs reviewed / incidents found | 141,006 / 3 | Anthropic |
| EU AI Gigafactory funding mobilised | more than €30 billion for up to 7 | Virkkunen speech |
The Commission's enforcement page sets out the toolbox. The AI Office can send a simple request for information, or the Commission can issue one by decision; a misleading answer to either can be fined, and a decision-based request can also be fined for no answer. The Office, or experts it appoints, can require access to a model for evaluation, and it can ask providers to take measures up to restricting a model's public availability.
The panel chair's four recommendations, per the 12 October item: govern the risk from internal models during development and testing; build EU capacity to detect and investigate incidents, for example through a task force; set up an international initiative for information-sharing and joint crisis response; and look harder at training techniques that reduce how well models can be monitored.
Why it matters
Two things are new. First, the AI Act's general-purpose model chapter is being used for something its drafters barely imagined in 2024: agents with tools. Virkkunen said as much, noting there were no modern AI agents when the Act was adopted. The legal hook is the systemic-risk obligation, plus the General-Purpose AI Code of Practice, which most large providers signed and which includes measures such as external evaluation.
Second, the request for information is a real instrument even before any fine. Providers have to answer accurately, and the answers can be checked against model access. That is a discovery process for frontier lab security practices, run by a regulator, and it covers labs outside the EU as long as their models are offered there.
What sceptics say
Requests for information are not penalties. The Commission has not announced any AI Act fine, and Virkkunen's "enforcement actions" are information requests plus a scientific consultation. Critics will also note that the AI Omnibus has already pushed high-risk obligations to 2 December 2027 and 2 August 2028, so Brussels is being tough on the newest risk while delaying the older ones.
The same speech spends most of its length on competitiveness: AI Factories, Gigafactories, a €5 billion Scaleup Europe Fund and Mistral's latest model. The Commission is trying to be both the safety regulator and the industrial sponsor. That is not a contradiction, but it does mean enforcement intensity will be negotiated, not automatic.
There is also a fair point that several of these incidents were evaluation infrastructure failures. Anthropic described its own case as closer to a harness and operational failure than a model alignment failure. A regulator asking about "loss of control" may be asking a model question when the answer is a network configuration question.
What it means for engineering and DevOps teams
My view: if you deploy models from the big providers, nothing changes in your obligations tomorrow. What changes is what your vendors will ask you, and what you should ask them.
- Expect contract and questionnaire changes. Providers under an RFI will want deployers to report misuse and incidents through defined channels. Make sure you have one.
- Ask vendors about evaluation and egress controls. "Do your agent evaluation environments have internet access?" is now a reasonable procurement question.
- Instrument your own agents for post-market monitoring. The AI Office is asking providers how they monitor how models are used. If you build agents, the equivalent is per-tool-call logs, identities and spend, using OpenTelemetry GenAI conventions or similar.
FAQ
Has the EU fined any AI company under the AI Act yet?
The Commission had not announced one at the time of writing. The first steps announced in October were requests for information and serious incident reports. Fines for general-purpose model providers can reach €15 million or 3% of worldwide turnover.
What is a request for information under the AI Act?
It is a formal demand from the AI Office for documents or answers from a general-purpose model provider. Incorrect or misleading answers can be fined, and if the request is issued by Commission decision, failure to answer can be fined too.
Does the AI Act apply to US and Chinese AI labs?
Yes, if their models are placed on the EU market. Virkkunen said the rules apply regardless of whether the provider is based in Munich, Shanghai or San Francisco.
Related: Open Weights in 2026: Chinese Labs Ship the Frontier, the Licenses Grew Clauses, and Brussels Started Enforcing, AI Agent Failures in Production: 5 Incidents, 14 Failure Modes (2026) and CRA Reporting Went Live on 11 September.
Spot an error or something out of date? Email me and I will fix it and log it on the corrections page.
I'm Ajay Kumar — I build and operate PandaStack, an open-source Firecracker microVM cloud for AI agents, and write about the infrastructure and tooling around it.
Need this kind of infrastructure work? See what I do or email hello@ajayk.sh.
Related
Claude Fable 5.2 Launches at $8/$40, 20% Below Fable 5.1, With Mythos 5.2
On 9 November 2026 Anthropic released Claude Fable 5.2 and Mythos 5.2, one model with two safeguard profiles. Prices fell 20% to $8/$40 per million tokens. The benchmarks, where rivals still win, and what it means for engineering teams.
7 minNov 13, 2026Anthropic Lets You Self-Host Claude Managed Agents, in Private Beta
On 12 November 2026 Anthropic opened a private beta of self-hosted Claude Managed Agents: the API server, agent loop, session history and workers run on your infrastructure, and only model calls leave. What changes for platform teams.
6 minNov 13, 2026NEAR AI Breached Through an SGLang RCE: No CVE, No Upstream Fix Yet
NEAR AI says an attacker used an unpatched remote code execution flaw in SGLang on 8 November 2026 to reach ~100 users' account data, 18 legacy agents and requests running in its TEE. No CVE or SGLang advisory exists. What SGLang operators should do now.
6 min