# GTG-2002 vibe hacking data extortion via Claude Code

- ID: gtg-2002-vibe-hacking-extortion-2025-08
- Reported: 2025-08-27
- Researcher: Anthropic Threat Intelligence
- Organization: Anthropic
- AI role: attacker_uses_ai_as_operator (AI as operator)
- Confidence in AI involvement: not assessed
- Research / borderline: false
- Last reviewed: 2026-10-20
- Entry page: https://openattacks.ai/attacks/gtg-2002-vibe-hacking-extortion-2025-08/
- Entry JSON: https://openattacks.ai/api/attacks/gtg-2002-vibe-hacking-extortion-2025-08.json
- Browse title: GTG-2002 'vibe hacking' data extortion via Claude Code
- Editorial summary: A criminal operator used Claude Code for reconnaissance, intrusion and data theft, then to help set ransom amounts and prepare extortion messages.
- Evidence class (catalog annotation): Reported campaign
- Source-stated target environments: Not specified
- Stage hunts and conditional defenses: https://openattacks.ai/api/defenses/gtg-2002-vibe-hacking-extortion-2025-08.json

## Technique
Cybercriminal GTG-2002 used Claude Code as active operator for scaled data extortion ('vibe hacking'): recon, credential harvest, network penetration, exfil, then ransom notes threatening data exposure (not classic encryptor). Actor stored preferred TTPs in CLAUDE.md; Claude helped choose ransom amounts from financial data and generated HTML ransom notes embedded in boot process.

## Stack relevance (editorial)
Assessment: attacker\_tool\_only. Editorial applicability reviewed against the catalog source account; not a scan or independent incident verification.
The named AI product is used by the attacker. No reviewed mapping from owning that product to the reported victim conditions is available.
A product mention alone is not a victim-side applicability mapping. Selection does not verify affected versions, permissions or compromise.

## Initial access
Opportunistic via OSINT and scanning of Internet-facing devices; some ops began from compromised VPNs for internal access (vs later GTG-1002)

## AI tooling and models
- [Claude Code](https://github.com/anthropics/claude-code)
- CLAUDE.md TTP guide

## Other tooling
- unknown

## Victims and sectors
At least 17 organizations in ~1 month: government, healthcare, emergency services, religious institutions

## Target geography
- Multiple regions
Multiple target countries are reported, but specific country names are largely redacted.

## Attribution
GTG-2002; financially motivated cybercriminal

## Scale and metrics
≥17 orgs; occasional ransom demands exceeding $500,000

## Attack flow
Catalog reconstruction of the supplied source account. Unknowns and research caveats are preserved.
### step-1: Internet-facing systems are scanned [access]
Some operations also start with compromised VPN access.
Evidence: https://www-cdn.anthropic.com/b2a76c6f6992465c09a6f2fce282f6c0cea8c200.pdf

### step-2: Claude Code assists active intrusion [ai]
The actor stores preferences in CLAUDE.md and uses model help for reconnaissance and credential collection.
Evidence: https://www-cdn.anthropic.com/b2a76c6f6992465c09a6f2fce282f6c0cea8c200.pdf

### step-3: Data is collected and exfiltrated [execution]
The campaign penetrates networks and retrieves information.
Evidence: https://www-cdn.anthropic.com/b2a76c6f6992465c09a6f2fce282f6c0cea8c200.pdf

### step-4: Victims receive extortion demands [impact]
Model assistance supports ransom valuation and HTML demands threatening data exposure.
Evidence: https://www-cdn.anthropic.com/b2a76c6f6992465c09a6f2fce282f6c0cea8c200.pdf

Connections:
- step-1 -> step-2
- step-2 -> step-3
- step-3 -> step-4

## Stage defense and hunting recommendations
Editorial recommendations, not validated coverage. Source-controlled query starters are drafts. Custom-schema examples require telemetry collection and field mapping; absence of a mapping means not assessed. MagicSword policy opportunities require managed Windows scope and enforcement.
### step-1: Web exploitation → host activity
- Visibility: Defender-side logs where collected
- Query origin: catalog_authored; status: draft; log scope: custom_schema
- SIGMA query download: /api/detections/web.sigma.yml
- KQL query download: /api/detections/web.kql
- SPL query download: /api/detections/web.spl
- Hunt hypothesis: Repeated exploit or upload requests are followed by an unexpected server process, file, or outbound connection.
- Required telemetry: Reverse-proxy / WAF request logs; Server process and file events; Outbound DNS / proxy records
- Investigate: Join requests to the affected host and process tree by time and request ID.
- Investigate: Inspect uploaded files and server-spawned shells; distinguish authorized testing from exploitation.
- Limitation: A scan or high request rate alone does not prove compromise or AI use. Host telemetry is needed to confirm execution.
- No direct MagicSword prevention claim is recorded for this stage.

### step-2: Provider-side abuse investigation
- Visibility: Provider / operator records
- Query origin: catalog_authored; status: draft; log scope: custom_schema
- SIGMA query download: /api/detections/provider.sigma.yml
- KQL query download: /api/detections/provider.kql
- SPL query download: /api/detections/provider.spl
- Hunt hypothesis: A model-provider investigation correlates related accounts, repeated offensive requests and shared infrastructure or exposed operator sessions.
- Required telemetry: Provider-owned account / request audit; Abuse-review findings and linked-account context; Lawfully available exposed operator-session evidence
- Investigate: Correlate accounts, request rates, infrastructure and source-described behavior in provider-owned records.
- Investigate: For victim-side defense, pivot to the reported execution or access stage rather than trying to detect attacker-side prompts.
- Limitation: Attacker-side planning is generally absent from victim SIEM logs. These templates require provider-owned audit data and do not identify AI use from a victim process alone.
- No direct MagicSword prevention claim is recorded for this stage.

### step-3: Sensitive data → unusual destination
- Visibility: Defender-side logs where collected
- Query origin: catalog_authored; status: draft; log scope: custom_schema
- SIGMA query download: /api/detections/exfil.sigma.yml
- KQL query download: /api/detections/exfil.kql
- SPL query download: /api/detections/exfil.spl
- Hunt hypothesis: Sensitive reads are followed by outbound transfer, a public artifact, or a tool call to a destination outside the approved workflow.
- Required telemetry: Sensitive resource access / DLP records; Proxy, egress and cloud upload events; Agent / SaaS audit with correlation IDs
- Investigate: Join the resource read and outbound action by session, identity or process, preserving a bounded time window.
- Investigate: Inspect destination ownership, payload classification and the user's intended action; baseline sanctioned sharing.
- Limitation: An outbound connection or high byte count alone is not exfiltration. Encrypted traffic may hide content, and bulk legitimate exports are common.
- No direct MagicSword prevention claim is recorded for this stage.

### step-4: Lure → user action / delivery
- Visibility: Defender-side logs where collected
- Query origin: catalog_authored; status: draft; log scope: custom_schema
- SIGMA query download: /api/detections/phishing.sigma.yml
- KQL query download: /api/detections/phishing.kql
- SPL query download: /api/detections/phishing.spl
- Hunt hypothesis: An impersonating message, ad or website leads to a suspicious download, consent request, pasted command or payment instruction.
- Required telemetry: Email / secure-web-gateway records; Browser redirects, downloads and URL reputation; User reports and downstream execution / identity events
- Investigate: Reconstruct redirect and delivery provenance using original report indicators, without visiting payload URLs.
- Investigate: Correlate the click with the actual download, consent or execution; verify the sender through an independent channel.
- Limitation: Polished text, AI branding and a novel domain do not prove maliciousness or AI generation. Follow-on evidence matters.
- Qualification: Investigate extortion communications alongside the preceding data-access evidence; message polish does not prove AI involvement.
- No direct MagicSword prevention claim is recorded for this stage.


## MITRE ATLAS
Mappings are catalog annotations based on described behavior, not assignments or endorsements by MITRE.
- AML.T0016.002: Generative AI — Claude Code is used as part of the extortion workflow.
  Technique: https://atlas.mitre.org/techniques/AML.T0016.002
  Evidence: https://www-cdn.anthropic.com/b2a76c6f6992465c09a6f2fce282f6c0cea8c200.pdf
- AML.T0102: Generate Malicious Commands — The model supports command-driven intrusion tasks.
  Technique: https://atlas.mitre.org/techniques/AML.T0102
  Evidence: https://www-cdn.anthropic.com/b2a76c6f6992465c09a6f2fce282f6c0cea8c200.pdf

## Defensive notes
EDR + app control on coding-agent spawned shells; hunt boot-process HTML ransom artifacts; restrict agent network egress

## Sources
- https://www-cdn.anthropic.com/b2a76c6f6992465c09a6f2fce282f6c0cea8c200.pdf
