Malicious code in enquriers (npm)
The 'enquriers' npm package is identified as malicious primarily due to its name similarity to the popular 'enquirer' package, which may cause confusion. Although no direct malicious payload, exfiltration, or install-time code execution was found in the package contents, the package is considered fully compromising if installed or running on a system. Systems with this package should be treated as compromised, and all secrets and keys should be rotated from a different machine. Removal of the package alone may not fully remediate the compromise.
AI Analysis
Technical Summary
The 'enquriers' package on npm is flagged as malicious mainly because it closely resembles the widely-used 'enquirer' package, potentially tricking users into installing it. While static analysis did not reveal explicit malicious code such as payloads or credential theft mechanisms, the package is considered a severe threat by some sources, which state that any system with this package installed should be treated as fully compromised. This discrepancy suggests that the threat assessment relies heavily on the risk of name confusion and potential indirect compromise rather than confirmed technical exploitation within the package itself.
Potential Impact
If the 'enquriers' package is installed or running on a system, the system should be considered fully compromised. This implies that attackers may have gained control or installed additional malicious software beyond the package itself. Consequently, all secrets and keys stored on the affected system are at risk and must be rotated from a secure, uncompromised environment. Removal of the package does not guarantee full remediation due to potential persistence mechanisms.
Mitigation Recommendations
No official patch or fix is available for this package. The recommended mitigation is to immediately remove the 'enquriers' package from any affected systems. Additionally, assume full system compromise: rotate all secrets and credentials from a different, secure machine. Conduct a thorough investigation and remediation of the affected system to ensure no residual malicious software remains.
Malicious code in enquriers (npm)
Description
The 'enquriers' npm package is identified as malicious primarily due to its name similarity to the popular 'enquirer' package, which may cause confusion. Although no direct malicious payload, exfiltration, or install-time code execution was found in the package contents, the package is considered fully compromising if installed or running on a system. Systems with this package should be treated as compromised, and all secrets and keys should be rotated from a different machine. Removal of the package alone may not fully remediate the compromise.
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 'enquriers' package on npm is flagged as malicious mainly because it closely resembles the widely-used 'enquirer' package, potentially tricking users into installing it. While static analysis did not reveal explicit malicious code such as payloads or credential theft mechanisms, the package is considered a severe threat by some sources, which state that any system with this package installed should be treated as fully compromised. This discrepancy suggests that the threat assessment relies heavily on the risk of name confusion and potential indirect compromise rather than confirmed technical exploitation within the package itself.
Potential Impact
If the 'enquriers' package is installed or running on a system, the system should be considered fully compromised. This implies that attackers may have gained control or installed additional malicious software beyond the package itself. Consequently, all secrets and keys stored on the affected system are at risk and must be rotated from a secure, uncompromised environment. Removal of the package does not guarantee full remediation due to potential persistence mechanisms.
Mitigation Recommendations
No official patch or fix is available for this package. The recommended mitigation is to immediately remove the 'enquriers' package from any affected systems. Additionally, assume full system compromise: rotate all secrets and credentials from a different, secure machine. Conduct a thorough investigation and remediation of the affected system to ensure no residual malicious software remains.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-5384
- Osv Schema Version
- 1.7.4
- Aliases
- ["GHSA-c8vc-qqjp-wg87"]
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a4f6c6c68715ace4315a8ca
Added to database: 07/09/2026, 09:39:56 UTC
Last enriched: 07/09/2026, 10:05:57 UTC
Last updated: 07/26/2026, 09:02:11 UTC
Views: 6
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.