Which versions of flowcardano are malicious?

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

How do I remediate flowcardano if I installed it?

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

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

Yes — flowcardano is associated with the IN-MAL-2026-006601, IN-MAL-2026-006602, GHSA-7wqh-42c8-vqcx 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 flowcardano 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 flowcardano (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 flowcardano across your stack and pipelines.

Malicious package

flowcardanonpm

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

MAL-2026-5805

Immediate action

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

npm uninstall flowcardano

What this malware does

flow/surf-lending DeFi cred-exfil campaign sibling (c1655). Cardano-themed Sentinel-9.9.9 dependency-confusion squat. preinstall node index.js || true exfils env secrets (mnemonic/private-key/token/blockfrost) to raw C2 2.25.140.71:8443/surflending/npm-confusion (same C2 as flow-lending/surf-lending/flow-lending-sdk/bodega-sdk/flowdefi). Automated analysis timed out; classified by campaign attribution (verified identical siblings). No-renotify.

On npm install, package.json's preinstall hook runs node index.js, which collects host identity (os.hostname(), os.userInfo().username, cwd) and scrapes process.env for any key matching the regex key|seed|secret|token|private|mnemonic|password|blockfrost|redis|telegram|batcher, then POSTs the resulting JSON to https://2.25.140.71:8443/surflending/npm-confusion (index.js lines 13-17). The destination is a bare IP rather than any publisher- or vendor-owned host, and the request path (/surflending/npm-confusion) self-describes the intent as a dependency-confusion exfiltration channel. The package name flowcardano impersonates Cardano-ecosystem tooling and is published at version 9.9.9, the canonical dependency-confusion bait version chosen to outrank legitimate internal packages in resolver order. Any developer or CI agent that installs this package leaks credential-shaped environment variables (wallet seeds/mnemonics, private keys, Blockfrost / Telegram / Redis tokens, generic API tokens and passwords) along with host identifiers 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)

21379b9b1e9f6a64a18a806531d9f1bb22394694b092eb2b26b6b4d356bd5a4a

649a634e3752b14f92fe6c92e11681dc8d16ba04019196b1c10cdf5968d74607

becf0970b25d3fece917cf67cf2734c2109c5b8b900f2c63f8f78679b7f5eae9

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 flowcardano (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 flowcardano across your stack and pipelines.
If you installed it — respond
flowcardano 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 flowcardano 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 flowcardano 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. flowcardano 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-006601IN-MAL-2026-006602GHSA-7wqh-42c8-vqcx

References

Credits

Amazon Inspector · finder
SafeDep · finder

Detect & block this

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