Malware in gx-npm-feature-flags
Malware was discovered in the npm package gx-npm-feature-flags. Systems with this package installed or running should be considered fully compromised, with all secrets and keys requiring immediate rotation from a different computer.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- gx-npm-feature-flags
A malicious package named gx-npm-feature-flags was published to npm and contains malware. According to the GitHub Advisory (GHSA-hhw7-23r7-qwj7), any computer that has 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\nUsers should assume complete loss of confidentiality and integrity on any system where this package was installed or executed.
Indicators of compromise
- Packages
- gx-npm-feature-flags
Remediation
- Immediately rotate all secrets, API keys, credentials, and signing keys from a different, uncompromised computer
- Remove the gx-npm-feature-flags package from all affected systems
- Perform a full security audit and malware scan on any system that had this package installed
- Review system logs and access logs for any suspicious activity during the period the package was installed
- Consider the affected system(s) as potentially fully compromised and plan for complete rebuild if critical infrastructure
- Check npm audit logs and dependency trees to identify all projects that may have installed this package
Sources
- GitHub Advisory GHSA-hhw7-23r7-qwj7 · GitHub Advisory Database
Cite this entry
"Malware in gx-npm-feature-flags." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 29, 2026; last updated June 29, 2026. https://supplychainattack.org/incident/malware-in-gx-npm-feature-flags-q9f644
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 @vpms/design-system
Malware was discovered in the npm package @vpms/design-system. Systems with this package installed or running should be considered fully compromised, with all secrets and keys requiring immediate rotation from a different computer.
npmCompromised package - resolvedcritical
Malware in velocityfix
The npm package velocityfix contained malware that provided full system compromise to attackers. Any computer with this package installed or running should be considered fully compromised.
npmCompromised package - containedcritical
Malware in ts-einkle-slot
Malware was discovered in the npm package ts-einkle-slot. Systems with this package installed or running should be considered fully compromised, with all secrets and keys requiring immediate rotation from a different computer.
npmCompromised package - containedcritical
Malware in authmatrix
Malware was discovered in the npm package authmatrix, resulting in full system compromise for any computer with the package installed or running. All secrets and keys on affected systems should be rotated immediately from a different computer.
npmCompromised package