Which versions of chain-argon are malicious?

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

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

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

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

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

Search your lockfiles and build artifacts for chain-argon (version 2.4.5).

Malicious package

chain-argonnpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

chain-argon is a confirmed malicious npm package (MAL-2026-1686) 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 chain-argon (npm)

MAL-2026-1686

Immediate action

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

npm uninstall chain-argon

What this malware does

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

Malicious versions

1 flagged

2.4.5

Indicators of compromise (SHA-256)

e32a6e98a7bcd546d4fd81a9b5354752206da946da1f49719f1b548bf66b476b

12ee1203bf0112eb0f499bffaaaaa84264b875f83e282b54ec6749fe9230baf2

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for chain-argon (version 2.4.5).
If you installed it — respond
Remove chain-argon 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 chain-argon 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. chain-argon 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-01200

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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