Malware in coral-wraith
Malware was discovered in the npm package coral-wraith. Systems with the package installed or running should be considered fully compromised and require immediate remediation.
- Disclosed
- Last updated
- Blast radius
- Any system with coral-wraith installed or running; full system compromise possible
- Ecosystems
- Attack vectors
- Affected entities
- coral-wraith
The npm package coral-wraith was found to contain malware. According to the GitHub Advisory (GHSA-f2r7-23p9-8jff), any computer with this package installed or running should be considered fully compromised.\n\nThe advisory recommends immediate rotation of all secrets and keys from a different, uncompromised computer. 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 compromise.\n\nFull system compromise is possible, and users should treat affected systems as potentially under the control of an external threat actor.
Indicators of compromise
- Packages
- coral-wraith
Remediation
- Immediately rotate all secrets, keys, and credentials from a different, uncompromised computer
- Remove the coral-wraith package from all affected systems
- Perform a full security audit and malware scan of any system that had coral-wraith installed
- Consider the affected system(s) as potentially fully compromised and plan for complete rebuild if critical systems are involved
- Review access logs and monitor for unauthorized activity on systems that had the package installed
Sources
- GitHub Advisory GHSA-f2r7-23p9-8jff · GitHub Advisory Database
Cite this entry
"Malware in coral-wraith." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 12, 2026; last updated June 12, 2026. https://supplychainattack.org/incident/malware-in-coral-wraith-1gt24m
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