Malware in logger-beauty
Malware was discovered in the npm package logger-beauty. The package grants full system compromise to attackers, requiring immediate removal and credential rotation from unaffected systems.
- Disclosed
- Last updated
- Blast radius
- Any system with logger-beauty installed or running
- Ecosystems
- Attack vectors
- Affected entities
- logger-beautynpm package
The npm package logger-beauty was found to contain malware. According to the GitHub Advisory (GHSA-x3x7-mgj2-qg5x), 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, unaffected 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 installation.\n\nThe incident was disclosed on July 6, 2026 via GitHub's advisory system.
Remediation
- Immediately remove the logger-beauty package from all affected systems
- Rotate all secrets, API keys, and credentials from a different, unaffected computer
- Assume full system compromise and conduct forensic analysis
- Monitor affected systems for signs of persistent malware or unauthorized access
- Review system logs and network traffic for indicators of compromise
Sources
- GitHub Advisory GHSA-x3x7-mgj2-qg5x · GitHub Advisory Database
Cite this entry
"Malware in logger-beauty." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 6, 2026; last updated July 6, 2026. https://supplychainattack.org/incident/malware-in-logger-beauty-1faiu7
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