Malicious code in root-locator (npm)
The npm package 'root-locator' versions 1.1.0 and 1.2.0 contain malicious code or depend on code that is malicious. Installing or running this package can lead to a full compromise of the affected computer. Secrets and keys stored on the compromised system should be rotated immediately from a different, secure machine. Removing the package alone may not eliminate all malicious software introduced by it.
AI Analysis
Technical Summary
The 'root-locator' npm package versions 1.1.0 and 1.2.0 have been identified as containing malicious code or dependencies with malicious code. According to sources including Amazon Inspector and the GitHub Security Advisory for malware, any system with this package installed or running should be considered fully compromised. The malicious code can grant an attacker full control over the affected system, posing a severe security risk. Immediate remediation involves removing the package and rotating all secrets and keys from a secure environment, though full eradication of the compromise cannot be guaranteed by removal alone.
Potential Impact
Systems with 'root-locator' versions 1.1.0 or 1.2.0 installed or running are at risk of full compromise. Attackers may gain complete control over the affected computer, potentially accessing or exfiltrating sensitive data, including secrets and keys. This compromises the confidentiality, integrity, and availability of the system and its data.
Mitigation Recommendations
Remove the 'root-locator' package versions 1.1.0 and 1.2.0 immediately from all affected systems. Rotate all secrets, keys, and credentials that were stored or used on the compromised systems, performing this rotation from a separate, secure machine. Due to the potential for persistent malicious software beyond the package itself, consider conducting a full system forensic analysis and remediation. No official patch or fix is indicated; the package should be considered untrusted and avoided.
Malicious code in root-locator (npm)
Description
The npm package 'root-locator' versions 1.1.0 and 1.2.0 contain malicious code or depend on code that is malicious. Installing or running this package can lead to a full compromise of the affected computer. Secrets and keys stored on the compromised system should be rotated immediately from a different, secure machine. Removing the package alone may not eliminate all malicious software introduced by 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 'root-locator' npm package versions 1.1.0 and 1.2.0 have been identified as containing malicious code or dependencies with malicious code. According to sources including Amazon Inspector and the GitHub Security Advisory for malware, any system with this package installed or running should be considered fully compromised. The malicious code can grant an attacker full control over the affected system, posing a severe security risk. Immediate remediation involves removing the package and rotating all secrets and keys from a secure environment, though full eradication of the compromise cannot be guaranteed by removal alone.
Potential Impact
Systems with 'root-locator' versions 1.1.0 or 1.2.0 installed or running are at risk of full compromise. Attackers may gain complete control over the affected computer, potentially accessing or exfiltrating sensitive data, including secrets and keys. This compromises the confidentiality, integrity, and availability of the system and its data.
Mitigation Recommendations
Remove the 'root-locator' package versions 1.1.0 and 1.2.0 immediately from all affected systems. Rotate all secrets, keys, and credentials that were stored or used on the compromised systems, performing this rotation from a separate, secure machine. Due to the potential for persistent malicious software beyond the package itself, consider conducting a full system forensic analysis and remediation. No official patch or fix is indicated; the package should be considered untrusted and avoided.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-14009
- Osv Schema Version
- 1.7.4
- Aliases
- ["GHSA-57g4-vm3v-74xg"]
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a7f43f0bf8831d5395d7626
Added to database: 08/14/2026, 16:36:00 UTC
Last enriched: 08/14/2026, 16:46:04 UTC
Last updated: 08/14/2026, 16:46:04 UTC
Views: 2
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.