Malicious code in nodemon-slint (npm)
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (5488028be686500c0af6b7f91ead55be9ddaeb86f3b920fce7eed6f8111b0050) Package name, README, homepage (nodemon.io), author (remy), and source tree are copied verbatim from the widely-used 'nodemon' package, with the addition of a single novel runtime dependency 'type-slint' (^3.3.7) declared in package.json. That dependency is never imported by any file reachable from the declared main (lib/nodemon.js) or from bin/, so it serves no functional purpose within this package. The only installer-facing effect of the manifest change relative to nodemon is that 'npm install nodemon-slint' also resolves and installs 'type-slint' into the installer's dependency tree, where any install-time hooks or load-time side effects it contains will run. The host package itself does not exhibit exfiltration, install-time RCE, or backdoor behavior in its own code; the risk is carried by the co-installed sibling. Name similarity to 'nodemon' (a top-tier package) plus injection of an unreferenced dependency is the namespace-abuse / typosquat-dropper shape. ## Source: ghsa-malware (25919cd9abbeb6b978466e7fb9d006c38d61ff9c3d238f1b3ddffc6809ca819e) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
AI Analysis
Technical Summary
The nodemon-slint npm package is identified as containing malicious code that compromises the host system completely. According to the source details, any computer with this package installed or running should be considered fully compromised, with potential unauthorized access to secrets and keys. The package removal alone is insufficient to ensure system cleanup, as persistent malicious software may remain. There is no CVSS score or detailed technical vulnerability data available. No known exploits in the wild have been reported. This is a supply chain malware incident affecting the npm ecosystem.
Potential Impact
Full system compromise on any computer with the nodemon-slint package installed or running. Potential exposure and theft of all stored secrets and keys on the affected system. The attacker may have persistent access beyond the presence of the malicious package itself.
Mitigation Recommendations
Remove the nodemon-slint package immediately from all affected systems. Rotate all secrets and keys stored on the compromised machines from a separate, secure computer. Conduct a thorough investigation and remediation of the affected systems, as removal of the package does not guarantee complete eradication of malicious software.
Malicious code in nodemon-slint (npm)
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (5488028be686500c0af6b7f91ead55be9ddaeb86f3b920fce7eed6f8111b0050) Package name, README, homepage (nodemon.io), author (remy), and source tree are copied verbatim from the widely-used 'nodemon' package, with the addition of a single novel runtime dependency 'type-slint' (^3.3.7) declared in package.json. That dependency is never imported by any file reachable from the declared main (lib/nodemon.js) or from bin/, so it serves no functional purpose within this package. The only installer-facing effect of the manifest change relative to nodemon is that 'npm install nodemon-slint' also resolves and installs 'type-slint' into the installer's dependency tree, where any install-time hooks or load-time side effects it contains will run. The host package itself does not exhibit exfiltration, install-time RCE, or backdoor behavior in its own code; the risk is carried by the co-installed sibling. Name similarity to 'nodemon' (a top-tier package) plus injection of an unreferenced dependency is the namespace-abuse / typosquat-dropper shape. ## Source: ghsa-malware (25919cd9abbeb6b978466e7fb9d006c38d61ff9c3d238f1b3ddffc6809ca819e) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The nodemon-slint npm package is identified as containing malicious code that compromises the host system completely. According to the source details, any computer with this package installed or running should be considered fully compromised, with potential unauthorized access to secrets and keys. The package removal alone is insufficient to ensure system cleanup, as persistent malicious software may remain. There is no CVSS score or detailed technical vulnerability data available. No known exploits in the wild have been reported. This is a supply chain malware incident affecting the npm ecosystem.
Potential Impact
Full system compromise on any computer with the nodemon-slint package installed or running. Potential exposure and theft of all stored secrets and keys on the affected system. The attacker may have persistent access beyond the presence of the malicious package itself.
Mitigation Recommendations
Remove the nodemon-slint package immediately from all affected systems. Rotate all secrets and keys stored on the compromised machines from a separate, secure computer. Conduct a thorough investigation and remediation of the affected systems, as removal of the package does not guarantee complete eradication of malicious software.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-10117
- Osv Schema Version
- 1.7.4
- Aliases
- ["GHSA-wr24-8cj8-p627"]
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a50f27368715ace439d5902
Added to database: 07/10/2026, 13:24:03 UTC
Last enriched: 07/10/2026, 13:32:34 UTC
Last updated: 07/30/2026, 20:44:15 UTC
Views: 60
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.