flow-lending-sdknpm
flow-lending-sdk is a confirmed malicious npm package (MAL-2026-5804) 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 flow-lending-sdk (npm)
What this malware does
Continuation of the flow/surf-lending DeFi cred-exfil campaign (c1655). Sentinel-9.9.9 depconf squat; preinstall node index.js || true exfils env secrets (mnemonic/private-key/blockfrost) to raw C2 2.25.140.71:8443/surflending/npm-confusion (same C2). Companions bodega-sdk/flowdefi verified identical. No-renotify.
[email protected] declares preinstall: node index.js || true in package.json, causing index.js to execute automatically on npm install. The script collects host identity (hostname, username, cwd) and iterates process.env, filtering for keys matching /key|seed|secret|token|private|mnemonic|password|blockfrost|redis|telegram|batcher/i — i.e., wallet seed phrases, private keys, API tokens, and infrastructure credentials. The collected JSON is HTTPS-POSTed to the bare IP 2.25.140.71:8443 at path /surflending/npm-confusion. The package ships no real SDK functionality (description is the placeholder flow-lending-sdk SDK, version is 9.9.9), and the exfil URL path explicitly names this as a dependency-confusion attack — almost certainly targeting developers of Cardano/Flow lending infrastructure who expect a private internal package of this name.
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
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for flow-lending-sdk (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 flow-lending-sdk across your stack and pipelines.
If you installed it — respond
flow-lending-sdk 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 flow-lending-sdk 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 flow-lending-sdk 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
Campaign
References
Credits
- Amazon Inspector · finder
- SafeDep · finder
Detect & block this
O3 blocks flow-lending-sdk-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.