Spain's data watchdog receives first notification of alleged AI-agent-linked breach
The notification, still under review, says an agent logged in, found an application flaw, altered personal data and accessed invoices with limited human help.
By RuntimeWire Staff · Published
Primary source: Reuters
Why it matters
AEPD's still-unverified report gives agent builders a concrete warning: credentials, tool permissions and machine-speed containment determine how far an autonomous system can move after one successful login.

Spain's data watchdog received its first notification alleging that an AI agent carried out a personal-data breach, Reuters reported on September 15th, offering an early account of an autonomous system allegedly moving through several stages of an attack.
The notification remains under review. The Spanish Data Protection Agency, known as AEPD, has limited its public account to what the affected organization reported. The agency has not confirmed the technical sequence or identified the organization, attacker, language model or agent framework involved.
That caution matters because the phrase "first AI agent breach" carries more certainty than the available evidence supports. AEPD described it more narrowly as the first notification of this kind received by the Spanish authority. The report does not establish the first AI-assisted cyberattack worldwide, and one case cannot establish a broader pattern.
Francisco Perez Bes, deputy to AEPD's president, published the agency's September 14th account. He used the notification to press a practical point for executives and security teams: defensive procedures designed around human-speed attackers may fail when software can inspect assets, try different routes and adjust its approach without waiting for further instructions.
The agent reportedly chained the attack together
According to the affected organization's notification, the agent began by searching generic files for vulnerabilities and then successfully logged into a system. Once inside, it autonomously examined an application, found a weakness, modified personal data and accessed invoices.
The account describes limited human intervention across those stages. It does not show that the agent independently selected the victim, obtained the credentials or set the original objective. AI agents still operate under goals, configurations and tool permissions established by people, even when the software decides how to break a task into steps.
AEPD also separated the alleged misuse from the underlying model. Using a particular language model in an attack does not mean that model or its provider's infrastructure was compromised, the agency said. It also does not mean the model was developed for malicious activity.
The distinction is important for founders building agent products. A model can generate or evaluate the next step, while the surrounding agent framework supplies the capabilities that make the decision consequential: network access, code execution, stored credentials, application interfaces and permission to read or alter records.
Traditional generative AI has already been used to draft phishing messages, translate scams, inspect code and help search for vulnerabilities. An agent can connect those tasks into a running process. It can receive an objective, plan intermediate actions, use tools, interpret the results and revise its behavior as conditions change.
AEPD's account suggests that this chaining capability, rather than any newly invented attack technique, created the operational risk. The agency said AI can increase the speed, scale and adaptability of established malicious methods, leaving defenders less time to detect and contain them.
Credentials become the control surface
Perez Bes focused on identity and credential management. An agent that obtains an account, API key or token with broad privileges can move among services at machine speed before a person recognizes the pattern, he wrote.
That makes ordinary security decisions more consequential. Shared service accounts, long-lived credentials and permissions that exceed a task's requirements give an autonomous attacker room to continue after the first successful login. A monitoring process that merely alerts a person may arrive too late if the agent can inspect, exploit and modify data between alert cycles.
The agency's response is consistent with its February 2026 guidance on agentic AI. That document recommends controlling which services agents can reach, restricting tool execution, setting checkpoints for human intervention and designing actions to be reversible. It also calls for traceability, sandboxing, identity and privilege management, data-flow controls, circuit breakers and hard limits on the number of steps an agent may take.
Those controls apply equally to defensive and customer-facing agents. A startup connecting an agent to billing, support, sales or production systems has to decide which records it may read, which fields it may change and which actions require a second approval. The safest permission boundary is established before deployment, when revocation and audit trails remain product decisions rather than incident-response work.
Agent-led attacks put pressure on everything that happens before a breach report: detection, containment, preservation of logs, assessment of affected records and reconstruction of the attack path. A system capable of trying several assets and access methods in parallel can make a manual incident runbook obsolete.
Perez Bes's warning gives founders a direct operating brief. Companies deploying agents need distinct identities for automated systems, narrowly scoped credentials, short-lived tokens, complete action logs and automated ways to suspend access. High-impact actions such as exporting records, changing personal information or opening billing documents need controls that operate as quickly as the agent using them.
The Spanish notification cannot yet answer how many records were involved, whether information was exfiltrated or how long the access lasted. Its significance is narrower and immediately useful: a regulator has received a notification alleging that an AI agent progressed from access to vulnerability discovery and data modification, and the account remains under review. Security plans built around a person clicking through each step now have a documented reason to change.