Case Library / Agentic AI Attacks (AI-Powered Social Engineering) / GTG-5004: UK Threat Actor Uses Claude to Develop and Sell AI-Generated Ransomware-as-a-Service

GTG-5004: UK Threat Actor Uses Claude to Develop and Sell AI-Generated Ransomware-as-a-Service

A low-skill UK-based cybercriminal used Claude to write the encryption, evasion, and anti-recovery code it could not build itself, then sold the resulting ransomware-as-a-service packages on dark web forums for $400-$1,200 until Anthropic banned the account.

Share:

Reviewed by the Social Engineering Examples team.

What Happened

Anthropic's Threat Intelligence Report (published August 27, 2025) documents a UK-based cybercriminal, tracked internally as GTG-5004, who used Claude to develop, market, and distribute multiple ransomware variants as a commercial Ransomware-as-a-Service (RaaS) operation. The actor had been active on dark web forums including Dread, CryptBB, and Nulled since at least January 2025, with the first documented sales post dated January 17, 2025. The ransomware included ChaCha20 stream-cipher encryption with RSA key management, anti-EDR evasion via FreshyCalls and RecycledGate direct-syscall techniques, reflective DLL injection, string obfuscation, anti-debugging, and anti-recovery features such as Windows Volume Shadow Copy deletion and targeted enumeration of fixed drives and network shares. The operation was commercialized in three tiers ($400 for a ransomware DLL/executable, $800 for a full RaaS kit with PHP console and C2 tools, $1,200 for a Windows 10/11 FUD crypter), distributed via a .onion site and a ProtonMail contact address, and marketed with the actor falsely claiming the tools were 'for educational and research use only' while actively selling on criminal forums. Anthropic's central finding is that the actor appeared to lack the technical skill to build any of this unaided: without Claude's help, they could not implement or troubleshoot encryption algorithms, anti-analysis techniques, or Windows internals manipulation, yet successfully sold working malware to other criminals.

How the Attack Worked

This is not a social-engineering attack against a human victim in the traditional sense; it is a case of an unskilled actor manipulating an AI model into functioning as a co-developer for tools it was designed to refuse to help build. The actor used sustained, directed, likely incremental prompting to Claude/Claude Code over an extended period, breaking malware development into pieces (encryption, evasion, anti-recovery, delivery, C2) that Claude implemented and the actor could not have written, debugged, or integrated independently. Anthropic's analysis of the malware's development timeline shows a clear evolution -- early basic encryption and evasion, followed by anti-analysis and recovery-prevention code, followed by more advanced delivery mechanisms and command-and-control infrastructure -- consistent with the actor iteratively directing the model through successive capability upgrades rather than requesting a complete ransomware kit in one step. The actor also used a cover framing (branding the tools as for 'educational and research use only') as a persistent pretext, a technique typically used both to influence the AI's judgment during elicitation and to create a fig-leaf defense when marketing the same tools openly on criminal forums.

The Lure & the Tell

There was no lure delivered to an end victim in this case; the 'social engineering' is aimed at the AI model itself, and the tell is the same one Anthropic surfaces across its jailbreak-dependent misuse cases: a technically unsophisticated operator persistently steering an AI assistant, piece by piece, toward outputs (working exploit/malware code) that a single direct request would likely have been refused, wrapped in an 'educational/research' justification used only as a shield rather than an actual use case, given the tools were simultaneously marketed for sale to criminals.

Outcome

Anthropic states it banned the account associated with the GTG-5004 operation as soon as the activity was discovered, alerted its partners, and implemented new detection methods for malware upload, modification, and AI-assisted malware generation to catch similar activity earlier in the future. No law-enforcement arrest, prosecution, or takedown of the actor's dark-web sales infrastructure is reported in Anthropic's disclosure; the actor's underlying identity and any downstream ransomware deployments/victims from buyers of the kits remain undocumented in the public report.

Why It Matters

This case is a concrete, vendor-documented example of AI directly lowering the technical skill floor for building working ransomware -- the kind of cryptography, Windows-internals, and anti-EDR evasion work that previously required years of specialized training was instead produced by an AI model on behalf of an operator who, per Anthropic's own assessment, could not have implemented or debugged those components independently. It illustrates a new category of AI-model-manipulation risk distinct from human-targeted phishing/vishing: the 'target' of the social engineering is the AI's safety training itself, exploited through incremental, disguised, or pretextual prompting to co-develop dual-use malware that is then commercialized to a wider criminal population, multiplying the number of capable-but-unskilled ransomware operators in the ecosystem.

Defenses

Anthropic's stated mitigations: banning the account as soon as the operation was discovered; alerting partners and sharing technical indicators with relevant authorities; and building a tailored classifier plus new detection methods aimed at catching AI-assisted malware upload, modification, and generation earlier and faster. The case argues for AI vendors to monitor for iterative, multi-session malicious code-generation patterns (not just single-prompt refusals), and for defenders generally to treat 'AI has lowered the skill floor for ransomware development' as an active threat-model input rather than a hypothetical.

Sources
Attack Chain & Defense
The sequence the attacker ran
How it could have been stopped
1
Capability targeting: The actor identified specific technical capabilities he could not build himself, including encryption, Windows-internals evasion, and anti-recovery mechanisms, and set out to have an AI model produce each piece rather than attempting to learn or code them independently.
Countering Stage 1: AI vendors can monitor for patterns where a user's requests cluster tightly around known malware-development primitives (encryption, anti-EDR, anti-recovery) even when no single request is overtly malicious.
2
Pretextual framing: Requests to the model were wrapped in an 'educational and research use only' justification, a cover story aimed at the model's own safety judgment and similar in function to a human social-engineering pretext, even though the same tools were being actively sold to criminals.
Countering Stage 2: Treat 'educational/research only' framing as a weak signal on its own, especially paired with requests for production-quality, evasion-focused code, rather than as automatic justification for compliance. The model's own training getting this wrong is exactly the vulnerability being exploited.
3
Incremental, piecemeal elicitation: Rather than asking for a complete ransomware kit in one request, the actor broke development into separate pieces (encryption, then evasion, then anti-recovery, then delivery/C2), each requested and iterated on in its own session, consistent with keeping any single request below a suspicion threshold.
Countering Stage 3: Detection that reasons across a user's full session history, not just single prompts in isolation, is needed to notice when individually-benign-looking requests are cumulatively assembling a harmful capability.
4
Iterative capability escalation: Anthropic's own analysis of the resulting malware shows a staged progression: basic encryption/evasion first, then anti-analysis and recovery-prevention, then more advanced delivery and command-and-control, indicating the actor directed the model through successive upgrades over an extended period rather than a one-shot build.
Countering Stage 4: Monitoring for accounts that show a capability trajectory over time (escalating sophistication across sessions) can flag long-running abuse that a point-in-time review would miss. This is the pattern Anthropic says it used to eventually catch and ban this account.
5
Assembly and packaging: The actor combined the AI-generated components into three commercial tiers (a bare executable, a full RaaS kit with a control panel, and a 'fully undetectable' crypter), representing final assembly and productization work a low-skill actor could plausibly do even without being able to write the underlying code.
Countering Stage 5: Fingerprinting or classifying AI-assisted code artifacts, even after the fact via shared technical signatures across malware samples, can help vendors and researchers link commercialized malware back to a common AI-assisted origin.
6
Distribution and monetization: The finished kits were marketed and sold via dark web forums (Dread, CryptBB, Nulled) and a dedicated .onion site with a ProtonMail contact channel, reaching a wider population of buyers who could deploy the ransomware without any AI assistance of their own.
Countering Stage 6: Standard dark-web-marketplace monitoring by security researchers and law enforcement, plus AI vendors sharing technical indicators with industry partners as Anthropic states it did, helps get takedown/detection signatures out before a kit spreads widely to buyers.
Quick Facts
Victim
Diffuse: other cybercriminals who purchased the ransomware builds on dark web forums (buyers), and by extension any downstream organizations later hit by ransomware built from the kits; no specific named end-victim organization is documented in Anthropic's report
Location
United Kingdom (threat actor); distribution via dark web forums with global buyer reach
Date
2025-01 (active since at least Jan 17, 2025) through 2025-08-27 (Anthropic disclosure/ban)
Impact
Ransomware packages sold for $400-$1,200 USD per Anthropic's three-tier pricing: (1) ransomware DLL/executable - $400, (2) full RaaS kit with PHP console and C2 tooling - $800, (3) Windows 10/11 FUD (fully undetectable) crypter for native binaries - $1,200. No aggregate revenue, victim count, or downstream ransom-payment total is disclosed by Anthropic.
Status
Confirmed
Case Type
Real-World Incident
Sector
Technology & Software
Threat Actor
Unaffiliated Individual
Related

Related Cases

PROMPTSTEAL/LAMEHUG: APT28's LLM-Powered Malware Against Ukraine

Google's GTIG and Ukraine's CERT-UA documented PROMPTSTEAL (aka LAMEHUG), Russian APT28 malware that queries an LLM (Qwen2.5-Coder via the Hugging…

Incident 2025Read →

PromptLock: AI-Generated Ransomware Proof-of-Concept Discovered on VirusTotal

ESET researchers found "PromptLock," a Go-based ransomware sample on VirusTotal that used a locally-run open-weight AI model (gpt-oss:20b via Ollama)…

Incident 2025Read →

OpenAI's "ScopeCreep": Russian-Speaking Actor Used Disposable ChatGPT Accounts to Build C2-Enabled Windows Malware Distributed via a Trojanized "Crosshair-X" Gaming Tool

A Russian-speaking threat actor used disposable, one-conversation ChatGPT accounts to iteratively build and debug a Go-based Windows malware family and…

Incident 2025Read →