Malware in @tqm-mfe/main
Malware discovered in the npm package @tqm-mfe/main. Any computer with this package installed or running should be considered fully compromised. All secrets and keys must be rotated immediately from a different computer.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- @tqm-mfe/main
A malware-laden version of the npm package @tqm-mfe/main has been identified and published to the npm registry. The package grants full control of affected systems to an outside entity.\n\nAny computer that has installed or executed this package should be considered fully compromised. All secrets, keys, and credentials stored on affected systems must be rotated immediately from a separate, unaffected computer.\n\nWhile the package should be removed, complete remediation cannot be guaranteed due to the level of system compromise. Additional forensic analysis and system hardening may be necessary to ensure all malicious artifacts are eliminated.
Indicators of compromise
- Packages
- @tqm-mfe/main
Remediation
- Immediately remove @tqm-mfe/main from all systems
- Rotate all secrets, API keys, and credentials from a separate, unaffected computer
- Conduct forensic analysis of affected systems to identify additional malicious artifacts
- Review system logs and network traffic for signs of unauthorized access or data exfiltration
- Consider full system reimaging if compromise is confirmed
- Audit all systems that may have accessed secrets or credentials while the malicious package was active
Sources
- GitHub Advisory GHSA-cg4c-94r8-hqjq · GitHub Advisory Database
Cite this entry
"Malware in @tqm-mfe/main." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 20, 2026; last updated July 20, 2026. https://supplychainattack.org/incident/malware-in-tqm-mfe-main-50efd5
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