Malware in nodemon-slint
The npm package nodemon-slint contains malware that grants full system compromise to attackers. Any system with this package installed or running should be considered fully compromised.
- Disclosed
- Last updated
- Blast radius
- Any system with nodemon-slint installed or executed
- Ecosystems
- Attack vectors
- Affected entities
- nodemon-slintMalicious npm package
The npm package nodemon-slint has been identified as containing malware. According to the GitHub Advisory (GHSA-wr24-8cj8-p627), any computer that has this package installed or running should be considered fully compromised.\n\nThe advisory indicates 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 initial compromise, given that the attacker may have gained full control of the system.\n\nThis represents a critical supply chain attack through a malicious npm package, likely targeting developers who depend on this package in their projects.
Indicators of compromise
- Packages
- nodemon-slint
Remediation
- Immediately isolate any system with nodemon-slint installed from the network
- From a separate, uncompromised computer, rotate all secrets, API keys, credentials, and signing keys that may have been accessible on the compromised system
- Remove the nodemon-slint package from all systems
- Perform a full security audit and malware scan on affected systems
- Review all code commits and deployments made from affected systems for potential backdoors or malicious changes
- Consider the system fully compromised and plan for complete rebuild if it had access to sensitive infrastructure
Sources
- GitHub Advisory GHSA-wr24-8cj8-p627 · GitHub Advisory Database
Cite this entry
"Malware in nodemon-slint." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 10, 2026; last updated July 10, 2026. https://supplychainattack.org/incident/malware-in-nodemon-slint-t04xo6
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 test2221 (npm)
The npm package test2221 version 2.2.4 was identified as malicious by the OpenSSF Package Analysis project. The package executes commands associated with malicious behavior.
npmCompromised package - containedcritical
Malware in n8n-nodes-trust-me-im-totally-safe
Malware was discovered in the npm package n8n-nodes-trust-me-im-totally-safe, resulting in full system compromise for any computer with the package installed or running. All secrets and keys on affected systems should be rotated immediately from a different computer.
npmCompromised package - activecritical
Malware in litespeed-cache
Malware discovered in the npm package litespeed-cache. The package grants full system compromise to attackers, requiring immediate removal and credential rotation from a clean system.
npmCompromised package - containedcritical
Malware in open-worker-cli
Malware was discovered in the npm package open-worker-cli. Systems with this package installed or running should be considered fully compromised, with all secrets and keys requiring immediate rotation from a different computer.
npmCompromised package