Malicious code in @xsat10/baileys-xsat (npm)
MAL-2026-13390 · GHSA-fj9m-r2qx-cc39
Published · Modified
Dependency scanning
Check whether @xsat10/baileys-xsat is in your codebase
Corgea flags malicious and compromised dependencies with reachability analysis, so you fix the packages that actually run in your application instead of working through the whole lockfile.
Description
__
Source: amazon-inspector (37ba86faab85b50d9ae903ee59c78a8b52e46797b4c003448cd9851cd774939b)
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.
Source: ghsa-malware (c98d95ec19b8569af9b1822b1f3561d46ca3feec14066b6f353a25a6fe830124)
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.
References
Ready to move
Start Securing
Free, no credit card | First findings in minutes