Which versions of @fyxzpediaa/baileys are malicious?

The following npm versions of @fyxzpediaa/baileys are flagged malicious: 8.1.2. Treat any of these as compromised.

How do I remediate @fyxzpediaa/baileys if I installed it?

@fyxzpediaa/baileys 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 @fyxzpediaa/baileys — how do I know if it already compromised me?

If @fyxzpediaa/baileys 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 @fyxzpediaa/baileys part of a known attack campaign?

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

Malicious package

@fyxzpediaa/baileysnpm

@fyxzpediaa/baileys is a confirmed malicious npm package (MAL-2026-16070) that steals credentials and exfiltrates sensitive data (malicious version 8.1.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @fyxzpediaa/baileys (npm)

MAL-2026-16070

Immediate action

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

npm uninstall @fyxzpediaa/baileys

What this malware does

This fork of Baileys injects a covert remote-directed action into the WhatsApp socket. On every WebSocket connection, socketConnect() reconstructs a URL from a char-code array (decoding to https://raw.githubusercontent.com/skyzopedia/NewsletterID/refs/heads/main/VIP_Push.json), fetches a JSON list from that mutable GitHub branch, and 200 seconds after connect iterates the list issuing authenticated w:mex queries with query_id 7871414976211147 (QueryIds.FOLLOW) against the installer's own WhatsApp session. A separate exported helper generateMessageV decodes a base64+XOR(key=23)-obfuscated string to a hardcoded <digits>@newsletter JID and invokes the same FOLLOW query. The obfuscation of both the URL (char-code array) and the JID literal (base64+XOR) exists solely to hide these targets from source review; upstream Baileys does not contain this code path. The runtime dependency @whiskeysockets/eslint-config is also declared as a mutable GitHub tarball reference (github:whiskeysockets/eslint-config) rather than a pinned registry range, so npm install resolves it to whatever that repository's default branch currently contains. The covert action uses the installer's authenticated identity to gain reach for author-chosen newsletter IDs but does not exfiltrate credentials, install persistence, or execute remote code on the installer's host; the harm is loss of control over the installer's WhatsApp account actions, not machine compromise.

Malicious versions

1 flagged

8.1.2

Indicators of compromise (SHA-256)

0747ec3c1ce519798cac2e89f8ec1e1532d428355a13929f0176a11d77a2b175

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

Campaign

IN-MAL-2026-019837

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @fyxzpediaa/baileys-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