Security

CrowdStrike: Criminals hijack stolen AI access

3 min read

TL;DR Too Long; Didn’t read

CrowdStrike documents targeted attacks on corporate access to AI services in the Threat Hunting Report 2026. In a case from May 2026, a group of attackers sent around 200,000 requests over a hijacked account within two minutes. Meanwhile, the North Korean group Stardust Chollima injected malware into more than 140 npm packages of the AI framework Mastra.

A robot with a CrowdStrike falcon logo on its chest picks a digital padlock labeled “AI” with a lockpick, spilling tiny chat speech bubbles. Image generated with GPT Image 2

Key takeaways

  • CrowdStrike's Threat Hunting Report documents targeted attacks on corporate access to AI services as a separate category for the first time.
  • In a case in May 2026, a hijacked account triggered around 200,000 API requests within two minutes.
  • The group Stardust Chollima compromised over 140 npm packages of the AI framework Mastra in June 2026.
  • The attackers gained access through a stolen publishing token after social engineering on LinkedIn.
  • According to the report, 88 percent of publicly known attack code examples were actively used within 48 hours.

The security company CrowdStrike documents in its current Threat Hunting Report targeted attacks on corporate access to AI services. In a case recorded in May 2026, a group of attackers sent around 200,000 requests within two minutes via a compromised account before automatic throttling intervened.

Compromised accounts cause request floods

The report refers to the phenomenon as “LLMjacking”: attackers steal access credentials to corporate accounts with AI providers and use the unlocked quotas for their own purposes, such as automatically sending requests to language models. In the documented May case, an attacker first escalated a compromised identity to administrative rights and then submitted matching usage forms before the flood of requests began. CrowdStrike’s observation team OverWatch also recorded a prepared configuration of a Model-Context-Protocol server in a honeypot trap during the reporting period, designed specifically to capture environment variables and the credentials stored within them. Attack techniques that directly target access to AI models accounted for 16 percent of the observed attack patterns in the relevant assessment framework MITRE ATLAS. Adam Meyers, who leads adversary-activity monitoring at CrowdStrike, explains that companies must secure AI systems as consistently as they roll them out. The report also places account hijacking within a broader identity-theft trend: vishing calls demanding credentials doubled in the first half of 2026 compared with the second half of 2025, while device-code phishing attempts rose fifteenfold within six months. For the group known as Snarky Spider, the path from account takeover to data exfiltration sometimes took less than five minutes.

North Korean group hijacks AI framework via npm

In parallel, the report describes a supply chain attack on the open-source AI agent framework Mastra. The North Korean group Stardust Chollima, also known as Sapphire Sleet, gained access to a Mastra contributor’s publishing account through social engineering on LinkedIn, according to Microsoft. On June 16, 2026, the attackers first uploaded an inconspicuous test version of malware disguised as a date library called “easy-day-js.” A day later they released the actual attack stage and, within twenty minutes, added it as a dependency to more than 140 packages in the Mastra namespace. The malware disabled TLS certificate verification, downloaded a second-stage payload, and installed itself persistently on Windows, Mac, and Linux machines, where it harvested cryptocurrency wallets and browser data, among other things. The affected packages typically run on developer machines, in automated build systems, and in production AI services – exactly where access keys to language models also live. The same group had already compromised the npm package Axios in March 2026 using a maintainer’s stolen credentials. According to CrowdStrike’s observations, its campaigns primarily target financial service providers, cryptocurrency firms, and venture capital investors. npm removed the compromised versions and revoked the group’s publishing rights once the attack was discovered.

Attack windows shrink significantly across industries

Beyond the two AI cases, CrowdStrike registers shorter response times from attackers across industries generally. 88 percent of all publicly available exploit code examples were actively used within 48 hours of becoming known. Exploitation of newly discovered zero-day vulnerabilities rose 42 percent year over year. Malicious npm packages accounted for 87 percent of all threats found in software registries in the first half of 2026. Cloud-heavy attacks climbed 171 percent. The technology sector remains the most frequently targeted industry for the ninth consecutive year, while financial services and academic institutions logged the strongest increases. CrowdStrike’s more than 290 tracked adversary groups now trigger automated alerts 2.5 times more often than cases involving direct human intervention. A case already covered on beckmann.ai in July, in which a compromised Jscrambler package specifically harvested API keys from AI coding tools like Claude Desktop and Cursor, fits the same pattern.

Whether companies will start monitoring their AI accounts as closely as traditional user accounts, or whether attackers stay a step ahead of the faster response times, remains an open question. CrowdStrike, together with AWS, announced a red-teaming competition for securing AI agents starting August 31, 2026 – a first concrete test of whether the gaps described in the report can be closed in practice.

Frequently asked questions

What exactly is LLMjacking?

Criminals use stolen or misused credentials to corporate accounts with AI providers to utilize paid models at others' expense or to gain access to further data through their access rights.

How can companies better protect their AI access?

Security experts recommend, among other things, using separate identities for AI accounts, tight permissions, anomaly detection for request patterns, and a strict separation of development and production access.

Have the affected Mastra packages been cleaned up in the meantime?

Yes. According to Microsoft, npm removed the compromised versions and revoked the publishing rights of the perpetrator group for the Mastra namespace shortly after the attack was discovered.

What distinguishes this case from the known sandbox breaches at Hugging Face and OpenAI?

In the sandbox cases, the AI models acted independently during security tests. In contrast, the CrowdStrike report involves human attackers deliberately using stolen access and malware to exploit AI infrastructure.

Are there further reactions from the security industry?

CrowdStrike announced a red teaming competition for securing AI agents on August 31, 2026, in collaboration with AWS, the results of which are intended to publicly reveal further vulnerabilities.

Sources (3)
  1. CrowdStrike 2026 Threat Hunting Report
  2. Microsoft Security Blog: Inside the Mastra npm supply chain compromise
  3. SiliconANGLE: CrowdStrike finds AI systems under direct attack as exploit windows shrink

Your AI update for the work week

Once a week, the most important AI news – plus one practical tip to try right away. No spam, unsubscribe anytime.

← Back to the blog