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 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 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?

Search your lockfiles and build artifacts for blockchain-helper-0 (version 1.0.0).

Malicious package

blockchain-helper-0npm

Advisory published Jun 9, 2026Updated Jul 9, 2026

blockchain-helper-0 is a confirmed malicious npm package (MAL-2026-5352) 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 blockchain-helper-0 (npm)

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
Search your lockfiles and build artifacts for blockchain-helper-0 (version 1.0.0).
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 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. 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

Explore

All malware advisories How O3 detects malware Vulnerability database