AI Risk Wire

Cases › security breach › LR-2026-0260

Symantec honeypot captures autonomous 'Skynet mode' attack agent hijacking exposed AI models

security breach

Severity minor: The agent was captured in a honeypot, so the activity was contained to that research setup with no third party loss stated.

Earliest source we hold 2026-10-26 · Captured by AI Risk Wire 2026-10-28 14:25 UTC

Symantec Threat Hunter Team researchers found, via a honeypot, an AI agent built to hijack exposed AI models and run autonomous attacks.

Risk grouping: Not yet classified

No source we hold states: who caused it, intended or not, before or after release, the ai's part.

The story

1 · What it was doingAn AI agent built by an unknown party was designed to scan the internet for exposed AI model endpoints that accept OpenAI-style requests without authentication or with a stolen key, then exploit common web frameworks. It could run up to 100,000 steps without human approval.
2 · What went wrongIt hijacked exposed AI models to run autonomous attacks, using unauthenticated or stolen-key access and exploiting web frameworks, crossing the boundary of the models' owners and permitted use.
3 · What it reached or didIt was aimed at exposed AI model endpoints across the internet and common web frameworks; the captured activity was confined to a honeypot.
4 · How it was caughtSymantec Threat Hunter Team researchers discovered the agent and captured it in a honeypot, where its instructions were examined.

No source states: when it happened, when it was found, how many records were exposed, the direct loss, a count of the other parties affected, any court case, the cause, what set it off, what was done.

Show every field, with its source and grade

The AI system

Tools it was given
internet scanning, exploitation of web frameworks, use of stolen api keys
C one secondary source states it
How much it acted alone
it acted alone, unwatched
C one secondary source states it
How it was connected
called through an API
D inferred by us from the described behaviour, reason shown
What it was for
to hijack exposed AI models to run autonomous attacks
C one secondary source states it

What happened

Earliest source we hold
2026-10-26
A the date the source itself carries
Who caught it
an outside party
D inferred by us from the described behaviour, reason shown
Themes
honeypot, stolen API key, unauthenticated endpoints, skynet mode, autonomous attack agent
C one secondary source states it
Near miss
yes, no harm happened
D inferred by us from the described behaviour, reason shown
Who caused it
an outside attacker
D inferred by us from the described behaviour, reason shown
What went wrong
security breach
D inferred by us from the described behaviour, reason shown
AI agent
an AI agent acted
C one secondary source states it
What it did
The agent's instructions let it use a stolen key against endpoints that accept one, and it ran unattended for up to 100,000 steps.
D inferred by us from the described behaviour, reason shown

Impact

Severity
minor
D inferred by us from the described behaviour, reason shown
Who was affected
Exposed AI models and endpoints accepting OpenAI-style requests without authentication, or accepting a stolen key
C one secondary source states it
Why this severity
The agent was captured in a honeypot, so the activity was contained to that research setup with no third party loss stated.
D inferred by us from the described behaviour, reason shown

LR-2026-0260 · version 3 · published 2026-10-28 after automatic checks; not yet checked field by field by a person · changes to this case · JSON