npm-scan-plus 🔒

Security scanner for npm packages - Pre and post-install scanning for malicious code, supply chain attacks, and obfuscated code.

Why We Built This

npm package supply chain attacks are increasing at an alarming rate. Recent examples include:

• TanStack (May 2026): Malicious package published to npm registry containing cryptocurrency stealing code distributed to thousands of applications. (InfoQ)
• event-stream (2018): Maintainer deliberately added malicious code to steal cryptocurrency wallet keys from Copay users
• ua-parser-js (2021): Compromised package with cryptomining malware affecting millions of downloads
• Colors.js / Faker.js (2022): Maintainer intentionally sabotaged popular packages

These attacks succeed because:

• Developers trust npm packages without verification
• No automated scanning before install
• Obfuscated code hides malicious intent
• Typosquatting confuses developers

npm-scan-plus was built to automatically detect these threats before they reach your project.

Features

Pre-Install Scanning

• ✅ Blocklist Check - Known malicious packages (event-stream, flatmap-stream, etc.)
• ✅ Typosquatting Detection - Similar names to popular packages (lodash vs lodsh)
• ✅ Vulnerability Database Check
  • OSV (Google's Open Source Vulnerabilities)
  • GitHub Advisory Database
  • npm Audit
• ✅ License Risk Analysis - Warns about GPL, proprietary, or missing licenses
• ✅ Maintainer Trust Scoring - Identifies known trusted maintainers
• ✅ Repository Validation - Verifies repo URL matches package
• ✅ Package Integrity - Hash verification from npm registry
• ✅ Size Anomaly Detection - Flags packages > 50MB
• ✅ Deprecated Dependencies - Warns about request, moment, underscore

Post-Install Scanning

• ✅ Obfuscation Detection - base64, eval(), hex encoding
• ✅ Malicious Pattern Detection - env exfil, shell exec, crypto mining
• ✅ Suspicious Scripts - postinstall, preinstall analysis
• ✅ Sensitive Files - .env, .ssh, credentials detection

Installation

Option 1: npx (run without installing)

# Scan a package before installing
npx npm-scan-plus pre install <package>

# Full automatic wrapper (pre-scan + install + post-scan)
npx npm-scan-plus-wrap install <package>
npx npm-scan-plus-wrap install  # install from package.json

Option 2: Install globally (recommended for frequent use)

npm install -g npm-scan-plus

# Then use directly
npm-scan-plus pre install <package>
npm-scan-plus-wrap install lodash
npm-scan-plus-wrap install  # install from package.json

Quick Start: Automatic Wrapper

The recommended way to use npm-scan-plus is with the automatic wrapper:

# Install a package with automatic pre + post scan
npm-scan-plus-wrap install lodash

# Install multiple packages
npm-scan-plus-wrap install lodash axios express

# Install all dependencies from package.json
npm-scan-plus-wrap install

The wrapper automatically:

1. 🔍 Pre-install scans each package
2. 📥 Runs npm install
3. 🔍 Post-install scans node_modules

Manual Usage

If you prefer manual control:

Pre-install scan

npm-scan-plus pre install <package>
npm-scan-plus pre install axios --version 1.6.0
npm-scan-plus pre install lodash -V  # verbose output

Post-install scan

npm-scan-plus post
npm-scan-plus post --folder ./node_modules

Blocklist management

npm-scan-plus blocklist list
npm-scan-plus blocklist add <package>
npm-scan-plus blocklist remove <package>

Detection Patterns

Obfuscation

• eval() with atob/fromCharCode
• Base64 encoded strings
• Hex/unicode encoded characters

Malicious Behavior

• Environment variable access (KEYS, SECRETS, TOKENS)
• Network requests to IP addresses or external code hosting
• Child process execution
• Crypto mining pool connections
• Keylogging code

Suspicious Scripts

• postinstall/preinstall with complex shell commands
• curl/wget downloads
• Packages scanning directories outside scope

Environment Variables

• GITHUB_TOKEN - For higher GitHub Advisory API rate limits

Development

# Build
npm run build

# Test
npm test

# Lint
npm run lint

Security Threats Detected

License

MIT

Developed by Chris Bunting <cbuntingde@gmail.com>