Malicious code in moonskin (npm)
The npm package moonskin was found to contain malicious code that communicates with a domain associated with malicious activity. The package was published to the npm registry and poses a supply chain risk to any project that installed affected versions.
- Disclosed
- Last updated
- Blast radius
- Unknown; depends on moonskin adoption and affected version range
- Ecosystems
- Attack vectors
- Affected entities
- moonskinnpm package with malicious code communicating with attacker-controlled domain
The npm package moonskin was identified as containing malicious code. According to the GitHub Advisory (GHSA-wqwp-pmcq-5vxm), the package communicates with a domain associated with malicious activity, indicating potential data exfiltration, command-and-control, or other malicious behavior.\n\nThis is a compromised-package incident where the malicious code was present in the published npm package itself. Any developer or application that installed moonskin during the affected period would have been exposed to the malicious behavior.\n\nThe advisory was published on 2026-07-14 via GitHub's security advisory system, which typically indicates the vulnerability has been identified and disclosed to the public.
Indicators of compromise
- Packages
- moonskin
Remediation
- Immediately remove moonskin from all projects and dependencies
- Audit package-lock.json and yarn.lock files to identify all installations of moonskin
- Review application logs and network traffic for suspicious outbound connections to the malicious domain
- Consider the moonskin package compromised; do not update to newer versions without verification from the maintainer
- Use npm audit to identify any other potentially compromised dependencies
- If moonskin was installed in production, conduct a security incident response to assess potential data exposure or system compromise
Sources
- GitHub Advisory GHSA-wqwp-pmcq-5vxm · GitHub Advisory Database
Cite this entry
"Malicious code in moonskin (npm)." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 14, 2026; last updated July 14, 2026. https://supplychainattack.org/incident/malicious-code-in-moonskin-npm-1pwv33
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- activecritical
Malware in @tonsdk/core
Malware was discovered in the npm package @tonsdk/core. Systems with this package installed are considered fully compromised and require immediate remediation.
npmCompromised package - activecritical
Malware in @aonunited/angular
Malware discovered in the npm package @aonunited/angular. Systems with this package installed are considered fully compromised and require immediate remediation.
npmCompromised package - activecritical
Malware in micro-ui-loader
The npm package micro-ui-loader contains malware that grants full system compromise to attackers. Any computer with this package installed or running should be considered fully compromised.
npmCompromised package - activecritical
Malware in @cw-ui/asio-neon-themes
Malware discovered in the npm package @cw-ui/asio-neon-themes. Systems with this package installed are considered fully compromised and require immediate remediation.
npmCompromised package