Malware in breeze-feature-flag-poc
Malware was discovered in the npm package breeze-feature-flag-poc. 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
- breeze-feature-flag-poc
The npm package breeze-feature-flag-poc was found to contain malware. According to the GitHub Advisory (GHSA-549f-jwr2-69q2), 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 malicious 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 initial compromise.\n\nThis represents a critical supply chain attack through a compromised npm package with potential for complete system compromise.
Indicators of compromise
- Packages
- breeze-feature-flag-poc
Remediation
- Immediately remove the breeze-feature-flag-poc package from all systems
- Rotate all secrets, API keys, and credentials from a different, uncompromised computer
- Perform a full security audit of any system that had this package installed
- Review system logs for any suspicious activity or unauthorized access
- Consider the affected system(s) as potentially fully compromised and plan for complete rebuild if critical infrastructure
- Check for any other malicious packages or artifacts that may have been installed
Sources
- GitHub Advisory GHSA-549f-jwr2-69q2 · GitHub Advisory Database
Cite this entry
"Malware in breeze-feature-flag-poc." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 9, 2026; last updated July 9, 2026. https://supplychainattack.org/incident/malware-in-breeze-feature-flag-poc-rqfft6
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 @dreamguyxeon/baileyx (npm)
@dreamguyxeon/baileyx, a Baileys WhatsApp Web API fork on npm, contains malicious code that silently auto-follows newsletters from a remote-controlled list after session setup. The package also patches the libsignal dependency to use a compromised version from @dgxeon13/libsignal-node.
npmCompromised packageMalicious commit - resolvedcritical
Malicious code in @dreamguyxeon/libsignal-node (npm)
@dreamguyxeon/libsignal-node is a malicious npm package that patches @whiskeysockets/baileys at import time to inject remote-controlled WhatsApp newsletter auto-follow code. The package was distributed as a dependency alias in my-auto-follow@1.0.3 and is part of a related malicious campaign.
npmCompromised packageMalicious commit - activecritical
Malicious code in my-auto-follow (npm)
The npm package my-auto-follow contains malicious code that silently auto-follows WhatsApp newsletters from an attacker-controlled list without user consent. The package also depends on a separate malicious libsignal patcher. This is part of an ongoing DGXeon campaign with related malicious packages already documented.
DgxeonnpmCompromised packageMalicious commit - containedcritical
Malware in nolimit-agent
Malware was discovered in the nolimit-agent npm package. Systems with this package installed are considered fully compromised and require immediate remediation including secret rotation and package removal.
npmCompromised package