Malware in harmony-enablers-test-2026
Malware was discovered in the npm package harmony-enablers-test-2026. Systems with this package installed or running should be considered fully compromised, requiring immediate rotation of all secrets and keys from a separate computer.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- harmony-enablers-test-2026
A malicious npm package named harmony-enablers-test-2026 was identified and published to the npm registry. The package contains malware that grants full control of affected systems to an outside entity.\n\nAny computer with this package installed or running should be considered fully compromised. All secrets, keys, and credentials stored on affected systems must be rotated immediately from a different, uncompromised computer.\n\nWhile the package should be removed, complete removal of all malicious software cannot be guaranteed due to the level of system compromise. A full security audit and potential system rebuild may be necessary for affected systems.
Indicators of compromise
- Packages
- harmony-enablers-test-2026
Remediation
- Immediately remove the harmony-enablers-test-2026 package from all systems
- Rotate all secrets, keys, and credentials from a separate, uncompromised computer
- Conduct a full security audit of any system that had this package installed
- Consider rebuilding affected systems from clean media
- Monitor for signs of unauthorized access or persistence mechanisms
- Review system logs for suspicious activity during the period the package was installed
Sources
- GitHub Advisory GHSA-ghw7-gg88-gpmr · GitHub Advisory Database
Cite this entry
"Malware in harmony-enablers-test-2026." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 7, 2026; last updated July 7, 2026. https://supplychainattack.org/incident/malware-in-harmony-enablers-test-2026-lp9v6e
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 autbank-core (npm)
The npm package autbank-core contained malicious preinstall and postinstall lifecycle hooks that exfiltrated environment variables, credentials, and system information to a hardcoded webhook.site endpoint during installation.
npmCompromised package - resolvedcritical
Malicious code in adxaa (npm)
The npm package adxaa contained obfuscated malicious JavaScript designed to target users of a specific WordPress site. The payload exfiltrates session data, deletes accounts, and hijacks credentials via email overwrite and password reset.
npmCompromised package - resolvedcritical
Malicious code in upload-to-gcp (npm)
upload-to-gcp@3.2.1 (npm) contains malicious code in its postinstall script that exfiltrates host identifiers to an attacker-controlled endpoint. The package masquerades as a Google Cloud Platform utility but performs unauthorized telemetry collection at install time.
npmCompromised package - resolvedcritical
Malicious code in akamai-sensor (npm)
A malicious npm package named akamai-sensor impersonated Akamai's legitimate sensor_data anti-bot SDK. The package contained hidden JavaScript code concealed using invisible Unicode characters and implemented a dynamic command-and-control channel via a Google Calendar dead-drop, enabling arbitrary code execution on installation.
npmCompromised packageTyposquatting