Malware in ethers-jss
Malware discovered in the npm package ethers-jss. Systems with this package installed are considered fully compromised and require immediate remediation.
- Disclosed
- Last updated
- Blast radius
- Any system with ethers-jss installed or running
- Ecosystems
- Attack vectors
- Affected entities
- ethers-jssnpm package
A malware incident has been identified in the npm package ethers-jss. According to the GitHub Advisory (GHSA-xh65-7qcm-493w), any computer with this package installed or running should be considered fully compromised.\n\nThe advisory indicates that the malicious package may have granted outside entities full control of affected systems. All secrets and keys stored on compromised computers should be rotated immediately from a different, unaffected system.\n\nWhile removal of the package is recommended, there is no guarantee that uninstalling it will remove all malicious software that may have been installed as a result of the compromise.
Indicators of compromise
- Packages
- ethers-jss
Remediation
- Immediately remove the ethers-jss package from all systems
- Rotate all secrets, keys, and credentials stored on affected computers from a different, uncompromised system
- Conduct a full security audit of any system that had ethers-jss installed
- Review system logs for unauthorized access or activity during the period the package was installed
- Consider the affected system(s) as potentially fully compromised and take appropriate incident response measures
Sources
- GitHub Advisory GHSA-xh65-7qcm-493w · GitHub Advisory Database
Cite this entry
"Malware in ethers-jss." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 10, 2026; last updated June 10, 2026. https://supplychainattack.org/incident/malware-in-ethers-jss-1ckdhb
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- activecritical
Malicious code in my-auto-follow (npm)
The npm package my-auto-follow contains malicious code that silently auto-follows WhatsApp newsletters from an attacker-controlled list without user consent. The package also depends on a separate malicious libsignal patcher. This is part of an ongoing DGXeon campaign with related malicious packages already documented.
DgxeonnpmCompromised packageMalicious commit - resolvedcritical
Malicious code in @dgxeon13/libsignal-node (npm)
@dgxeon13/libsignal-node is a malicious npm package that impersonates Signal's libsignal Node binding. Upon require, it executes code that modifies @whiskeysockets/baileys to inject a payload enabling remote-controlled WhatsApp newsletter auto-follow functionality.
npmCompromised packageTyposquatting - resolvedcritical
Malicious code in @dreamguyxeon/baileyx (npm)
@dreamguyxeon/baileyx, a Baileys WhatsApp Web API fork on npm, contains malicious code that silently auto-follows newsletters from a remote-controlled list after session setup. The package also patches the libsignal dependency to use a compromised version from @dgxeon13/libsignal-node.
npmCompromised packageMalicious commit - resolvedcritical
Malicious code in @dreamguyxeon/libsignal-node (npm)
@dreamguyxeon/libsignal-node is a malicious npm package that patches @whiskeysockets/baileys at import time to inject remote-controlled WhatsApp newsletter auto-follow code. The package was distributed as a dependency alias in my-auto-follow@1.0.3 and is part of a related malicious campaign.
npmCompromised packageMalicious commit