Which versions of blockchain-helper-0 are malicious?

The following npm versions of blockchain-helper-0 are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate blockchain-helper-0 if I installed it?

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

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

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

Malicious package

blockchain-helper-0npm

Malicious code in blockchain-helper-0 (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-5352

Immediate action

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

npm uninstall blockchain-helper-0

What this malware does

Note: This report is updated by a verification record

Crypto/SSH/wallet stealer (self-labeled "CRYPTO STEALER"). postinstall scripts/postinstall.js auto-execs, src/index.js harvests ~/.ssh/id_rsa + wallet keys/seeds + env and exfils to hardcoded Telegram bot 8227918239:AAGEMDrBZluDsBBYPxfSyMuv2l3FY8cZCcs chat 6433587894. Auto-exec + hardcoded attacker Telegram exfil; "blockchain-helper" identity has no reason to read SSH/wallet keys.

The package was found to contain malicious code or consuming dependency that contains malicious code

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

8b9fac34e13ad38cb702f7aad434d18aa276005fe5fa4cbe48c7eb65af26623d

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 blockchain-helper-0 (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging blockchain-helper-0 across your stack and pipelines.
If you installed it — respond
blockchain-helper-0 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 blockchain-helper-0 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 blockchain-helper-0 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. blockchain-helper-0 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-009498

References

Credits

Amazon Inspector · finder
SafeDep · finder

Detect & block this

O3 blocks blockchain-helper-0-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