Think Like an Attacker: Why Your npm install Is a Hacker's Dream
summary
Shows how a dormant npm package with a suddenly added post-install script allows attackers to exfiltrate npm/GitHub tokens and AWS keys, then auto-bump and republish dependents for worm-like propagation. Cites the September 2025 “great Shyolu” incident: 500+ developers affected, ~500 npm packages compromised, ~2,500 GitHub tokens leaked and ~$50M in crypto stolen. Describes detection and defense using PMG and vet (CLI + MCP server), static Yara-like rules, sandboxed dynamic analysis and policy-driven CI checks.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:06Risks of trusting npm packages
- 3:40Attackers exploit package trust
- 5:45Dormant packages and typosquatting
- 8:14Attack flow and consequences
- 9:39AI tools' blind spots in packages
- 11:48Shyoulu supply chain attack
- 14:17Steps to avoid being hacked
- 16:28Introducing PMG and Vet
- 22:24Vet in CI/CD and MCP servers
- 24:36Malware analysis at Safeep
- 26:02Is package paranoia justified
- 27:28Closing remarks
- 28:10Q&A on GitHub Actions checks
related talks
39m"Malice in the Modules" - How NPM Became a Supply-Chain Battleground?
29mAll your packages are belong to us - Protecting your npm dependencies
53mLessons From NPM's Dark Side: Preventing the Next Shai-Hulud
23mProtecting Your npm Dependencies
37mSponsored Session: The Simple, Yet Lethal, Anatomy of a Software Supply Chain Attack
25mWhen the supply chain hits a sour note
41mMalicious Modules on npm - a series of unfortunate events
21mSupply Chain Attacks on Open Source: What's Happening, What...