Which versions of janus-erc20 are malicious?

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

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

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

If janus-erc20 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.

Is janus-erc20 part of a known attack campaign?

Yes — janus-erc20 is associated with the IN-MAL-2026-005703, GHSA-w6mr-3c22-93v5 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 janus-erc20 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for janus-erc20 (version 1.0.0).

Malicious package

janus-erc20npm

Advisory published Jun 11, 2026Updated Jun 16, 2026

janus-erc20 is a confirmed malicious npm package (MAL-2026-5614) 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-erc20 (npm)

MAL-2026-5614

Immediate action

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

npm uninstall janus-erc20

What this malware does

On npm install, postinstall.js harvests installer secrets and POSTs them to 193.203.169.109:8443/c/janus-erc20 over HTTPS with TLS verification disabled (rejectUnauthorized:false). The script (1) collects hostname, username, and cwd, (2) iterates process.env and filters keys matching /KEY|SECRET|TOKEN|PRIVATE|MNEMONIC|PASSWORD|RPC|ALCHEMY|INFURA|DATABASE|WALLET/i, (3) reads .env files from cwd, parent directories, and the home directory, and (4) reads ~/.npmrc (which contains npm auth tokens) and ~/.config/ipor-fusion/config.json. Errors are silenced with 2>/dev/null||true. The main index.js is empty — the package has no legitimate ERC20 functionality and exists solely to deliver the postinstall harvester. The targeted IPOR Fusion config path plus the generic blockchain-sounding name indicates the package is positioned as a namespace lure against IPOR Fusion / DeFi developers.

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

1.0.0

Indicators of compromise (SHA-256)

728f3d5af5a999be016a49283fff2c5cedc0c5df445d2f078f1f9817dde22334

6e537c421c5b4b7f2450374573623759822628bfa17500279b6db5a46616835c

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for janus-erc20 (version 1.0.0).
If you installed it — respond
janus-erc20 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-erc20 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

No. janus-erc20 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-005703GHSA-w6mr-3c22-93v5

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks janus-erc20-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