Malware in @nebula.js/theme
Malware was discovered in the npm package @nebula.js/theme. 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
- @nebula.js/theme
A critical malware incident was identified in the npm package @nebula.js/theme. According to the GitHub Security Advisory (GHSA-4hpr-95rm-52f2), any computer with this package installed or running should be considered fully compromised.\n\nThe advisory recommends immediate action: all secrets and keys stored on affected computers should be rotated 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, as the attacker may have gained full control of the system.\n\nAffected users should treat this as a critical security incident requiring comprehensive system remediation and credential rotation.
Indicators of compromise
- Packages
- @nebula.js/theme
Remediation
- Immediately rotate all secrets, API keys, and credentials from a different, uncompromised computer
- Remove the @nebula.js/theme package from all affected systems
- Perform a comprehensive security audit and malware scan of all systems that had this package installed
- Review system logs and access logs for any unauthorized activity during the period the package was installed
- Consider full system reimaging if the package was installed on production or sensitive systems
- Monitor for any signs of continued compromise or data exfiltration
Sources
- GitHub Advisory GHSA-4hpr-95rm-52f2 · GitHub Advisory Database
Cite this entry
"Malware in @nebula.js/theme." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 4, 2026; last updated August 4, 2026. https://supplychainattack.org/incident/malware-in-nebula-js-theme-1mascl
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-models (npm)
The npm package sme-rko-finance-front-operations-feed-models contained malicious code that downloads and executes attacker-controlled native binaries from remote servers upon package load. The malware uses obfuscation techniques including fragmented string arrays, platform-specific endpoints, and DNS TXT record fallbacks to evade detection.
npmCompromised package - resolvedcritical
Malicious code in modern-localization (npm)
The npm package modern-localization contained malicious code that fetches and executes arbitrary JavaScript from a remote jsonbin.io endpoint on server-side require, with no integrity verification. The payload is executed with full Node.js privileges via Function() or child_process.fork().
npmCompromised package - resolvedcritical
Malicious code in sme-rko-finance-front-operations-tax (npm)
The npm package sme-rko-finance-front-operations-tax contained malicious code that downloads and executes platform-specific binaries from attacker-controlled infrastructure on require. The package was identified and reported by OpenSSF's malicious-packages project.
npmCompromised package - resolvedcritical
Malicious code in localization-fixer (npm)
The npm package localization-fixer contained malicious code that fetches and executes arbitrary JavaScript from attacker-controlled jsonbin.io endpoints on package require, granting full Node.js capabilities to remote payloads.
npmCompromised package