Which versions of pearx93qja-notthedevs are malicious?

The following npm versions of pearx93qja-notthedevs are flagged malicious: 1.1.8. Treat any of these as compromised.

How do I remediate pearx93qja-notthedevs if I installed it?

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

If pearx93qja-notthedevs 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 pearx93qja-notthedevs across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for pearx93qja-notthedevs (version 1.1.8).

Malicious package

pearx93qja-notthedevsnpm

Advisory published Nov 2, 2026Updated Nov 5, 2026

pearx93qja-notthedevs is a confirmed malicious npm package (MAL-2026-18663) that opens a backdoor for remote access (malicious version 1.1.8). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in pearx93qja-notthedevs (npm)

MAL-2026-18663

Immediate action

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

npm uninstall pearx93qja-notthedevs

What this malware does

Part of a self-republishing campaign: the package ships autochange2.js, which in a loop gives the package a new random name, rewrites package.json and runs npm publish to publish the package again under the new name. Self-replicating publication is the propagation step of a registry worm and fills the registry with copies. Version examined: 1.1.8; tarball SHA-256 938dfb2c4192301e0c212617e4e459e1a4af51beed1d2ca862b68f9c2e6a3595.

Malicious versions

1 flagged

1.1.8

Detection & response playbook

Backdoor / remote access

Find it
Search your lockfiles and build artifacts for pearx93qja-notthedevs (version 1.1.8).
If you installed it — respond
pearx93qja-notthedevs 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 pearx93qja-notthedevs 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. pearx93qja-notthedevs on npm has been identified as a malicious package (version 1.1.8 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

Oluwatosin Amokeodo · finder

Detect & block this

O3 blocks pearx93qja-notthedevs-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