Malware in @sauruslord/baileys
The npm package @sauruslord/baileys contains malware that grants full control of affected systems. Any computer with this package installed or running should be considered fully compromised.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- @sauruslord/baileys
The npm package @sauruslord/baileys has been identified as containing malware. According to the GitHub Security Advisory (GHSA-gq5v-w47h-r596), any computer that has this package installed or running should be considered fully compromised.\n\nThe advisory recommends that all secrets and keys stored on affected computers be rotated immediately from a different, uncompromised system. While the package should be removed, there is no guarantee that removal will eliminate all malicious software that may have been installed as a result of the package installation, given that the malware may have granted outside entities full control of the system.\n\nAffected users should treat their systems as potentially fully compromised and take appropriate incident response measures.
Indicators of compromise
- Packages
- @sauruslord/baileys
Remediation
- Immediately remove the @sauruslord/baileys package from all systems
- Rotate all secrets, keys, and credentials from a different, uncompromised computer
- Assume full system compromise and conduct thorough forensic analysis
- Monitor affected systems for signs of unauthorized access or persistence mechanisms
- Consider rebuilding affected systems from clean media if full compromise is suspected
Sources
- GitHub Advisory GHSA-gq5v-w47h-r596 · GitHub Advisory Database
Cite this entry
"Malware in @sauruslord/baileys." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 15, 2026; last updated July 15, 2026. https://supplychainattack.org/incident/malware-in-sauruslord-baileys-2fdfj8
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- resolvedcritical
Malicious code in test2221 (npm)
The npm package test2221 version 2.2.4 was identified as malicious by the OpenSSF Package Analysis project. The package executes commands associated with malicious behavior.
npmCompromised package - containedcritical
Malware in n8n-nodes-trust-me-im-totally-safe
Malware was discovered in the npm package n8n-nodes-trust-me-im-totally-safe, resulting in full system compromise for any computer with the package installed or running. All secrets and keys on affected systems should be rotated immediately from a different computer.
npmCompromised package - activecritical
Malware in litespeed-cache
Malware discovered in the npm package litespeed-cache. The package grants full system compromise to attackers, requiring immediate removal and credential rotation from a clean system.
npmCompromised package - containedcritical
Malware in open-worker-cli
Malware was discovered in the npm package open-worker-cli. Systems with this package installed or running should be considered fully compromised, with all secrets and keys requiring immediate rotation from a different computer.
npmCompromised package