Malware in nodemon-sudo
The npm package nodemon-sudo contained malware that could fully compromise any system where it was installed or executed. The advisory recommends treating affected systems as fully compromised and rotating all secrets and keys from a different computer.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- nodemon-sudonpm package containing malware
The npm package nodemon-sudo was found to contain malware. According to the GitHub advisory (GHSA-8228-4gjp-c339), any computer with this package installed or running should be considered fully compromised.\n\nThe malware grants full control of the affected system to an outside entity. All secrets, keys, and credentials stored on compromised systems should be rotated immediately from a different, unaffected computer.\n\nWhile 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. Systems should be treated as potentially containing persistent backdoors or other malware.\n\nThe advisory was published on 2026-07-09 via GitHub's security advisory system.
Indicators of compromise
- Packages
- nodemon-sudo
Remediation
- Remove the nodemon-sudo package immediately
- Treat any system that had this package installed or running as fully compromised
- Rotate all secrets, keys, and credentials from a different, unaffected computer
- Perform a full security audit and malware scan of affected systems
- Consider rebuilding or replacing affected systems if possible
- Review system logs and access logs for signs of unauthorized activity during the period the package was installed
Sources
- GitHub Advisory GHSA-8228-4gjp-c339 · GitHub Advisory Database
Cite this entry
"Malware in nodemon-sudo." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 9, 2026; last updated July 9, 2026. https://supplychainattack.org/incident/malware-in-nodemon-sudo-ecyg6c
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 github-policy-bot (npm)
The npm package github-policy-bot contained malicious code that exfiltrated host identifiers and environment metadata during installation via a postinstall script. The package name shadowed a legitimate Google-owned repository and was authored under a placeholder account claiming security research purposes.
npmCompromised packageTyposquatting - containedcritical
Malicious code in crypto-javas (npm)
The npm package crypto-javas contains malicious code in its postinstall hook and main entrypoint that harvests environment variables (including CI secrets like AWS_*, GITHUB_TOKEN, NPM_TOKEN) and exfiltrates them to an attacker-controlled backend. The package is presented deceptively as @wizlabs/js-crypto with a placeholder repository.
npmCompromised packageTyposquatting - containedcritical
Malicious code in flydev (npm)
The npm package flydev contains malicious code designed to destroy Windows systems. The package masquerades as a utility but executes destructive operations including filesystem deletion, process termination, memory exhaustion, and fork bombs when invoked.
npmCompromised package - containedcritical
Malicious code in npm-wold (npm)
npm-wold@1.1.1 contains malicious code in its postinstall script that fetches remote JSON from a hardcoded endpoint and dynamically invokes attacker-controlled functions with attacker-supplied arguments, enabling code execution at install time.
npmCompromised package