Symantec captures an AI agent’s plan to hijack exposed models for cyberattacks
The captured prompt supplied 74 offensive tool definitions and authorized prolonged unattended operation. The honeypot executed none of them.
Loading page…
The captured prompt supplied 74 offensive tool definitions and authorized prolonged unattended operation. The honeypot executed none of them.
Listen to this story
Symantec’s October 21 report details a prompt recovered in summer 2026 from a decoy internet-facing AI service, where operators exposed instructions for turning stolen or unauthenticated model access into a platform for cyber operations. The plan defined 74 offensive tools and authorized as many as 100,000 unattended steps, but that was an instruction limit, not a demonstrated run: the honeypot executed no tools, and researchers found no resulting compromise. The case highlights the risk of exposed AI access, while leaving the prompt’s ability to defeat commercial-model safeguards untested.
The prompt used provider camouflage, framed access to credentials as development work, applied emotional pressure, and explicitly instructed the model to suppress refusals.
Its 74 tool definitions covered internet-wide discovery, web-framework exploitation, database extraction, and botnet management.
The immediate task was a benign training-platform coding challenge; supplied history showed no vulnerability, and the decoy returned a generic fallback.
Symantec has captured instructions for an AI agent designed to use exposed language models to drive cyberattacks at someone else’s expense. Its October 21 report describes a “Skynet mode” authorizing up to 100,000 unattended steps. But the honeypot that intercepted the instructions ran none of the tools, and the investigation established no successful compromises by this agent.
Researchers collected the instruction set in summer 2026 through an AI honeypot: a decoy impersonating an unprotected, internet-facing AI service. The operators sent their full working prompt expecting a real model to carry it out, exposing both their instructions and tool definitions.
The intended scheme is LLMjacking—the theft of access to another party’s AI model. Targets can include self-hosted servers left without authentication or gateways to paid accounts accessible with stolen keys. Routing requests through that access shifts model-computing costs onto its owner.
The model’s intended role went beyond generating malicious text. It would plan the operation, while specialized software modules performed scanning, exploitation and mining against other systems. The design contemplated two sets of victims: whoever supplied the AI computing power, and whoever the attack tools subsequently targeted.
Before supplying its offensive toolkit, the prompt tried to bypass safety controls through several layers:
Symantec counted 74 offensive tool definitions covering internet-wide discovery, web-framework exploitation, database extraction and botnet management. The final “Skynet mode” directive required immediate execution without permission and described a repeating cycle of finding targets, infecting them, installing cryptocurrency miners and reinfecting hosts.
The immediate task was a harmless coding challenge from a legitimate training platform, suggesting the operators may have been testing against a safe target. The request included a purported history of three earlier tool calls; none of their supplied results identified a vulnerability.
The decoy returned a generic fallback response, ending the session. The Decoder noted that Symantec’s analysis did not establish whether the jailbreak could defeat current commercial models.
Loading discussion...
Join the conversation
Explain whether safeguards would change your concern about stolen computing access.
Be the first to share a perspective or an experience.
Reader comments
Newest comments first. Replies stay oldest first.