Which versions of argonnode are malicious?

The following npm versions of argonnode are flagged malicious: 2.4.5. Treat any of these as compromised.

How do I remediate argonnode if I installed it?

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

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

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

Search your lockfiles and build artifacts for argonnode (version 2.4.5).

Malicious package

argonnodenpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

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

Malicious code in argonnode (npm)

MAL-2026-1656

Immediate action

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

npm uninstall argonnode

What this malware does

The package argonnode was found to contain malicious code.

Malicious versions

1 flagged

2.4.5

Indicators of compromise (SHA-256)

dacb9530e6e0cbe7c52a5dccdd2cbd468c04b5534c805cee284ed1a83d1589e3

5f60d672b9b27685ae096e5891cc64c301004345e38b2a1ecda4e569340c6236

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01108

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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