surf-lendingnpm
Advisory published Updated
surf-lending is a confirmed malicious npm package (MAL-2026-5808) that steals credentials and exfiltrates sensitive data (malicious version 9.9.9). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in surf-lending (npm)
What this malware does
Sibling of [email protected] campaign (C2 path /surflending/). Sentinel-9.9.9 dep-confusion squat; preinstall node index.js || true exfils env secrets (mnemonic/key/token/blockfrost) to raw C2 2.25.140.71:8443/surflending/npm-confusion. c913 + c252.
On npm install, the package automatically runs node index.js via scripts.preinstall. The script collects host identity (hostname, username, cwd) and filters process.env for keys matching /key|seed|secret|token|private|mnemonic|password|blockfrost|redis|telegram|batcher/i, then POSTs the resulting JSON to https://2.25.140.71:8443/surflending/npm-confusion. Errors are swallowed (|| true) to hide failures. The credential-shaped regex (mnemonic/seed/private/blockfrost) targets crypto-wallet and infrastructure secrets, and the path /surflending/npm-confusion together with the suspicious 9.9.9 version is consistent with a dependency-confusion attack against an internal surf-lending package. Any developer or CI environment installing this package will leak its secrets to the attacker-controlled endpoint.
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Search your lockfiles and build artifacts for surf-lending (version 9.9.9).
If you installed it — respond
surf-lending 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 surf-lending was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
- SafeDep · finder
Detect & block this
O3 blocks surf-lending-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.