Which versions of blockchain-helper-lib are malicious?

The following npm versions of blockchain-helper-lib are flagged malicious: 0.0.1, 0.0.2, 0.0.3, 0.0.4, 0.0.5, 0.0.6, 0.0.7, 0.0.8, 0.0.9, 0.0.10, 0.0.11, 0.0.12, 0.1.0, 0.1.1, 0.1.2, 0.1.3, 0.1.4, 0.1.5, 0.1.6, 0.1.7, and 8 more. Treat any of these as compromised.

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

Remove blockchain-helper-lib from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed blockchain-helper-lib — how do I know if it already compromised me?

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

Yes — blockchain-helper-lib is associated with the GHSA-3rcr-854m-q7w4, RLMA-2026-01128 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-lib 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-lib (28 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging blockchain-helper-lib across your stack and pipelines.

Malicious package

blockchain-helper-libnpm

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

MAL-2026-549

Immediate action

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

npm uninstall blockchain-helper-lib

What this malware does

The package blockchain-helper-lib was found to contain malicious code.

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

28 flagged

0.0.10.0.20.0.30.0.40.0.50.0.60.0.70.0.80.0.90.0.100.0.110.0.120.1.00.1.10.1.20.1.30.1.40.1.50.1.60.1.70.1.80.1.90.1.100.1.110.1.120.1.130.2.00.2.2

Indicators of compromise (SHA-256)

bc40ef408de1f7f81edfe9ef64b28fdd82b1361373d7d3aa2051d56ee8e01f7b

c11700a2d24dc725d693b0942598bae18970721cbb482671f43c005800569e42

039c99a407d1a6564a9ab599fcc038f9fdc39245784bfd550cf76224b3939f8e

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for blockchain-helper-lib (28 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging blockchain-helper-lib across your stack and pipelines.
If you installed it — respond
Remove blockchain-helper-lib from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If blockchain-helper-lib 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-lib 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-lib on npm has been identified as a malicious package (versions 0.0.1, 0.0.2, 0.0.3, 0.0.4, 0.0.5, 0.0.6, 0.0.7, 0.0.8, and 20 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-3rcr-854m-q7w4RLMA-2026-01128

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks blockchain-helper-lib-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring