Which versions of wxwxtt are malicious?

The following npm versions of wxwxtt are flagged malicious: 0.0.0, 0.0.1, 0.1.0, 1.0.0, 1.0.1, 1.1.0, 2.0.0, 2.0.1, 3.0.0, 99.0.1. Treat any of these as compromised.

How do I remediate wxwxtt if I installed it?

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

If wxwxtt 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.

How do I find wxwxtt across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for wxwxtt (10 malicious versions).

Malicious package

wxwxttnpm

Advisory published Oct 26, 2026Updated Nov 5, 2026

wxwxtt is a confirmed malicious npm package (MAL-2026-18701) that opens a backdoor for remote access (malicious versions 0.0.0, 0.0.1, 0.1.0…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in wxwxtt (npm)

MAL-2026-18701

Immediate action

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

npm uninstall wxwxtt

What this malware does

wxwxtt is a dependency-confusion package (versions up to 99.0.1) from the same campaign as troubleshooting (MAL-2026-17641): a postinstall script runs beacon.cjs, which POSTs the installing host's name, install path and working directory to a hard-coded collector, and index.js, byte-identical to the troubleshooting payload (sha256 a86a4da763bbb34c16f361abe7aab66d5df591b66867ac8160041f932159b08d), does the same when imported.

Malicious versions

10 flagged

0.0.00.0.10.1.01.0.01.0.11.1.02.0.02.0.13.0.099.0.1

Detection & response playbook

Backdoor / remote access

Find it
Search your lockfiles and build artifacts for wxwxtt (10 malicious versions).
If you installed it — respond
wxwxtt 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 wxwxtt 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. wxwxtt on npm has been identified as a malicious package (versions 0.0.0, 0.0.1, 0.1.0, 1.0.0, 1.0.1, 1.1.0, 2.0.0, 2.0.1, and 2 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

References

Credits

CyberXYZ · finder

Detect & block this

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