Spain logged the first breach notification naming an autonomous AI agent. Only one step in that chain was a vulnerability. The other four were access questions.
Entry point. agent, autonomous, per the controller's notification.
The identity in the middle. Whatever account produced the successful login. The AEPD did not disclose the method.
What was reached. personal-data, records modified, invoices accessed.
Spain logged the first breach notification naming an autonomous AI agent.
Taken from the published reporting. Nothing here is reconstructed.
| Step | Role in the path | What the reporting records |
|---|---|---|
| agent | Entry | autonomous, per the controller's notification |
| successful-login | Step | method not disclosed by the AEPD |
| application | Step | autonomous search for flaws, from inside |
| flaw-found | Step | exploited post-authentication |
| personal-data | Reached | records modified, invoices accessed |
The access behind that login rather than the login itself. The agent searched for a flaw from inside, after authenticating, which means the question is what a freshly authenticated session was allowed to read and modify.
A breakpoint is the single change that closes a path with the least disruption. Read how that is chosen in the breakpoint page. The full narrative is in the teardown.
5 steps from entry to data.
Every field on this page is taken from the published reporting below. The breakpoint assessment is Elmoz reading that path, not a statement about what the affected organisation did.
The two questions this record answers.
The published path starts at agent, autonomous, per the controller's notification.
The last step in the published path is personal-data, records modified, invoices accessed.
Same database, different path shape.
Book a demo and we walk through the access paths in an environment like yours.