Malware in postcss-minify-selector
Malware discovered in the npm package postcss-minify-selector. The package is considered to provide full system compromise to any computer where it is installed or running.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- postcss-minify-selector
A critical malware incident has been identified in the npm package postcss-minify-selector. According to the GitHub Advisory (GHSA-gwv6-f7j6-4xc8), 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, there is no guarantee that removal will eliminate all malicious software that may have been installed as a result of the package installation, given the potential for full system compromise.\n\nAffected systems should be treated as potentially under the control of an external threat actor and handled accordingly.
Indicators of compromise
- Packages
- postcss-minify-selector
Remediation
- Immediately isolate any computer with postcss-minify-selector installed from the network
- Rotate all secrets, API keys, and credentials from a different, uncompromised computer
- Remove the postcss-minify-selector package from all systems
- Perform a full security audit and malware scan of affected systems
- Consider full system reimaging if the package was installed on production or sensitive systems
- Review all access logs and activity on affected systems for signs of unauthorized access or data exfiltration
Sources
- GitHub Advisory GHSA-gwv6-f7j6-4xc8 · GitHub Advisory Database
Cite this entry
"Malware in postcss-minify-selector." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 24, 2026; last updated June 24, 2026. https://supplychainattack.org/incident/malware-in-postcss-minify-selector-1u44s0
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