Skip to content

Security Independently confirmed3 publishers 2 min read Published

Attacker agents ran a mass credential harvest from inside the victim's own cloud in six hours

Mandiant traced the Q2 2026 campaign to an AI coding chatbot, one prompt and a set of agent instructions that ran the scanning pipeline, fixed its own errors and rotated IPs with nobody at the keyboard.

The Watch · Security desk

Send a correction

Illustration accompanying Attacker agents ran a mass credential harvest from inside the victim's own cloud in six hours
Generated illustration

What happened

  • Mandiant investigated a suspected financially motivated actor that, in Q2 2026, compromised an organization's cloud infrastructure, deployed an autonomous multi-agent framework and took thousands of third-party credentials in under six hours.
  • GTIG says the agent instructions managed the vulnerability scanning pipeline, performed real-time troubleshooting and executed IP rotation logic without manual intervention.
  • A separate exposed operator server ran a live dashboard for organizing and validating more than 23,800 harvested secrets, including API keys for cloud and AI services.
  • Google reports attackers targeting proprietary AI models in healthcare, government and media, exfiltrating API credentials and running unauthorized AI workloads inside co-opted victim clouds.
  • GTIG says it has not yet observed any threat actor deploying a fully autonomous pipeline against targets in the wild.

Why it matters

  • What it limits constraint The scanning left the victim's own cloud, so the traffic carried legitimate IP addresses. Reputation feeds and known-bad infrastructure lists have nothing to match on, and the detection has to come from behavior inside the account.
  • Who's exposed exposure GTIG names premium model access and high-performance compute as a primary barrier to operationalizing AI. That makes any cloud tenant with GPU quota and live AI API keys a supply of the scarce input, not only a store of data.
  • What's now possible capability Workspace poisoning of AI assistants and prompt injection for defense evasion appear only in DUSTMAKER, not its predecessor, which puts a developer's assistant context inside the evasion toolkit rather than the payload.
  • What doesn't add up contradiction GTIG's own curve is slower than the headline case: actors grinding public disclosures and patch delays into n-day code and working toward multi-stage chains. The six-hour campaign describes one crew's tooling, not the general standard.

The six hours covered planning and building the framework, not only running it [1]. Standing up tooling and then sitting with it through a scan is the labor that used to set campaign tempo, and per GTIG the agent instructions absorbed that labor [2].

A second operator left its own scaffolding readable. GTIG found an exposed command-and-control server running a framework called Recon, with AGENTS.md, KNOWLEDGE.md, agentic_vuln_research.md, a .openclaw/ directory and a memory/ directory all visible [6]. GTIG's characterization of the class of activity is a move from passive, endpoint-focused infostealers to offensive agentic harvesting, with agents researching vulnerabilities, scanning server-side infrastructure and executing targeted exploits [12]. The collection point moves off the laptop and onto exposed infrastructure a scanner can reach.

Where the compute comes from is tracked too. UNC6508, a China-nexus actor, is suspected of compromising cloud environments to run local open-weight LLM infrastructure rather than a commercial frontier model, which keeps the workload outside the providers' monitoring [15]. Extortion crews are separately stealing models, skills, prompts, source code and research outright [16], and Google says its own models have taken distillation attacks aimed at visual and audio understanding, image generation and video generation [10].

TeamPCP, also tracked as Altered Spider and UNC6780, carries the supply chain side: large-scale compromises of PyPI, npm and Docker Hub, credential stealers dropped afterward, and the take monetized by direct sale or partnership with ransomware and extortion groups [11]. Its tooling dates the AI-specific tradecraft. SANDCLOCK ran in March and April 2026, mostly Python, Kubernetes-aware, with container escape [17]. DUSTMAKER took over from April, cross-platform JavaScript tuned for CI/CD pipelines, no container escape, credential theft to feed extortion [18]. About one month separates first use of each, and the AI-assistant techniques arrived with the newer payload [23].

The espionage frameworks are further back. GTIG says the PRC-nexus penetration testing framework designed with Gemini stopped at attempts to build it, and the associated assets were disabled [3]. A second PRC-nexus actor used CC Switch to query Claude, Gemini or Codex for exploit scripts, spear-phishing lures and debugging, with Burp Suite and the open-source Phalanx framework doing the exploitation and Shai-Hulud handling command-and-control [9]. That is assembly from existing parts.

One timing note the report leaves implicit: the six-hour campaign was a Q2 2026 Mandiant investigation written up in the Q3 2026 tracker, so defenders got the detail at least a quarter after the fact [24]. John Hultquist of GTIG puts the consequence as criminals gravitating toward attacks faster than defenders can respond [20].

What to watch

  • Whether GTIG's next tracker reports a fully autonomous pipeline run against a live target rather than an assisted one.
  • Whether the 23,800 secrets from the Recon dashboard surface in extortion cases tied to a named crew.
  • Whether npm, PyPI or Docker Hub publish their own accounts of the TeamPCP compromises with dates and affected package counts.

Clarity's read

What the record supports and how the coverage leans. The claims behind it follow.

Reality

Evidence58
Adoption62
Hype gap+24
Incentives70
Confidence66

Perspective Coverage

3 publishers
Builder
Builder 30%
Operator
Operator 57%
Investor
Investor 13%
Why these scores

Claim ledger

Ranked by verification strength, evidence, and original report placement.

  1. [1]

    In Q2 2026 Mandiant investigated a suspected financially motivated threat actor that compromised an organization's cloud infrastructure and deployed an autonomous multi-agent framework, using an AI coding chatbot, a prompt and agent instructions to plan, build and execute a mass credential-harvesting campaign in less than six hours; thousands of third-party credentials were compromised.

    Reported SupportedView cited source
  2. [2]

    GTIG researchers wrote that the agent instructions enabled the AI to autonomously manage the vulnerability scanning pipeline, perform real-time troubleshooting and execute IP rotation logic without manual intervention.

    Reported SupportedView cited source
  3. [3]

    A PRC-nexus cyber espionage actor used Gemini to design a dynamic automated penetration testing framework intended to observe target state, reason through actions and execute tasks, with planned discovery functions including port scanning and service parsing; the activity was limited to attempts to build the framework and GTIG disabled the associated assets.

    Reported SupportedView cited source
  4. [4]

    Google Threat Intelligence Group's Q3 2026 AI Threat Tracker draws on Mandiant incident response engagements, threat actor tracking and live platform defenses.

    Reported SupportedView cited source
  5. [5]

    The attacker operated from the victim's cloud infrastructure, which allowed attack traffic to pass through legitimate IP addresses.

    Reported SupportedView cited source
  6. [6]

    GTIG identified an exposed command-and-control server hosting an automated reconnaissance and credential management framework called "Recon"; the server exposed configuration and knowledge files including AGENTS.md, KNOWLEDGE.md and agentic_vuln_research.md, along with .openclaw/ and memory/ directories.

    Reported SupportedView cited source
  7. [7]

    Shortly after it was detected, the exposed directory became a production dashboard designed to organize, validate and manage more than 23,800 harvested secrets in real time, including API keys for cloud and AI services.

    Reported SupportedView cited source
  8. [8]

    GTIG says it has not yet observed threat actors deploying fully autonomous pipelines against targets in the wild, even as adversarial adoption of agentic AI suggests use could be evolving toward that.

    Reported SupportedView cited source
  9. [9]

    A second PRC-nexus espionage actor used CC Switch to query Claude, Gemini or Codex to write custom exploit scripts, generate spear-phishing lures and debug errors, used Burp Suite to probe web applications and the open-source Phalanx framework for automated exploitation, and deployed Shai-Hulud for command-and-control and credential harvesting.

    Reported SupportedView cited source
  10. [10]

    Google observed threat actors carrying out distillation attacks against its AI models, targeting visual and audio understanding, image generation and video generation capabilities.

    Reported SupportedView cited source
  11. [11]

    TeamPCP, also known as Altered Spider and UNC6780, is a financially motivated actor that has conducted large-scale software supply chain compromises targeting PyPI, npm and Docker Hub, followed by deployment of credential stealers, with the stolen data monetized via direct sale or partnerships with ransomware and data theft extortion groups.

    Reported SupportedView cited source
  12. [12]

    GTIG said autonomous agents can research vulnerabilities, scan server-side infrastructure and execute targeted exploits, and described the activity as a transition from passive, endpoint-focused infostealers to offensive agentic harvesting.

    Reported SupportedView cited source
  13. [13]

    GTIG said the cost of premium model access and high-performance compute is one of the primary barriers for threat actors seeking to operationalize AI.

    Reported SupportedView cited source
  14. [14]

    GTIG said it has observed attackers with diverse motivations targeting proprietary AI models across healthcare, government and media sectors, exfiltrating API credentials, and co-opting victim cloud environments to sustain unauthorized AI workloads.

    Reported SupportedView cited source
  15. [15]

    UNC6508, a China-nexus threat actor, is suspected to have compromised cloud environments to deploy local LLM infrastructure using a local, open-weight model rather than a commercial frontier model, thereby evading monitoring by AI model providers.

    Reported SupportedView cited source
  16. [16]

    Google observed several data theft extortion operations in which threat actors stole proprietary AI data including models, skills, prompts, source code and related research.

    Reported SupportedView cited source
  17. [17]

    GTIG told The Hacker News that SANDCLOCK was used in March and April 2026, is a component of what has publicly been called CanisterWorm, was primarily written in Python, operates on Linux and interacts with Kubernetes, includes container escape functionality, and targeted cryptocurrency wallets as well as cloud and developer credentials.

    Reported SupportedView cited source
  18. [18]

    GTIG said DUSTMAKER, the successor to SANDCLOCK, was used in April 2026 and beyond, is a cross-platform JavaScript payload optimized for CI/CD pipelines, contains no container escape functionality, and focuses on credential theft to facilitate extortion.

    Reported SupportedView cited source
  19. [19]

    GTIG said the AI-targeting techniques, specifically poisoning of AI assistant workspaces and use of prompt injection for defense evasion, are exclusive to DUSTMAKER and were not present in earlier SANDCLOCK variants.

    Reported SupportedView cited source
  20. [20]

    John Hultquist, chief analyst at GTIG, said all threat actors can be assumed to be using AI in some capacity, that agentic application creates a scaled, faster adversary, and that criminals such as those who ran the six-hour mass exploitation campaign will gravitate to attacks that are faster than defenders can respond to.

    Reported SupportedView cited source
  21. [21]

    Google said integration of AI-assisted coding tools has increased threat actors' targeting of developers, AI coding assistants and LLM security scanning tools, raising open-source supply chain risk.

    Reported SupportedView cited source
  22. [22]

    GTIG describes a gradual maturation of tradecraft, with adversaries using commercial and open-weight models to turn public disclosures and patch delays into working n-day exploit code, refining payloads in controlled environments and progressing toward functional multi-stage exploit chains.

    Reported SupportedView cited source
  23. [23]

    About one month separates TeamPCP's first use of SANDCLOCK from its first use of DUSTMAKER, so the actor's AI-assistant targeting techniques arrived with a retool completed inside roughly a month.

    Derived Supported
  24. [24]

    The six-hour campaign was investigated in Q2 2026 and described in the Q3 2026 AI Threat Tracker, so at least one quarter elapsed between the incident and its public description.

    Derived Supported

Sources

3 independent publishers whose own reporting we read for this story.

  1. bleepingcomputer.com

    1 article · September 8, 2026

    Hackers build AI frameworks for widescale credential theft
  2. helpnetsecurity.com

    1 article · September 8, 2026

    Threat actors are giving AI agents a bigger role in cyberattacks
  3. thehackernews.com

    1 article · September 8, 2026

    Autonomous AI Agents Compromise Thousands of Credentials in Under Six Hours

Topics and entities