permit2npm
permit2 is a confirmed malicious npm package (MAL-2026-13775) that steals credentials and exfiltrates sensitive data. Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in permit2 (npm)
What this malware does
permit2 is a malicious npm package that squats the bare name of Uniswap's Permit2 token-approval system (whose legitimate npm distribution is the scoped @uniswap/permit2-sdk), advertising itself as a "smart contract development toolkit." The package contains no real functionality — the published tarball ships only a package.json and an install-time payload (index.js), which both preinstall and postinstall execute via node index.js, so it runs automatically on npm install.
The payload is a more aggressive variant of the infostealer used across the mssjeep843 DeFi-impersonation campaign and exfiltrates to the same webhook.site endpoint. It collects environment variables whose names match a broadened secret pattern (KEY|TOKEN|SECRET|PASS|PRIVATE|MNEMONIC|RPC|AWS|GITHUB|NPM|KUBE|VAULT|AUTH|PGP|GPG|SEED|WALLET|BEARER|API|INFURA|ALCHEMY|HELIUS|QUICKNODE|ANKR|PRIVATE_KEY) and, rather than merely listing credential directories, reads and exfiltrates the full contents (up to 4000 bytes each) of a wide set of credential and key files: ~/.aws/credentials and ~/.aws/config, SSH private keys (~/.ssh/id_rsa, ~/.ssh/id_ed25519) and ~/.ssh/config, ~/.kube/config, ~/.docker/config.json, ~/.netrc, ~/.pgpass, ~/.npmrc, ~/.pypirc, ~/.gitconfig, ~/.git-credentials, GCP application-default and legacy credentials, Solana/Anchor keypairs (id.json), NEAR credentials, the Sui keystore, up to three Foundry keystore files, and .env/.env.local/.env.production/.env.development/secrets.env from the current working directory. It also captures the hostname, username, cwd and platform. The JSON is POSTed over HTTPS to https://webhook.site/326b0891-2093-4800-a4c1-686ce3e07b09, with errors swallowed so the install never visibly fails. Any host that installed this package should treat SSH keys, cloud credentials, wallet keystores and .env secrets as compromised and rotate them.
Malicious versions
Every published version of this package is considered malicious — remove it entirely.
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for permit2 (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging permit2 across your stack and pipelines.
If you installed it — respond
permit2 is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If permit2 was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks permit2 before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Credits
- SafeDep · finder
Detect & block this
O3 blocks permit2-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.