Which versions of relion-node are malicious?

The following npm versions of relion-node are flagged malicious: 2.4.7. Treat any of these as compromised.

How do I remediate relion-node if I installed it?

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

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

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

Search your lockfiles and build artifacts for relion-node (version 2.4.7).

Malicious package

relion-nodenpm

Advisory published Apr 16, 2026Updated Apr 23, 2026

relion-node is a confirmed malicious npm package (MAL-2026-2797) that executes malicious code on install (malicious version 2.4.7). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in relion-node (npm)

MAL-2026-2797

Immediate action

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

npm uninstall relion-node

What this malware does

The package relion-node was found to contain malicious code.

Malicious versions

1 flagged

2.4.7

Indicators of compromise (SHA-256)

540f1597911d1a78fef2746b39c39a3dd7e99d665388e3c07ca8d26873e1ddea

92fd7c62cf3860ce9650e66abf6424900c5e1bfab538bd3b611158c8da85bd43

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for relion-node (version 2.4.7).
If you installed it — respond
Remove relion-node 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 relion-node 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. relion-node on npm has been identified as a malicious package (version 2.4.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-02034

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks relion-node-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