Which versions of argonflux are malicious?

The following npm versions of argonflux are flagged malicious: 2.0.1. Treat any of these as compromised.

How do I remediate argonflux if I installed it?

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

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

Yes — argonflux is associated with the GHSA-5x7q-hcgw-g7x2, RLMA-2026-04944, RLUA-2026-06069 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 argonflux across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for argonflux (version 2.0.1).

Malicious package

argonfluxnpm

Advisory published Jul 6, 2026Updated Sep 1, 2026

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

Malicious code in argonflux (npm)

MAL-2026-6798

Immediate action

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

npm uninstall argonflux

What this malware does

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged

2.0.1

Indicators of compromise (SHA-256)

ac7feeef8f690a4bff32cb47e1725046d4c0ae9a1abdf45ac4b434f59d314320

2f41f6565202438b533e3417cad332b49542fac467de1ade60972b9568babfb8

f01cb8050885989a0ffc55f645f25eb34ff18f06d2f89d3b25ece683a57f25e4

Detection & response playbook

Malicious package

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

Campaign

GHSA-5x7q-hcgw-g7x2RLMA-2026-04944RLUA-2026-06069

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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