HomeRepo ScannerPricingBlogDownload
🚨 Breaking Threat Advisory

61,764 GitHub Repos Probed & 771 Poisoned npm Hooks: Why Attackers Are Now Hunting Your AI Coding Keys

Starting on November 10, 2026, threat actors launched one of the largest coordinated software supply-chain campaigns ever observed on GitHub (tracked across the security community as wfx-loot). Rather than exploiting a vulnerability in GitHub itself, attackers weaponized 4,837 previously leaked developer and bot tokens to systematically probe tens of thousands of repositories, inject self-erasing secret-stealers, and—most critically—plant workstation traps that trigger on npm install.

61,764Repositories Probed for Write Access
8,093Repos Injected with Malicious Commits
1,970+Confirmed Secret-Stealer Executions
771Repos Poisoned with Workstation postinstall Traps

Immediate Check: Before cloning or running npm install on unfamiliar repositories this week, run them through our Free Instant GitHub Supply-Chain Scanner.

1. What Made This Attack Different: AI Coding Keys Are Now Tier-1 Loot

Historically, supply-chain payloads focused almost exclusively on cloud IAM credentials and package registry tokens. Analysis of the ~1,500-line shell dropper deployed in the November 2026 campaign reveals a major shift in attacker economics: autonomous AI coding credentials are now explicitly targeted alongside AWS, Azure, and GCP keys.

Once executed—either inside a CI runner or directly on a developer's laptop—the script aggressively harvests:

Why target AI keys? Because in 2026, a stolen enterprise Anthropic or OpenAI key doesn't just carry high API billing limits—it often grants access to organization workspaces, fine-tuned context, and automated agent pipelines. Worse still, developers increasingly allow autonomous coding agents (Claude Code, Cursor, Windsurf, Cline, Aider) to clone repositories and run npm install automatically without human inspection of package.json lifecycle hooks.

2. Anatomy of the 5-Minute "Hit-and-Run" & Workstation Trap

The campaign reached high-profile organizations globally—including accounts associated with Fortune 100 enterprises and government institutions in the United States and France—by combining three stealth techniques:

  1. Automated Write-Access Probing: Compromised accounts opened innocuous pull requests titled "docs: dependency audit notes" from branches such as wfx-docs or ci-check-XXXX to map where stolen tokens still held write privileges.
  2. Workstation postinstall Droppers (771 Repos): Attackers dropped a hidden shell script (.ci-xxxxxx.sh) into the repository root and registered a postinstall hook inside package.json. Any developer—or AI coding agent—running npm install executed the credential harvester locally on their own machine.
  3. Self-Reverting Anti-Forensics: In CI workflow attacks, the script exfiltrated compressed credentials, reverted its own commit, and deleted the GitHub Actions run logs within minutes—often leaving only a missing workflow run number (e.g., jumping from Run #41 to Run #43) as evidence.
// Typical workstation trap observed across 771 poisoned repositories:
{
  "name": "example-utility",
  "scripts": {
    "build": "tsc",
    "postinstall": "bash ./.ci-8f4a21c.sh --silent || true"
  }
}

3. Cloud Backdoors That Survive Password & Key Rotation

Simply rotating leaked API keys is not sufficient if an environment executed the payload. Where cloud permissions allowed, the script attempted to establish durable persistence:

4. Key Indicators to Audit Right Now

Artifact TypeObserved PatternRecommended Action
Pull Request Titledocs: dependency audit notesAudit repo write logs & rotate all exposed secrets
Branch Nameswfx-docs, ci-check-[0-9]{4}, chore/[a-z0-9]{8}Inspect git reflog for reverted commits
Workstation TrapHidden .ci-*.sh + package.json postinstallIsolate machine, rotate .env, SSH, Cloud & AI keys
GitHub Actions HistorySkipped / missing sequential run_number entriesReview GitHub Organization Audit Log for workflows.delete_workflow_run

5. How ClaudeArmor Protects Your Workstation & AI Coding Agents

Cloud-only repository scanners miss attacks that inject and self-delete in under five minutes—and they cannot stop an AI coding agent on your laptop from running a poisoned postinstall script on a freshly cloned repo. We built ClaudeArmor specifically for this threat model:

🛡️ Lock Down Your Workstation Before Your Next npm install

Test any public repository free right now, or lock in ClaudeArmor Early-Bird Launch Pricing (from $27) for continuous 24/7 protection across your workstation and all 20 AI coding agents.