Which versions of xdaxx are malicious?

The following npm versions of xdaxx are flagged malicious: 1.0.1. Treat any of these as compromised.

How do I remediate xdaxx if I installed it?

xdaxx is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed xdaxx — how do I know if it already compromised me?

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

Yes — xdaxx is associated with the IN-MAL-2026-016769 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 xdaxx 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 xdaxx (version 1.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging xdaxx across your stack and pipelines.

Malicious package

xdaxxnpm

xdaxx is a confirmed malicious npm package (MAL-2026-13468) that steals credentials and exfiltrates sensitive data (malicious version 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in xdaxx (npm)

MAL-2026-13468

Immediate action

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

npm uninstall xdaxx

What this malware does

The tarball contains a working browser-side account-takeover payload gated to run on noviembrenacional.com. When loaded in a logged-in victim's browser, it uses the victim's authenticated session to delete other users' accounts via WordPress/BuddyPress /members/<user>/settings/delete-account/ endpoints and, if the victim is the noviembrenacional administrator, changes the account email to [email protected] and triggers a password reset — completing a full account takeover. Execution progress is beaconed to a canarytokens.com URL controlled by the payload author. The same exploit is shipped in two forms: original.js in cleartext and i.js as a unicode-escape/hex-obfuscated copy (identifiers like _0xd243bf, strings built via \u00XX escapes and reversed-string tricks). The package has no lifecycle hooks and the declared main entry is missing, so installing or importing the package does not itself run the payload against the installer's machine; the npm registry is being used as hosting/distribution for a targeted attack tool against a specific third-party site.

Malicious versions

1 flagged

1.0.1

Indicators of compromise (SHA-256)

a7cd212c80bcca22443f4498afeadb70b93268b5904daa521b83242513d478bd

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for xdaxx (version 1.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging xdaxx across your stack and pipelines.
If you installed it — respond
xdaxx is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If xdaxx 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 xdaxx 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. xdaxx on npm has been identified as a malicious package (version 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-016769

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks xdaxx-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database