← ClaudeAtlas

npm-supply-chain-auditlisted

Audit npm projects for malicious packages, supply chain attacks, typosquatting, and IOCs. Use when user wants to check for compromised dependencies, suspicious packages, or verify project security.
omar16100/skills · ★ 0 · AI & Automation · score 68
Install: claude install-skill omar16100/skills
# npm Supply Chain Security Audit Perform a thorough security audit of npm dependencies, checking for malicious packages, compromised versions, typosquatting, and indicators of compromise (IOCs). ## Input Handling - If `$ARGUMENTS` contains a **package name or version** (e.g., `axios@1.14.1`, `plain-crypto-js`): research that specific package/version for known attacks - If `$ARGUMENTS` contains a **project path**: audit that project's dependencies - If `$ARGUMENTS` is empty: audit the current working directory ## Phase 1: Package Research (if specific package/version given) Use web search to investigate: 1. **Registry check**: Does this exact version exist on npm? Was it published and yanked? 2. **Security advisories**: Search Snyk, Socket.dev, GitHub Advisories, npm advisories for CVEs or reports 3. **Typosquatting analysis**: Is the package name suspiciously similar to a legitimate package? 4. **Publisher analysis**: Who published it? Is the publisher account suspicious (new, ProtonMail, no other packages)? 5. **Attack timeline**: If malicious, determine exposure window and attack vector Report findings in a structured table format. ## Phase 2: Local Dependency Scan Search the target project (the current working directory if no path given) for: ### 2a. Lock File & Manifest Search - Search all `package.json` files for the target package in dependencies, devDependencies, optionalDependencies, peerDependencies - Search all `package-lock.json`, `yarn.lock`, `pnpm-lock