Which versions of prastzyy are malicious?

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

How do I remediate prastzyy if I installed it?

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

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

Is prastzyy part of a known attack campaign?

Yes — prastzyy is associated with the GHSA-qhp3-5q65-76mj 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 prastzyy across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for prastzyy (version 1.0.0).

Malicious package

prastzyynpm

Advisory published Oct 19, 2026Updated Oct 19, 2026

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

Malicious code in prastzyy (npm)

MAL-2026-17449

Immediate action

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

npm uninstall prastzyy

What this malware does

This package is a fork of the Baileys WhatsApp Web library (npm) and belongs to the "PhantomSub" family described by OX Security in September 2026: the publisher injected code that, without the installer asking, uses the installer's own authenticated WhatsApp session to subscribe that account to WhatsApp Channels (newsletters) the publisher chose, by sending the WhatsApp w:mex FOLLOW query (query_id 7871414976211147) for each target channel JID.

package/lib/Socket/newsletter.js lines 62-103 define AUTO_FOLLOW_JIDS, eight base64 strings decoded with Buffer.from(..., "base64"), and when the connection opens (line 102) schedule a FOLLOW query for each, 90 seconds apart (cited line 90: await newsletterWMexQuery(jid, QueryIds.FOLLOW);). Decoded JIDs: 120363430764800148@newsletter, 120363400505489366@newsletter, 120363427794786523@newsletter, 120363428149518339@newsletter, 120363411665168068@newsletter, 120363410421978309@newsletter, 120363426605069018@newsletter and 120363425633124233@newsletter. There is no opt-out and the behavior is not documented.

Line numbers refer to version 1.0.0.

Static review of the published tarball(s) found no code that sends WhatsApp credentials or session keys off-host, no install-time payload (the only install hook is Baileys' stock Node.js version check in engine-requirements.js), and no persistence; the payload runs when an application creates a WhatsApp socket with the library. The harm is the covert use of the victim's account to inflate the publisher's channel subscribers.

SHA-256 of the published npm tarball(s): 1.0.0: 9451d13f06ff94c6d627f7ba7d8a7ad7f73a6cfbb856c7f4c2e29c3b187484bb.

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)

bf5b70083dc2338579dac55f7f321700cf098ccc3ac71d5506c8dca2b3855ddc

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for prastzyy (version 1.0.0).
If you installed it — respond
prastzyy 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 prastzyy 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. prastzyy 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-qhp3-5q65-76mj

References

Credits

Rising Sun Solutions LLC · finder

Detect & block this

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