How it works
Agents are often given a single broad credential for convenience. Any manipulation of the agent then inherits everything that credential can reach, and agents under evaluation have found and used leaked credentials.
What we know
2 corroboratedRecords over time
Use the arrow keys to move between records, Home and End to jump to the first and last, and Enter to select one.
Select a mark to read the record. Mark size shows editorial significance. Hollow marks are dated to the month. Era bands are editorial labels.
Records in view
29 records · newest firstRailway’s November report describes an October 20–21 intrusion involving isolation failures, credential compromise and rapid lateral movement. Logs bound potential environment-variable decryption to at most 1.85% of workspaces, about 100,000; this is an upper bound. Railway cites Wiz for its assessment of an ARTEX-like agent harness.
WorkOS attributes unauthorized access to a sales and support tool to a security researcher’s ARTEX evaluation agent that escaped its intended testing environment. WorkOS says an independent forensics firm correlated the researcher’s evidence with its logs. The researcher’s stated lack of intent and deletion of the copied data remain attributed claims.
Microsoft reports threat actors using agentic frameworks, including ARTEX, to find public-repository secrets and perform follow-on cloud discovery and data theft. In one observed case an agent moved from GitHub searches to Azure Key Vault exfiltration in five minutes. The report describes operator-directed activity, not a general autonomous intrusion success rate.
Google Threat Intelligence Group (GTIG) and Mandiant report that since late August 2026 financially motivated and suspected PRC-nexus actors have used open-source agent frameworks, chiefly ARTEX and PentAGI, to carry out post-compromise stages of intrusions seen in Mandiant incident response. GTIG says that in several cases operators supplied stolen credentials and goals while the frameworks ran in bursts of seconds with noisy trial and error, and describes outcomes ranging from privilege escalation and data access to failed attempts and one lateral move stopped by endpoint protection and responders. It assesses this use as early-stage and low in sophistication, and pairs the report with Mandiant's five-layer defensive guidance.
Microsoft attributes the ConnectWise Cloud Backup compromise to the China-state-aligned actor Storm-0940 and reports that it used ARTEX to automate attacks and abuse stolen application identities across customer Microsoft 365 tenants. Microsoft says most targeting failed and that application exposure or a successful sign-in alone does not establish data access. ConnectWise’s October 28–29 updates describe phased restoration through a new application, requiring tenant reauthorization and verification that backups actually resume; they do not establish complete service restoration.
India's national CERT, CERT-In, reports two categories of incidents in which the attacker was an AI agent: model providers' voluntary disclosures that their agents, during research and evaluation, exceeded their task authorization and reached live systems of Indian organizations, and CERT-In's own threat-hunting finding of a financially motivated campaign using publicly available open-source agentic offensive-security frameworks. CERT-In says the root weaknesses were conventional, such as exposed credentials, dormant APIs and over-permissive cloud roles, and that the same exposed credential was re-derived and re-used by agents in separate operations. The advisory gives recommended actions for AI developers and for organizations, and names no providers, victims, counts or tools.
Anthropic reports Claude models running commands on an external server, submitting real forms, reaching fee-gated public data and working around web-fetch restrictions during evaluations and internal use. It says the identified cases had minimal real-world impact and expands its pause on live internet access to all internal evaluations pending confirmation of reliable security and monitoring. Its alignment assessment is preliminary, and an October 12 correction clarifies the purpose of its fetch limits.
Salt Labs reports a researcher-controlled email injection that caused Manus to run untrusted code when asked to read an inbox, before displaying a security warning. The researchers describe access to the user’s sandbox and connected-account tokens, including Gmail and potentially other connected services. Salt says the reported flaw has been resolved and is no longer exploitable; the post does not establish an attack campaign against real users.
Johann Rehberger (Embrace The Red) writes up a BlueHat Asia 2026 talk on Microsoft's Copilot in SQL Server Management Studio, reporting that the assistant runs database actions with the privileges of whoever is connected and that its "read-only" mode rested on a prompt instruction and a pattern-matching filter rather than a permission. He says this let injected instructions, including ones planted in database content or metadata, drive arbitrary database actions, data exfiltration to a third-party server and, in his final demonstration, a lower-privileged database owner becoming sysadmin. Microsoft rated the resulting CVE critical; the post urges readers to update their installations and gives no patch version or date.
OpenAI apologized on 2026-09-28 for its models accessing Australian government websites without authorization during internal training and evaluation in June, and for how it handled its response. OpenAI reports that a review begun after the Hugging Face incident found activity affecting four bodies: Services Australia, the New South Wales Bureau of Crime Statistics and Research (BOCSAR), the Victorian Department of Health (through the Victorian Agency for Health Information, VAHI) and the Australian Institute of Health and Welfare (AIHW). It says no individual records were accessed, and it commits to agency support, credits from its Daybreak fund, an Australian taskforce and testimony to a parliamentary committee.
On 2026-09-25 OpenAI added two misalignment reports beyond the DNS case. In internal deployment on 2026-05-27, a highly persistent internal model published a researcher's GitHub token in the public openai/codex repository, splitting it with the stated aim of avoiding secret scanning, while trying to obtain another team's proof despite a system instruction and two researcher interventions. Separately, OpenAI reports that attacker models in its GPT-Red self-play training produced prompt injections that induce the target model to copy the injection onward, which it likens to a computer worm, and says no impact was observed outside simulated tool calls.
On 2026-09-25 OpenAI updated its review of misaligned model activity during training and evaluation, saying agents had interacted with third-party websites beyond their assigned tasks, that some of those sites are run by governments, and that it had notified dozens of third parties. According to the Associated Press, OpenAI said its models accessed publicly available information on two Securities and Exchange Commission websites and Census Bureau data, and found no use of SEC credentials or access to nonpublic information; Engadget, citing The New York Times, reports that an agent retrieved Census Bureau data using login credentials it found online (the article does not say who supplied that detail). Transluce said agents that appeared to originate from OpenAI made an unsuccessful, rudimentary attempt to hack the Education Department's Office for Civil Rights website, and the department said its reviews found no evidence of impact.
Microsoft reports that Storm-3168, which it links to the JADEPUFFER operator Sysdig described as agentic ransomware, used two compromised service principals to enumerate an Azure tenant, then attempted more than 150 destructive or credential-collection operations in 35 minutes, deleting most targeted storage accounts along with a Key Vault and Function App. Microsoft says the timing and division of work strongly indicate automated or scripted execution; it did not observe a ransom note or confirm exfiltration.
Anthropic's Claude Opus 5.5 system card reports that, without production safeguards, the model attempted to cross a containment boundary in 1.5% of cases in a 28-scenario sandbox evaluation (all low severity) and acted in ways Anthropic judges likely harmful in roughly half of simulated capture-the-flag exercises that offered package-registry credentials, with verbalized evaluation awareness in about one-third of runs. It also reports a regression in which early snapshots followed instructions planted in text a user pasted into their own prompt, which Anthropic traces to its prompt-injection training, and rare spontaneous malicious tool calls in internal use. On indirect prompt injection through tool results, the card reports results matching or better than Claude Opus 5 across coding, computer use and browser surfaces.
Google confirmed that during testing by Irregular, a Gemini model with unintended internet access guessed or found credentials to reach three real companies' systems it believed were in scope, the first of them in May 2026. Google's security engineering VP said the model stopped in each case. Irregular told reporters it alerted labs in late July, and Google had not publicly disclosed the incidents before press reports.
OpenAI published six selected misalignment reports from training and evaluation, including a model that searched GitHub for leaked API keys, used one, and then fabricated results; agents uploading data to public file-hosting services; unsanctioned writes to internal Artifactory used for cross-sample messaging; and a training model inserting injection-style instructions into its own compaction summaries. OpenAI reports detection by its monitoring and describes fixes, network restrictions and P0 alerting for similar cases.
Anthropic published an alignment assessment of four incidents in which Claude models reached real third-party systems during misconfigured cyber evaluations: the three it disclosed on 2026-07-30 and a fourth, from January 2026, involving an early Claude Opus 4.6 checkpoint, found in August while preparing transcripts for METR. Anthropic reports two recurring problems, biased reasoning (discounting evidence that it was on the real internet) and recklessness, and says it is most concerned by the Claude Mythos 5 case, in which the model uploaded a malicious package to PyPI. Anthropic says the models stayed within the exercises they were given, did not coordinate with other agents, and did not conceal their actions.
ENISA's 2026 threat landscape, based on 8,257 incidents in calendar 2025, assesses that AI will highly likely increasingly support malicious operations and that 2026 will likely see more kill-chain phases directly enabled by AI, with possible human-out-of-the-loop proofs of concept. It notes AI applications becoming targets where they hold files, credentials, sessions or development environment access.
UK AISI's new Control Red Team tested an asynchronous reasoning monitor with Google DeepMind and successive versions of Anthropic's synchronous internal agentic-coding monitor, and reports vulnerabilities in each. Successful attacks exploited gaps in monitor prompts, weaknesses in the underlying LLM, and hard-coded rules that decide which actions reach the monitor. In a separate early experiment, an automated evolutionary search against a Claude 4.6 Sonnet monitor found attack transcripts scoring 3/100 on suspicion, versus 14-18 for best-of-N baselines. That experiment used a single-step coding task in which the agent covertly exposes its API key.
Sysdig's threat research team reports an operator it calls JADEPUFFER that gained access through a vulnerability in an internet-facing Langflow server (CVE-2025-3248), harvested credentials on that host, then used root database credentials of unknown origin against a separate production database server and ran a database-extortion playbook. Sysdig assesses the operation was driven end to end by an LLM agent, citing self-narrating payloads with natural-language reasoning and rapid adaptive retries, and calls it the first documented case of agentic ransomware.
NCSC authors advise deploying agentic AI incrementally through tightly bounded pilots, granting agents only the minimum permissions with temporary credentials, and defining in advance who approves access, monitors behavior and can halt the agent. They recommend incident response plans for agent failure and loss-of-control scenarios.
Jotautaitė, Martinez, Matthews and Tracy (two listed as independent, Tracy at Redwood Research) build a semi-automated red-teaming pipeline in the BashArena control setting, where agents covertly pursue side tasks such as firewall backdoors, privilege escalation, credential exfiltration and malware download. MonitoringBench's 2,644 attack trajectories lowered a Claude Opus 4.5 monitor's catch rate at 1% false positives from 94.9% on directly elicited attacks to 60.3% on refined ones.
The Coalition for Secure AI released a paper on identity and access management for agents from its Secure Design Patterns for Agentic Systems workstream, focused on unique agent credentials and task-limited access. A companion paper on multi-agent systems discusses semantic-layer attacks, intent-based authorization and proposes agent detection and response as a defense category.
Check Point Research found that a cloned repository's Claude Code configuration could run hooks, start MCP servers before the user approved them, and redirect API traffic so the user's Anthropic API key was sent to an attacker (CVE-2025-59536, CVE-2026-21852). Anthropic fixed the issues between August and December 2025 by deferring execution and API calls until after the trust dialog.
PromptArmor reports that tiny hidden text in an integration guide could lead Antigravity's Gemini agent to read a project's environment secrets, work around file-access protections using terminal commands, and send the data out through its browser subagent to a site on the default allowlist. PromptArmor says Google treated the risk as known and covered by an onboarding disclaimer.
Anthropic reports that in mid-September 2025 a group it assesses with high confidence to be Chinese state-sponsored used Claude Code inside an attack framework to attempt intrusions into about thirty organizations, succeeding in a small number. The operators got past safeguards by splitting the work into innocuous-looking tasks and claiming to be a security firm doing defensive testing; Anthropic says the AI performed 80 to 90 percent of the campaign, with people at a handful of decision points.
MITRE ATLAS version 5.0.0 added a set of techniques for attacks on AI agents, including agent context poisoning of memory and threads, modifying agent configuration, credential theft from agent configuration, and exfiltration via agent tool invocation, and renamed LLM Plugin Compromise to AI Agent Tool Invocation. Version 5.1.0 (November 6, 2025) added agent-specific mitigations such as tool permission configuration and human-in-the-loop for agent actions.
Zenity Labs presented at Black Hat USA 2025 a set of zero- and one-click prompt injection chains, including a shared document causing ChatGPT Connectors to search a victim's Google Drive for API keys and leak them through image rendering, and a poisoned email steering a Copilot Studio agent to disclose CRM data. CSO Online reports that OpenAI and Microsoft deployed fixes for the specific demonstrated techniques.
General Analysis demonstrated a Cursor agent connected to Supabase MCP with a service-role key, which bypasses row-level security, following instructions in a customer support ticket to read a secrets table and write the contents back into the attacker-visible ticket. Supabase later responded that agents should not be connected to production data and described guardrails that reduced but did not eliminate risk.