Which versions of argon-node are malicious?

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

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

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

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

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

Search your lockfiles and build artifacts for argon-node (version 3.5.7).

Malicious package

argon-nodenpm

Advisory published Mar 24, 2026Updated Apr 7, 2026

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

Malicious code in argon-node (npm)

MAL-2026-2334

Immediate action

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

npm uninstall argon-node

What this malware does

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

Malicious versions

1 flagged

3.5.7

Indicators of compromise (SHA-256)

5686d1d939aab5467c279b9bc3b8d5094b946d854364d19b3c1780ebcd7fc67d

e3639b8833add6b5673b5f647479520157a22229369754ef98675e97a4a56385

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01711

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks argon-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