janus-flownpm
Advisory published Updated
janus-flow is a confirmed malicious npm package (MAL-2026-5556) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in janus-flow (npm)
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.
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
Search your lockfiles and build artifacts for janus-flow (version 1.0.0).
If you installed it — respond
janus-flow 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 janus-flow was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks janus-flow-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.