AI Security Review
scanned 2h ago · by lpm-firewall-aiThe package executes a postinstall credential stealer. It harvests environment variables, local credential files, and browser wallet extension storage, then exfiltrates them to Telegram.
Decision evidence
public snapshot- package.json defines postinstall: node install.js, so attack runs during npm install.
- install.js embeds Telegram bot token/chat id and posts to api.telegram.org.
- install.js collects secret-like env vars and then includes env_all with every environment variable in a gzipped JSON document.
- install.js reads credential files including .npmrc, .git-credentials, kube config, gcloud, docker, .netrc, and env-pointed credential files.
- install.js searches Chrome extension storage for MetaMask/Trust Wallet and archives vault directories with tar or PowerShell Compress-Archive.
- install.js uses a /tmp .dbc_lk cooldown lock to limit repeated reporting from the same host.
- index.js only re-exports the legitimate debug dependency.
- No evidence of destructive file deletion beyond temporary archive cleanup.
Source & flagged code
6 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgSource appears to send environment or credential material to an external endpoint.
install.jsView on unpkg · L6A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
install.jsView on unpkg · L6A single source file combines environment access, network access, and code or shell execution; review context before blocking.
install.jsView on unpkg · L6