Malware in @su-doughnym/metrics-js
Malware was discovered in the npm package @su-doughnym/metrics-js. 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
- @su-doughnym/metrics-js
A malware-laden version of the npm package @su-doughnym/metrics-js was published and made available to users. The advisory indicates that any computer with this package installed or running should be considered fully compromised.\n\nThe malware grants outside entities full control of affected systems. All secrets and keys stored on compromised computers should be rotated immediately from a different, unaffected 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 compromise.\n\nThis incident was disclosed via GitHub Advisory GHSA-wj6x-p526-mv2w on 2026-06-25.
Indicators of compromise
- Packages
- @su-doughnym/metrics-js
Remediation
- Immediately remove @su-doughnym/metrics-js from all systems
- Rotate all secrets, API keys, and credentials from a different, unaffected computer
- Perform a full security audit and malware scan of all affected systems
- Review system logs and network traffic for signs of unauthorized access or data exfiltration
- Consider the affected systems as potentially compromised and plan for full reimaging if critical infrastructure
- Monitor for any lateral movement or persistence mechanisms installed by the malware
Sources
- GitHub Advisory GHSA-wj6x-p526-mv2w · GitHub Advisory Database
Cite this entry
"Malware in @su-doughnym/metrics-js." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 25, 2026; last updated June 25, 2026. https://supplychainattack.org/incident/malware-in-su-doughnym-metrics-js-1lcl45
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- containedcritical
Malware in fetch-runtime
Malware was discovered in the npm package fetch-runtime. Any system with this package installed or running should be considered fully compromised. All secrets and keys must be rotated immediately from a different computer.
npmCompromised package - resolvedcritical
Malicious code in ghazaly (npm)
The npm package ghazaly version 99.9.0 contained malicious code that executed a postinstall hook to collect system information (hostname, current user, IP addresses) and exfiltrate it to a Burp Collaborator domain. The package exhibited dependency-confusion characteristics with a high version number and nonsense dependencies.
npmCompromised packageDependency confusion - containedcritical
Malicious code in base65-13x (npm)
base65-13x@5.0.2 on npm contains malicious obfuscated code disguised as a legitimate base-x library. The decode() function executes a ~123KB VM-style payload with dynamic code construction and network I/O capabilities.
npmCompromised package - containedcritical
Malicious code in kit-vim-map (npm)
The npm package kit-vim-map contained malicious code that executes a remote-controlled Linux ELF binary on installation, providing the attacker with arbitrary RCE, persistence, and file exfiltration capabilities. The binary beacons to C2 server 217.60.77.63 and establishes persistence via systemd user units.
npmCompromised packageMalicious commit