Developer IDEs Are C2 Channels — Three Weaponization Paths, One Week
The Convergence
Three research teams disclosed in a single week that developer coding environments are now initial access vectors on par with malicious packages. SpecterOps published Ouroboros, weaponizing VS Code Dev Tunnels in Rust to pivot off Teams and Azure tokens. Straiker disclosed NomShub: a Cursor sandbox escape via shell builtins, ~/.zshenv persistence, remote tunnel. A separate researcher showed Claude Code Hooks (.claude/settings.json) reproduce the Lazarus VS Code tasks backdoor pattern. Any malicious repo cloned into Claude Code runs arbitrary shell on SessionStart.
The developer workstation is now the new DMZ. The tools developers trust most are the entry point.
The 60-Second Kill Chain
Adan Alvarez handed Claude Code a leaked IAM key with no AWS-specific guidance and observed full S3 exfiltration in roughly sixty seconds. Success rate: 58 percent, seven of twelve runs. Every successful run followed the same six phases. GetCallerIdentity, policy enumeration, credential recovery, AssumeRole, bucket enumeration, exfiltration. The determinism is detectable. It is only detectable if alerting fires faster than CloudTrail's hardcoded 5-minute log delivery delay.
The Scanner Failure
Trail of Bits bypassed every major AI skill scanner in a few hours. ClawHub, Cisco, skills.sh — the three commercial offerings, all of them. Methods: 100K newlines, payload embedding in .docx and .pyc, prompt injection against the guard models. Their recommendation reads avoid public skill marketplaces entirely. Anthropic's own MS Office skills use LD_PRELOAD with C code embedded in a docstring. The official skills contain the primitives attackers would plant.
The Supply Chain Compromise
TeamPCP, tracked as UNC6780, compromised the LiteLLM, BerriAI, Trivy, and Checkmarx repositories to plant SANDCLOCK and steal AWS keys and GitHub tokens from build environments. Many security teams run these tools inside their own CI/CD. The targeting was the AI orchestration layer specifically. That is the same layer where scanning has been demonstrated broken.
Cross-Source Pattern
Kaspersky's honeypot work validates the demand side. A Raspberry Pi posing as an AI server was indexed by Shodan in 3 hours and pulled 113K requests per month. 23 percent targeted AI-specific paths: /api/tags, /v1/models, /.cursor/rules, /.well-known/mcp.json. Attackers are fingerprinting AI development infrastructure now.
Detection Architecture
| Vector | Detection Approach | Gap |
|---|---|---|
| Claude Code Hooks | Hunt .claude/settings.json with hook entries | No default EDR signature |
| VS Code Dev Tunnels | Outbound to *.devtunnels.ms | Often allowlisted |
| Cursor NomShub | .cursor/rules/ from untrusted repos | No SIEM ingest |
| AWS agentic exfil | Honeytokens + EventBridge on GetCallerIdentity | CloudTrail 5-min delay |
What to do
Hunt for .claude/settings.json, .cursor/rules/, and VS Code Dev Tunnel processes across all developer endpoints today
Deploy AWS honeytokens in S3 buckets, code repos, and CI environments with EventBridge alerting on GetCallerIdentity this week
Ban public AI skill marketplaces (skills.sh, ClawHub) at the proxy/EDR level and stand up an internal signed registry within 30 days
Pin LiteLLM, BerriAI, Trivy, and Checkmarx by hash; rotate any AWS/GitHub credentials these tools accessed since Q1 2026