Which versions of helios-components are malicious?

The following npm versions of helios-components are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate helios-components if I installed it?

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

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

Yes — helios-components is associated with the RLMA-2026-01971 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 helios-components across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for helios-components (version 1.0.0).

Malicious package

helios-componentsnpm

Advisory published Apr 16, 2026Updated Apr 23, 2026

helios-components is a confirmed malicious npm package (MAL-2026-2770) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in helios-components (npm)

MAL-2026-2770

Immediate action

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

npm uninstall helios-components

What this malware does

The package helios-components was found to contain malicious code.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

70b1dc7c3d7c0d2b4f4b5e8740797cc1266f03840d0d3ebe6fedb10ca64df8c4

abeb968ba4df2b2034b9794205c8251dd5687f652448abd156fafb7f117fbc6e

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for helios-components (version 1.0.0).
If you installed it — respond
Remove helios-components 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 helios-components 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. helios-components 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

RLMA-2026-01971

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks helios-components-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

Explore

All malware advisories How O3 detects malware Vulnerability database