Malware in dbmux
Malware was discovered in the npm package dbmux. Any computer with this package installed or running should be considered fully compromised, requiring immediate rotation of all secrets and keys from a different system.
- Disclosed
- Last updated
- Blast radius
- Any system with dbmux installed or running is considered fully compromised; all secrets and keys must be rotated.
- Ecosystems
- Attack vectors
- Affected entities
- dbmuxnpm package
The npm package dbmux was found to contain malware. According to the GitHub Advisory (GHSA-62wx-5f55-w8g2), any computer that has this package installed or running should be considered fully compromised.\n\nImmediate action is required: all secrets and keys stored on affected computers must be rotated immediately from a different, uncompromised computer. The malicious package should be removed, though there is no guarantee that removal will eliminate all malicious software that may have been installed as a result of the compromise.\n\nThe advisory indicates that full control of affected systems may have been given to an outside entity, underscoring the severity of the incident.
Indicators of compromise
- Packages
- dbmux
Remediation
- Immediately rotate all secrets, API keys, and credentials from a different, uncompromised computer
- Remove the dbmux package from all affected systems
- Audit system logs for unauthorized access or activity during the period the malicious package was installed
- Consider the affected computer(s) as potentially fully compromised and plan for forensic analysis or reimaging
- Check for any additional malicious software that may have been installed alongside the compromised package
Sources
- GitHub Advisory GHSA-62wx-5f55-w8g2 · GitHub Advisory Database
Cite this entry
"Malware in dbmux." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 9, 2026; last updated June 9, 2026. https://supplychainattack.org/incident/malware-in-dbmux-13zxox
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- activecritical
Malware in @doaction/auth
Malware discovered in the npm package @doaction/auth. Systems with this package installed are considered fully compromised and require immediate remediation.
npmCompromised package - containedcritical
Malware in @doaction/shared
Malware was discovered in the npm package @doaction/shared. Systems with this package installed are considered fully compromised and require immediate remediation.
npmCompromised package - containedcritical
Malware in transacts
The npm package transacts was found to contain malware, resulting in full system compromise of any computer with the package installed or running. All secrets and keys should be rotated immediately from a different computer, and the package should be removed.
npmCompromised package - containedcritical
Malware in buffer-utilities
Malware was discovered in the npm package buffer-utilities, resulting in full system compromise for any installation. The package should be removed immediately and all secrets and keys rotated from a clean system.
npmCompromised package