Malware in @sauruslord/libsignal
Malware discovered in the npm package @sauruslord/libsignal. Systems with this package installed are considered fully compromised and require immediate remediation.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- @sauruslord/libsignal
A malicious npm package @sauruslord/libsignal has been identified as containing malware. According to the GitHub Advisory (GHSA-p9pv-49fq-8f6m), any computer with this package installed or running should be considered fully compromised.\n\nThe advisory indicates that the malware grants full control of affected systems to an outside entity. All secrets and keys stored on compromised computers should be rotated immediately from a different, unaffected system.\n\nWhile 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 initial compromise. Full system remediation and security review is recommended.
Indicators of compromise
- Packages
- @sauruslord/libsignal
Remediation
- Immediately remove the @sauruslord/libsignal package from all systems
- Rotate all secrets, keys, and credentials from a different, unaffected computer
- Perform a full security audit and malware scan of any system that had this package installed
- Review system logs and network activity for signs of unauthorized access or data exfiltration
- Consider full system reimaging if the package was installed on production or sensitive systems
- Check for any other malicious packages or artifacts left behind by the malware
Sources
- GitHub Advisory GHSA-p9pv-49fq-8f6m · GitHub Advisory Database
Cite this entry
"Malware in @sauruslord/libsignal." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 15, 2026; last updated July 15, 2026. https://supplychainattack.org/incident/malware-in-sauruslord-libsignal-14gqqr
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 sme-rko-finance-front-operations-feed-impl (npm)
The npm package sme-rko-finance-front-operations-feed-impl contained malicious code that downloads and executes platform-specific binary payloads via Cloudflare Workers or DNS-based staging channels. The malware obfuscates child_process imports and executes on require(), making it active upon installation.
npmCompromised package - containedcritical
Malicious code in sme-rko-finance-front-operations-overnight (npm)
The npm package sme-rko-finance-front-operations-overnight contains malicious code that downloads and executes attacker-controlled binaries from Cloudflare Workers hosts on package require. The payload uses obfuscation techniques to evade static analysis and includes environment-based gating to reduce detection.
npmCompromised package - containedcritical
Malicious code in sme-rko-finance-front-payment-registers-operations-domain (npm)
The npm package sme-rko-finance-front-payment-registers-operations-domain contained malicious code that downloads and executes platform-specific binaries from attacker-controlled infrastructure. The package uses obfuscated string construction to hide command-and-control domains and implements a DNS-TXT fallback channel for payload delivery.
npmCompromised package - resolvedcritical
Malicious code in sme-rko-finance-front-operations-providers (npm)
The npm package sme-rko-finance-front-operations-providers contained malicious code that downloads and executes platform-specific binaries from attacker-controlled Cloudflare Workers subdomains and DNS-TXT fallback channels upon require().
npmCompromised package