Which versions of janus-flow are malicious?

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

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

Remove janus-flow from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound network activity or persistence. Use O3 Security's dependency scanner to confirm the package and its artifacts are fully purged across your stack.

Is janus-flow part of a known attack campaign?

Yes — janus-flow is associated with the IN-MAL-2026-005400 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

Can O3 Security detect janus-flow in my codebase?

Yes. O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, blocking janus-flow and packages like it before any post-install script runs.

Malicious package

janus-flownpm

Malicious code in janus-flow (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-5556

Immediate action

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

npm uninstall janus-flow

What this malware does

On npm install, the package's postinstall hook (node postinstall.js 2>/dev/null || true) silently runs a credential harvester against the installer machine. postinstall.js collects os.hostname(), os.userInfo().username, process.cwd(), platform, and timestamp; iterates process.env for keys matching /KEY|SECRET|TOKEN|PRIVATE|MNEMONIC|PASSWORD|RPC|ALCHEMY|INFURA|DATABASE|WALLET/i; reads .env files from multiple paths and ~/.npmrc; and POSTs the resulting JSON blob to https://193.203.169.109:8443/c/janus-flow with rejectUnauthorized:false (TLS verification disabled). The lifecycle command's stderr redirect plus || true suppresses any failure from the installer. The package's advertised purpose ("Flow blockchain utilities") is a cover story: index.js exports {} and provides no functionality, so the only effect of installing this package is the credential beacon. The destination is a bare IP unrelated to any Flow blockchain publisher and matches no legitimate vendor endpoint.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

2d33c10c068a69d14d0333b93de7745caffd62013c57de6c55f20a6b53ffdcb1

Frequently asked questions

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

Campaign

IN-MAL-2026-005400

References

npmjs.com

Credits

Amazon Inspector · finder

Scan your dependencies

O3 Security blocks malicious packages like this at install time and in CI.

Supply-chain protection