Which versions of a5xm are malicious?

Every published version of a5xm on npm is considered malicious. Remove the package entirely.

How do I remediate a5xm if I installed it?

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

If a5xm was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is a5xm part of a known attack campaign?

Yes — a5xm is associated with the GHSA-8v27-jw75-7v3c 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 a5xm across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for a5xm (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging a5xm across your stack and pipelines.

Malicious package

a5xmnpm

Malicious code in a5xm (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-486

Immediate action

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

npm uninstall a5xm

What this malware does

The package a5xm was found to contain malicious code.

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

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

af04e818925f6a7dfdce51341c120a1afe18e57ef12daa899e5246aafd56297f

59318b8cded3eb39d4e5d1cf0e5320f1a6642ee9cf10efada20f75811ca117a2

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for a5xm (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging a5xm across your stack and pipelines.
If you installed it — respond
Remove a5xm 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 a5xm was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks a5xm before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. a5xm on npm has been identified as a malicious package (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-8v27-jw75-7v3c

References

github.com

Credits

Amazon Inspector · finder

Detect & block this

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