Which versions of flow-lending are malicious?

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

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

flow-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 flow-lending — how do I know if it already compromised me?

If flow-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 flow-lending part of a known attack campaign?

Yes — flow-lending is associated with the IN-MAL-2026-006611, IN-MAL-2026-006612, GHSA-pgcr-8w67-72j9 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 flow-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 flow-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 flow-lending across your stack and pipelines.

Malicious package

flow-lendingnpm

flow-lending is a confirmed malicious npm package (MAL-2026-5803) 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 (npm)

MAL-2026-5803

Immediate action

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

npm uninstall flow-lending

What this malware does

Sentinel-high (9.9.9) dependency-confusion squat of an internal Cardano/DeFi lending pkg. preinstall node index.js || true auto-execs a credential exfil: harvests env secrets (mnemonic/private key/token/blockfrost API key) and POSTs to raw attacker C2 2.25.140.71:8443/surflending/npm-confusion. 2-pkg campaign (flow-lending + surf-lending). c913 + c252.

On npm install, the package's preinstall lifecycle hook executes index.js, which collects host identity (hostname, username, cwd) and enumerates process.env, filtering keys against the regex /key|seed|secret|token|private|mnemonic|password|blockfrost|redis|telegram|batcher/i. The collected JSON is POSTed over HTTPS to a hardcoded bare IP destination (https://2.25.140.71:8443/surflending/npm-confusion). The package provides no legitimate functionality; the path component 'surflending/npm-confusion' and the 9.9.9 version (a version-bump pattern used to win dependency-confusion resolution) indicate a directed dependency-confusion attack against an internal Cardano/SundaeSwap-related package name. Any installer with wallet-related secrets in environment variables (mnemonics, private keys, blockfrost tokens, telegram bot tokens, redis credentials, batcher keys) loses them at install time.

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)

244fb3d5df39fbdba24f9a22b86d0bca43667f3376a9529d5cc84e411f11a28f

82e6486823dda6ec2719a9f76200cd47c559c51f1db0be144edf32fce5c9969f

31f3b9a8a1c9a108f544556d9f0ed2d1642e847bfe36ba050aab0011fb9d731d

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 flow-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 flow-lending across your stack and pipelines.
If you installed it — respond
flow-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 flow-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 flow-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. flow-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-006611IN-MAL-2026-006612GHSA-pgcr-8w67-72j9

References

Credits

Amazon Inspector · finder
SafeDep · finder

Detect & block this

O3 blocks flow-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