Which versions of helium-module are malicious?

The following npm versions of helium-module are flagged malicious: 1.0.0, 99.99.9. Treat any of these as compromised.

How do I remediate helium-module if I installed it?

Remove helium-module 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 helium-module — how do I know if it already compromised me?

If helium-module 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 helium-module part of a known attack campaign?

Yes — helium-module is associated with the GHSA-v72c-68qv-fq35, RLMA-2026-01342 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 helium-module 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 helium-module (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging helium-module across your stack and pipelines.

Malicious package

helium-modulenpm

Malicious code in helium-module (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-244

Immediate action

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

npm uninstall helium-module

What this malware does

The package helium-module 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

2 flagged

1.0.099.99.9

Indicators of compromise (SHA-256)

d34558c0d1e56c0103ad087e485e142f3918050a1b0bdc15fc7e7b46c1a2ae1f

643f63c743fd06fb24cb2d488e001ce0efab3f0d82014801ea2eebad96041692

ffe21caff9c6c62ba0e331a831740acf2be5826d33390fd58f9d208559fe8d10

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

Campaign

GHSA-v72c-68qv-fq35RLMA-2026-01342

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks helium-module-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