NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

@xsat10/baileys-xsatnpm

Advisory published Updated

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

Malicious code in @xsat10/baileys-xsat (npm)

MAL-2026-13390
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @xsat10/baileys-xsat

What this malware does

Package is a fork of the Baileys WhatsApp Web library. Static keyword co-occurrence patterns matched on lib/Utils/generics.js (ping/GET references) and lib/Utils/messages-media.js (require('child_process') alongside POST/GET/hostname tokens), but these are consistent with Baileys' normal media upload/download paths and connectivity checks rather than a traced exfiltration flow. The concern is fork provenance: Baileys forks have previously been used to wire covert side effects (e.g. auto-follow of author-controlled newsletters, install counters) into the main exported API using the consumer's authenticated WhatsApp session. No specific installer-side data read and non-first-party destination pair has been identified in the code paths matched.

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
2.0.0

Indicators of compromise (SHA-256)

c98d95ec19b8569af9b1822b1f3561d46ca3feec14066b6f353a25a6fe830124
37ba86faab85b50d9ae903ee59c78a8b52e46797b4c003448cd9851cd774939b

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for @xsat10/baileys-xsat (version 2.0.0).

  2. If you installed it — respond

    @xsat10/baileys-xsat 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.

  3. Did it already run?

    If @xsat10/baileys-xsat 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. @xsat10/baileys-xsat on npm has been identified as a malicious package (version 2.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-fj9m-r2qx-cc39IN-MAL-2026-016041

References

Credits

  • Amazon Inspector · finder

Detect & block this

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

Explore

@xsat10/baileys-xsat (npm) malicious package — MAL-2026-13390 | O3 Security