Which versions of flowdefi are malicious?

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

How do I remediate flowdefi if I installed it?

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

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

Yes — flowdefi is associated with the IN-MAL-2026-006608, IN-MAL-2026-006607, GHSA-24j3-x8g2-c23q 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 flowdefi 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 flowdefi (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 flowdefi across your stack and pipelines.

Malicious package

flowdefinpm

flowdefi is a confirmed malicious npm package (MAL-2026-5806) 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 flowdefi (npm)

MAL-2026-5806

Immediate action

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

npm uninstall flowdefi

What this malware does

flow/surf-lending DeFi cred-exfil campaign sibling (c1655). preinstall node index.js || true exfils env secrets to raw C2 2.25.140.71:8443/surflending/npm-confusion (verified identical). No-renotify.

On npm install, the package's preinstall hook executes node index.js, which collects the host's os.hostname(), os.userInfo().username, current working directory, and all environment variables whose names match a credential-shaped regex (key|seed|secret|token|private|mnemonic|password|blockfrost|redis|telegram|batcher). The harvested data is POSTed as JSON to the bare IPv4 endpoint https://2.25.140.71:8443/surflending/npm-confusion. The package metadata is a stub (description: "flowdefi SDK", no repository, no author, version pinned to 9.9.9 — a classic dependency-confusion high-version trick), and the exfil path is literally named /surflending/npm-confusion, indicating a dependency-confusion attack targeting an internal package named flowdefi, likely belonging to a Cardano/DeFi project (the regex specifically targets Cardano-ecosystem secrets such as blockfrost, mnemonic, seed, batcher). Installing this package on a developer or CI machine will leak wallet seed phrases, private keys, API tokens, and other secrets to the attacker.

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)

97aab6ad6cd465ed64cf6bb5151508a6fac2ba7b26b98d5732f0ed5d0c594d13

b5e410fabd766facf41c970113c2a0a1b06b67b82521ffae20a32328cd74994e

224957c95a54d8bc6cdfa2f0153483240125d9879182a51d3accbd4137cd7465

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 flowdefi (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 flowdefi across your stack and pipelines.
If you installed it — respond
flowdefi 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 flowdefi 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 flowdefi 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. flowdefi 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-006608IN-MAL-2026-006607GHSA-24j3-x8g2-c23q

References

Credits

Amazon Inspector · finder
SafeDep · finder

Detect & block this

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