Malware in ecto-win-flag-q2m7
Malware discovered in the npm package ecto-win-flag-q2m7. Systems with this package installed are considered fully compromised and may have given outside entities complete control.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- ecto-win-flag-q2m7
A malicious npm package named ecto-win-flag-q2m7 has been identified as containing malware. According to the GitHub Advisory (GHSA-22wq-6mfh-69qv), any computer with this package installed or running should be considered fully compromised.\n\nThe advisory warns that all secrets and keys stored on affected computers should 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 complete system compromise.\n\nAffected users should treat their systems as potentially fully controlled by an outside entity and take appropriate incident response measures.
Indicators of compromise
- Packages
- ecto-win-flag-q2m7
Remediation
- Immediately isolate affected systems from the network
- Rotate all secrets, API keys, and credentials from a different, uncompromised computer
- Remove the ecto-win-flag-q2m7 package from all systems
- Perform a full forensic analysis and malware scan of affected systems
- Consider the affected systems as fully compromised and plan for complete rebuild if critical systems are involved
- Review access logs and audit trails for any unauthorized activity during the period the package was installed
Sources
- GitHub Advisory GHSA-22wq-6mfh-69qv · GitHub Advisory Database
Cite this entry
"Malware in ecto-win-flag-q2m7." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 12, 2026; last updated June 12, 2026. https://supplychainattack.org/incident/malware-in-ecto-win-flag-q2m7-1o5z3t
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 sme-rko-finance-front-operations-feed-impl (npm)
The npm package sme-rko-finance-front-operations-feed-impl contained malicious code that downloads and executes platform-specific binary payloads via Cloudflare Workers or DNS-based staging channels. The malware obfuscates child_process imports and executes on require(), making it active upon installation.
npmCompromised package - containedcritical
Malicious code in sme-rko-finance-front-operations-overnight (npm)
The npm package sme-rko-finance-front-operations-overnight contains malicious code that downloads and executes attacker-controlled binaries from Cloudflare Workers hosts on package require. The payload uses obfuscation techniques to evade static analysis and includes environment-based gating to reduce detection.
npmCompromised package - containedcritical
Malicious code in sme-rko-finance-front-payment-registers-operations-domain (npm)
The npm package sme-rko-finance-front-payment-registers-operations-domain contained malicious code that downloads and executes platform-specific binaries from attacker-controlled infrastructure. The package uses obfuscated string construction to hide command-and-control domains and implements a DNS-TXT fallback channel for payload delivery.
npmCompromised package - resolvedcritical
Malicious code in sme-rko-finance-front-operations-providers (npm)
The npm package sme-rko-finance-front-operations-providers contained malicious code that downloads and executes platform-specific binaries from attacker-controlled Cloudflare Workers subdomains and DNS-TXT fallback channels upon require().
npmCompromised package