Which versions of surf-lending are malicious?

The following npm versions of surf-lending are flagged malicious: 9.9.9. Treat any of these as compromised.

How do I remediate surf-lending if I installed it?

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.

I already installed surf-lending — how do I know if it already compromised me?

If surf-lending 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.

Is surf-lending part of a known attack campaign?

Yes — surf-lending is associated with the IN-MAL-2026-006606, IN-MAL-2026-006605, GHSA-6762-f2rg-qwfv campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find surf-lending across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for surf-lending (version 9.9.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging surf-lending across your stack and pipelines.

Malicious package

surf-lendingnpm

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)

MAL-2026-5808

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall surf-lending

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

1 flagged

9.9.9

Indicators of compromise (SHA-256)

0673929ecbf78a2eefece81336bea6445736f60e2bced40cd1c0da7384438dfc

2ee48ee7b6045907414fd157235c904e9de41a64666deda286a011e0abc17b6e

d146bef145fcfc130e133a5c859ad346e934154820dc99baed00d5a4ae7304b9

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for surf-lending (version 9.9.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging surf-lending across your stack and pipelines.
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 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 surf-lending 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

No. surf-lending on npm has been identified as a malicious package (version 9.9.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-006606IN-MAL-2026-006605GHSA-6762-f2rg-qwfv

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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database