A perfect headline — with one problem

“The first autonomous AI hacker.”

It would be a perfect headline.

It would simply be far more definitive than the facts currently known.

Spain’s data protection authority, the AEPD, has reported for the first time on a notification of a data breach in which the attack was allegedly carried out with the help of an AI agent. [1]

The authority is investigating the matter.

That sentence is crucial.

At present, we are talking about a reported incident, not a fully publicly documented forensic investigation.

What the agent is said to have done

According to the affected organisation, a third party used an AI agent based on a large language model.

The agent is said to have gained access to a system.

It then allegedly searched independently for vulnerabilities in an application.

One such vulnerability is said to have been found and exploited.

Subsequently, personal data were altered and invoice information was viewed. [1][2]

The authority describes several stages of the attack with limited human intervention.

The affected company and the specific language model were not publicly named.

And that is precisely why the headline “AI independently hacks company for the first time” would be premature.

There are crucial things we still do not know

We do not yet know the full technical attack chain.

We do not know what instructions the human gave the agent.

We do not know which tools had already been provided to it.

We do not know which access rights were in place.

And we do not know whether, and at what points, people intervened during the attack.

That is not a minor detail.

There is a fundamental difference between a system that decides of its own accord to attack a company and a system that largely automates an attack specified by a human.

Autonomy is not initiative

An autonomous AI agent does not have to suddenly think:

“Today I’m going to attack a company.”

Autonomy can mean that a human specifies an overarching goal and the software then independently plans the intermediate steps.

The human determines the goal.

The machine increasingly decides how to get there.

That is already a major change.

And it is probably this change that matters more than the question of whether we are allowed to use the term “autonomous hacker.”

Cyberattacks have so far also been a question of human working time

An attacker normally has to conduct research.

Examine systems.

Test vulnerabilities.

Combine information.

Adapt scripts.

Analyse failed attempts.

Plan the next step.

This work takes time.

AI agents can automate part of it.

That does not necessarily create entirely new attack techniques.

But speed, scalability and adaptability may increase. [1][3]

And that could change the economics of cybercrime.

What happens when an attack suddenly becomes cheaper?

Today, a complex manual attack is not worthwhile against every target.

The effort has to be reasonably proportionate to the expected gain.

But if an AI system can automate research, vulnerability discovery and parts of the attack chain, the cost per target may fall.

That would make smaller organisations more attractive as well.

Not because their data have suddenly become more valuable.

But because the attack becomes cheaper.

A human could theoretically no longer examine just ten systems carefully.

They could have thousands of systems analysed automatically.

That would be a considerable scaling effect.

This is exactly what we build AI agents for

The irony is obvious.

A good AI agent is supposed to work independently.

It is supposed to recognise obstacles.

It is supposed to find alternative solutions.

It is supposed to use tools.

It is supposed to break complex tasks down into subtasks.

It is supposed to adapt its plan when something does not work.

All of these capabilities are valuable in legitimate use.

In an abusive context, the same capabilities become problematic.

The security problem therefore does not lie solely in the language model.

It lies in the overall system of:

model,

tools,

access,

identities,

permissions,

data,

and control mechanisms.

The second danger: the legitimate agent itself is manipulated

There is another side to this.

People can deliberately use AI agents for attacks.

At the same time, attackers can attempt to manipulate legitimate AI agents.

One example is indirect prompt injection.

An agent is tasked with evaluating a website, email or file.

That content contains hidden or cleverly worded instructions.

The agent may interpret them as part of its task and carry out actions its actual user never intended. [3]

The more permissions the agent has, the greater the potential damage.

An assistant does not need master keys

This gives an old security principle renewed importance:

the principle of least privilege.

A system should have only the rights it actually needs for its specific task.

A scheduling assistant that is meant to read your calendar, for example, does not automatically need access to all emails.

A research agent does not necessarily need to be able to delete files.

A coding agent should not automatically be allowed to modify a production server.

The more capable an agent becomes, the more dangerous blanket authority becomes.

Who is responsible when the agent chooses an unauthorised path?

The legal dimension also becomes more complicated.

Suppose a human gives an agent a goal.

The agent independently decides on several intermediate steps and, in doing so, chooses an unauthorised method.

Who bears responsibility?

Technical autonomy does not automatically mean legal independence.

An AI does not become an independent perpetrator simply because it plans work steps on its own.

For companies and developers, however, this means that agents’ actions must be traceable.

We need logs.

Clear identities.

Limited rights.

Approvals for particularly sensitive actions.

And ways to stop an agent reliably.

Perhaps the future of cyberattacks will look alarmingly unspectacular

We like to imagine the AI hacker in dramatic terms.

A digital intelligence independently deciding whom to attack.

Reality may be far more mundane.

A human enters a target.

The agent works.

It researches.

It tests.

It adapts its strategy.

It repeats.

And at some point reports:

Task completed.

No rebellious machine.

No consciousness.

No science fiction.

Just automation.

And that is precisely why the Spanish case is so interesting.

Not because it would already prove that artificial intelligence has become independently criminal.

But because it shows how quickly the boundary between AI as a tool and AI as an acting component within a complex workflow is shifting.

That may change cybersecurity more profoundly than any spectacular hacker headline.

RECHERCHE

Sources

  1. [1]
    Agencia Española de Protección de Datos – AEPD (2026): Meldung über eine Datenschutzverletzung, bei der ein Angriff mutmaßlich mithilfe eines KI-Agenten durchgeführt wurde. Spanische Datenschutzbehörde.
    ↑ BACK TO FIRST REFERENCE
  2. [2]
    Reuters (2026): Spanish data watchdog publicises first AI agent-linked data breach report. Bericht über den gemeldeten spanischen Fall und den noch laufenden Prüfungsstatus.
    ↑ BACK TO FIRST REFERENCE
  3. [3]
    National Institute of Standards and Technology – NIST (2026): Sicherheitsanalysen zu KI-Agenten, Agent Hijacking, indirekter Prompt-Injection, Identität und Autorisierung. INSTAGRAM CAPTION: Ein KI-Agent soll in Spanien weitgehend selbstständig mehrere Schritte eines Cyberangriffs durchgeführt haben. Hat KI damit erstmals eigenständig „gehackt“? Noch wissen wir dafür zu wenig. Aber der Fall zeigt etwas anderes: Cyberangriffe könnten zunehmend automatisiert, schneller und billiger werden. Und genau das könnte wesentlich größere Folgen haben.
    ↑ BACK TO FIRST REFERENCE