Which versions of aaaaaxxxxx are malicious?

The following npm versions of aaaaaxxxxx are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate aaaaaxxxxx if I installed it?

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

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

Yes — aaaaaxxxxx is associated with the GHSA-w24m-g68p-7wmq, RLMA-2026-01709 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 aaaaaxxxxx 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 aaaaaxxxxx (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging aaaaaxxxxx across your stack and pipelines.

Malicious package

aaaaaxxxxxnpm

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

MAL-2026-1265

Immediate action

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

npm uninstall aaaaaxxxxx

What this malware does

The package aaaaaxxxxx 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

1 flagged

1.0.0

Indicators of compromise (SHA-256)

76e892030ae3b51f49aca22d108dff0826190b133c1d18bd448c9308b904f8d4

74022d63a8f08b2891b69972616980c694bf36c621e434d53bb293d3c556d50e

22eaa7c8a0b33e24beb730bff22b3590fc063d8f5bd0e731f03fcf8196aeb348

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 aaaaaxxxxx (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging aaaaaxxxxx across your stack and pipelines.
If you installed it — respond
Remove aaaaaxxxxx 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 aaaaaxxxxx 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 aaaaaxxxxx 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. aaaaaxxxxx on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-w24m-g68p-7wmqRLMA-2026-01709

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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