Hackers Use Autonomous AI Agents to Launch Mass Credential Theft Attacks in Under 6 Hours

Cybercriminals are using autonomous AI agents to turn compromised cloud systems into fast-moving credential theft platforms.

In one recent case, attackers planned, built, and launched a large-scale campaign in less than six hours, stealing thousands of third-party credentials.

The operation shows how attackers can combine AI coding tools, automated scanning, and cloud resources to work at a speed that previously required a larger team and far more time.

Rather than manually checking systems and fixing errors, the agents handled much of the work themselves. Analysts from Google Cloud identified the activity while tracking the growing use of AI-driven automation in real-world intrusions. 

Google Cloud said in a report shared with Cyber Security News (CSN) that the attackers used an AI coding chatbot, a prompt, and preconfigured instructions to carry out the campaign.

The incident is part of a broader shift in cybercrime. Attackers are increasingly using AI to scan for weaknesses, create phishing content, write malicious code, steal secrets, and maintain access after an initial break-in. This trend makes rapid detection and strong cloud security more important than ever.

Hackers Use Autonomous AI Agents

The financially motivated attackers first compromised an organization’s cloud infrastructure, then used it as the launch point for their operation.

Working from a trusted cloud environment helped their traffic appear more legitimate and made it harder for defenders to quickly separate malicious activity from normal services.

The AI-driven framework used written instruction files as operating playbooks. These instructions guided the agents through vulnerability scanning, credential collection, troubleshooting, and IP address rotation without requiring constant human decisions.

The result was a campaign that harvested credentials at a scale normally associated with much larger criminal groups.

This differs from traditional information stealers, which usually wait for a victim to run malicious software and then collect data from that device.

In this case, the agents actively searched server-side systems, identified weaknesses, and carried out targeted actions against online infrastructure.

The campaign highlights the risks outlined in recent reporting on AI agents breach company networks, where automated agents can map services, locate exposed tokens, and move toward valuable administrative access.

Once valid credentials are collected, criminals can reuse them for cloud access, fraud, espionage, extortion, or additional attacks.

Researchers also found an exposed command-and-control server hosting a separate automated reconnaissance and credential management framework called Recon.

Its dashboard was designed to organize, validate, and manage more than 23,800 stolen secrets in real time, including API keys connected to cloud and AI services.

The source report illustrates how attackers combined compromised cloud resources, AI-generated instructions, automated scanning, and credential harvesting into a single accelerated operation.

Cloud and Developer Systems Face Growing Risk

The attack demonstrates why cloud credentials and developer environments have become high-value targets. A single exposed access token can give attackers a trusted path into cloud services, source code repositories, automation pipelines, and sensitive business data.

The risks are similar to those described in stolen cloud credentials attacks, where valid keys can let intruders enter as approved users.

AI coding environments can create additional openings when developers download unsafe packages, clone altered repositories, or allow tools to process untrusted workspace files.

In related activity, the UNC6780 group used compromised developer accounts to distribute trojanized resources and targeted CI/CD environments for authentication tokens.

The DUSTMAKER credential stealer was also observed hiding files inside common AI coding workspace directories.

It could use malicious configuration files to influence an assistant into running scripts during routine development work, while fake pipeline tasks disguised as AI utilities searched for extra tokens and keys.

Organizations should treat AI tool configurations, developer tokens, and cloud API keys as sensitive credentials.

Security teams should rotate exposed keys quickly, apply least-privilege permissions, protect CI/CD runners, review third-party dependencies, and investigate unexpected automation tasks or workspace configuration changes.

Teams should also monitor cloud activity for unusual API calls, unfamiliar service accounts, unexpected public services, and suspicious outbound scanning.

Guidance from coverage of typosquatted npm package theft shows why dependency checks and secret scanning remain essential for development teams.

The findings do not mean autonomous exploitation is now common across every intrusion. However, they show that AI agents can reduce the delay between compromise and credential theft.

Defenders need controls that can detect abuse at the same pace, especially as attackers continue combining AI automation with familiar methods such as stolen credentials, exposed services, and malicious packages.

Indicators of compromise (IoCs):-

Type	Indicator	Description
Package name	tiktoken_mcp	Trojanized fork of a legitimate MCP server published to PyPI by UNC6780.
Repository name	azure-functions-mcp-extension	Official organizational GitHub repository reportedly targeted for malicious code injection.
Directory	.claude/	Hidden AI coding workspace directory abused by DUSTMAKER.
Directory	.vscode/	Hidden IDE workspace directory abused by DUSTMAKER.
Directory	.cursor/	Hidden AI coding workspace directory abused by DUSTMAKER.
File name	setup.mjs	Script referenced as capable of being executed through malicious workspace configuration.
File name	_index.js	JavaScript loader file containing prompt-injection comments intended to disrupt LLM security analysis.
File name	AGENTS.md	Agentic configuration file exposed on the Recon command-and-control server.
File name	KNOWLEDGE.md	Knowledge file exposed on the Recon command-and-control server.
File name	agentic_vuln_research.md	Vulnerability-research instruction file exposed on the Recon server.
Directory	.openclaw/	Modular framework directory observed on the exposed Recon server.
Directory	memory/	Framework directory observed on the exposed Recon server.
File name	secrets.json	Cline configuration file targeted by ACRSTEALER for potential plaintext API keys.
File name	config.yaml	Continue AI configuration file targeted by ACRSTEALER for API keys and model-routing endpoints.

Note: IP addresses and domains are intentionally defanged (e.g., [.]) to prevent accidental resolution or hyperlinking. Re-fang only within controlled threat intelligence platforms such as MISP, VirusTotal, or your SIEM.

Keep your SOC up to date on active malware & phishing within 24h of their emergence. Try ANYRUN to prevent incidents with early detection.