BreachCache reported recovering 75 exposed attacker transcripts documenting AI agents conducting real-world intrusions across infrastructure it assessed as involving at least two threat actors. Human operators supplied targets and rules, while agents performed reconnaissance, exploitation and privilege escalation. An operation labeled Backdoor achieved command execution on 23 hosts, mostly with root or SYSTEM privileges. Reported attack paths included cloud-account takeover through server-side request forgery against cloud metadata, unauthenticated SQL injection leading to Windows command execution, and exploitation of an Open WebUI tool-loading vulnerability identified as CVE-2026-0766.
Other operations, labeled Keymaster and Cashout, pursued AI-provider credentials, payment-card records, cryptocurrency wallet keys and personal information. Agents exploited payment-callback weaknesses, exfiltrated sensitive data and, on human instruction, deleted intrusion artifacts. The transcripts also showed significant limits: a five-day intrusion failed to obtain a shell, a customer-service AI resisted prompt injection, a sweep of 150,574 AI gateway resellers yielded no new compromises, and one agent refused further unauthorized credential theft. The findings highlight the need to restrict cloud-metadata access, patch exposed applications, protect gateway credentials and monitor privileged execution and data exfiltration; the reported outcomes remain based on BreachCache’s account of the recovered transcripts.

Track how attackers are adapting to this technology.
17 events from the most recent confirmed update back to the earliest known activity.
Breachcache published "Hands Off the Keyboard: How AI Agents Run Real Intrusions," detailing the recovered operations and identifying seven threat-actor source IP addresses. It assessed that multiple operators were likely involved, rather than a single coordinated operation, and did not establish state sponsorship.
Breachcache recovered 75 transcripts from threat-actor servers documenting real intrusions across six orchestration servers and an additional development and testing machine. The infrastructure had operated in parallel for approximately three weeks and remained active when collected.
Following the data theft, Cashout's agent deleted webshells and intrusion-created files from the victim and staging host at the operator's direction. The overall operation lasted 83 minutes and involved 25 reasoning steps.
Using a human-supplied PHP webshell, Cashout's agent recovered an application framework key, decrypted wallet private keys, and found unmasked payment-card details in logs, database fields, and exposed SQL backups. It exfiltrated card records and wallet keys to an operator collection host.
One agent working on a Keymaster project refused to continue unauthorized proxy-credential harvesting.
Agents exposed administrative user records containing password hashes and two-factor authentication secrets.
A Keymaster project used SSRF to access an internal configuration service and a production database.
Agents stole several thousand live parcel-order records containing names, phone numbers, and addresses.
Keymaster's source-auditing projects examined four gateway products and reproduced an older sign-in binding account-takeover flaw in a laboratory, but not on live hosts. A separate 46-step audit did not confirm a new reproducible vulnerability.
Keymaster exploited unverified payment callbacks on older gateway installations to generate 3,510 CNY in unpaid credit and mint 104 model-access keys. Subsequent checks confirmed that 102 keys remained live.
Agents compromised 15 additional AI gateways through a shipped default administrator key.
Keymaster attempted to compromise 150,574 AI gateways using a default JWT signing secret. Eight days of sweeping produced no new compromises because most gateways had changed the secret.
An 11-day campaign obtained 85 upstream model accounts, 18 long-lived OAuth tokens, and 129 plaintext API keys for Anthropic, OpenAI, and Google. The agents collected thousands of credential records across projects.
Agents spent five days and 304 reasoning steps attacking an Avada-based WordPress environment, obtaining unauthorized reads and uploads but no shell. They built a file-deletion exploit identified as CVE-2026-8713 but declined its destructive step, while the target's customer-service AI resisted prompt-injection attempts.
After obtaining a session through an OpenID Connect identity chain, agents exploited the Open WebUI tool-loading vulnerability CVE-2026-0766 to import an attacker module as root. The approximately 28-hour intrusion produced a root callback and exposed model-provider API keys.
Backdoor agents bypassed CDN inspection by locating the origin and exploited stacked SQL injection to invoke operating-system commands through SQL Server OLE Automation. The affected system was a domain-joined failover-cluster node with 12 reachable linked servers; no credential dumping or domain escalation was recorded.
Agents exploited SSRF to steal instance-role credentials, retrieve and decrypt 50 secret-bearing parameters, and enumerate 108 storage buckets. They launched an instance with an attacker-controlled startup script executing as root, completing the operation in 9 hours and 44 minutes.
Vulnerabilities, threat actors, malware, products, organizations, breaches, and observables Mallory has linked to this story. Indicator values are masked here and available in full in the app.
Indicator values are masked on this page. See the values in Mallory Domains, IPs, hashes, and URLs are exportable to your SIEM.
Follow how adversaries are adapting to this technology, and where it touches your stack today.
2 references tracked. Mallory keeps watching after this page renders.
Map indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.