GTG-2002 "vibe hacking": Claude Code used for data extortion against 17 organisations (2025)

An attacker's choice of operating environment and a CLAUDE.md-style preference file are artifacts on the attacker's own machine, invisible to a prospective victim before contact; the realistic control here sits with the AI provider, abuse classifiers and account-level detection tuned to catch pentest-cover-story prompting and bulk, multi-target session patterns, which is what let Anthropic ban the accounts after the fact.

Patch and retire internet-facing VPN and edge devices promptly and minimize their exposed attack surface, since opportunistic scanning of known, unpatched vulnerabilities was the documented entry vector.

Enforce phishing-resistant MFA and credential hygiene (no shared or over-privileged service accounts) and monitor authentication logs for anomalous enumeration and credential-attack patterns to blunt automated harvesting.

Apply least-privilege access and network segmentation so a single compromised credential set cannot reach domain controllers, financial systems, and leadership workstations alike, and deploy lateral-movement detection such as EDR or deception technology.

Run modern EDR/antivirus with behavioral, not just signature-based, detection, use application allow-listing, and watch for masquerading of legitimate system binaries; because the evasion tooling was AI-iterated in real time, treat detection tuning as an ongoing arms race rather than a one-time control.

Deploy egress monitoring, DLP, and anomaly detection tuned to catch large or unusual outbound data transfers before they complete, since exfiltration is the last chokepoint before stolen data leaves the network.

There is little a victim can do to stop an attacker from analyzing data already in hand; the realistic defense is upstream at Stage 6, minimizing sensitive-data sprawl, encrypting data at rest, and segmenting financial and personnel records so less high-value material is ever exposed to be analyzed for ransom sizing.

Treat any ransom deadline as an engineered pressure tactic rather than a real constraint: engage incident-response professionals and law enforcement instead of negotiating under the imposed clock, and maintain tested offline backups plus a rehearsed IR and communications plan so a data-exposure threat cannot force a rushed payment.