Which versions of ethereum-kit-9 are malicious?

The following npm versions of ethereum-kit-9 are flagged malicious: 1.25.36. Treat any of these as compromised.

How do I remediate ethereum-kit-9 if I installed it?

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

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

Yes — ethereum-kit-9 is associated with the IN-MAL-2026-005351 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 ethereum-kit-9 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 ethereum-kit-9 (version 1.25.36). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ethereum-kit-9 across your stack and pipelines.

Malicious package

ethereum-kit-9npm

Malicious code in ethereum-kit-9 (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-5356

Immediate action

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

npm uninstall ethereum-kit-9

What this malware does

Crypto/SSH/wallet stealer, blockchain-helper-0 campaign sibling (c960+). postinstall auto-execs, src/index.js harvests ~/.ssh/id_rsa+id_ed25519+Sol/Eth/BTC/Tron/Sui/Aptos wallets+.env+seeds, self-labels "CRYPTO STEALER", exfils to SAME Telegram bot 8227918239 chat 6433587894 (not rotated). Campaign now uses inflated version (1.25.36) not 1.0.0.

On npm install, the package's postinstall hook loads src/index.js, which after a short delay and a sandbox/CI evasion check enumerates the installer's home and project directories for sensitive files and uploads each one to api.telegram.org using a hardcoded bot token and chat_id. Targeted paths include SSH private keys (~~/.ssh/id_rsa, id_ed25519), crypto wallet keystores and data directories for Solana, Ethereum (~~/.ethereum/keystore), Bitcoin, Tron, Sui, and Aptos, and project secrets (.env,.env.local, mnemonic.txt, seed.txt, wallet.json, private.key, secrets.json). The payload skips execution when CI/sandbox indicators are present (CI=true, GITHUB_ACTIONS, NODE_ENV=test/development, usernames like runner/sandbox/docker/jenkins, and 12-hex-char container hostnames) to evade analysis. The package name and generic 'Utility library' description with placeholder author impersonate Ethereum tooling to lure developers.

Malicious versions

1 flagged

1.25.36

Indicators of compromise (SHA-256)

fca6873d6bb09703d4ceba095e845845ec40ca4274def05870ed6d59b90fdf6a

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 ethereum-kit-9 (version 1.25.36). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ethereum-kit-9 across your stack and pipelines.
If you installed it — respond
ethereum-kit-9 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 ethereum-kit-9 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 ethereum-kit-9 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. ethereum-kit-9 on npm has been identified as a malicious package (version 1.25.36 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-005351

References

Credits

Amazon Inspector · finder
SafeDep · finder

Detect & block this

O3 blocks ethereum-kit-9-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