Malware in coinbase-wallet-utils
Malware was discovered in the npm package coinbase-wallet-utils. Systems with this package installed are considered fully compromised and require immediate remediation including secret rotation and package removal.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- coinbase-wallet-utilsnpm package containing malware
A critical malware incident was identified in the npm package coinbase-wallet-utils. According to the GitHub Advisory (GHSA-6228-p677-g9p7), any computer with 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, the advisory notes that full control of the computer may have been given to an outside entity, meaning removal of the package alone may not eliminate all malicious software that resulted from the installation.\n\nThis represents a critical supply chain compromise affecting npm ecosystem users who installed or used this package.
Indicators of compromise
- Packages
- coinbase-wallet-utils
Remediation
- Immediately rotate all secrets and keys from a different, uncompromised computer
- Remove the coinbase-wallet-utils package from all affected systems
- Conduct a full security audit of any system that had this package installed
- Monitor affected systems for signs of unauthorized access or persistence mechanisms
- Review and revoke any credentials or API keys that may have been exposed
Sources
- GitHub Advisory GHSA-6228-p677-g9p7 · GitHub Advisory Database
Cite this entry
"Malware in coinbase-wallet-utils." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 10, 2026; last updated June 10, 2026. https://supplychainattack.org/incident/malware-in-coinbase-wallet-utils-rf8iik
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