Malicious code in @bikli/cli (npm)
The npm package @bikli/cli versions 1.0.9, 1.1.0, and 1.1.1 contain malicious code. Installation or execution of these versions may fully compromise the host system, potentially exposing all stored secrets and keys. Although no static or behavioral evidence of install-time code execution or backdoors was detected by Amazon Inspector, the GHSA advisory warns that any system with this package should be considered fully compromised. Immediate removal and secret rotation are strongly recommended.
AI Analysis
Technical Summary
The @bikli/cli npm package versions 1.0.9, 1.1.0, and 1.1.1 have been identified as malicious. While automated static and behavioral scans did not detect install-time code execution or credential theft mechanisms, the GHSA advisory indicates that the package effectively compromises any system on which it is installed or running. This implies the presence of malicious code capable of full system compromise, warranting urgent remediation actions.
Potential Impact
Systems with the affected @bikli/cli package versions installed or running should be considered fully compromised. All secrets and keys stored on such systems are at risk and must be rotated immediately from a secure, uncompromised environment. Removing the package alone may not eliminate all malicious components introduced by the package, as full control may have been granted to an attacker.
Mitigation Recommendations
Remove the affected versions (=1.0.9, =1.1.0, =1.1.1) of the @bikli/cli package immediately. Rotate all secrets and keys stored on the compromised system from a different, secure computer. Due to the potential for persistent compromise, consider rebuilding the affected system to ensure complete remediation. No official patch or fix is available; the package itself is malicious.
Malicious code in @bikli/cli (npm)
Description
The npm package @bikli/cli versions 1.0.9, 1.1.0, and 1.1.1 contain malicious code. Installation or execution of these versions may fully compromise the host system, potentially exposing all stored secrets and keys. Although no static or behavioral evidence of install-time code execution or backdoors was detected by Amazon Inspector, the GHSA advisory warns that any system with this package should be considered fully compromised. Immediate removal and secret rotation are strongly recommended.
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 @bikli/cli npm package versions 1.0.9, 1.1.0, and 1.1.1 have been identified as malicious. While automated static and behavioral scans did not detect install-time code execution or credential theft mechanisms, the GHSA advisory indicates that the package effectively compromises any system on which it is installed or running. This implies the presence of malicious code capable of full system compromise, warranting urgent remediation actions.
Potential Impact
Systems with the affected @bikli/cli package versions installed or running should be considered fully compromised. All secrets and keys stored on such systems are at risk and must be rotated immediately from a secure, uncompromised environment. Removing the package alone may not eliminate all malicious components introduced by the package, as full control may have been granted to an attacker.
Defensive Guidance
Remove the affected versions (=1.0.9, =1.1.0, =1.1.1) of the @bikli/cli package immediately. Rotate all secrets and keys stored on the compromised system from a different, secure computer. Due to the potential for persistent compromise, consider rebuilding the affected system to ensure complete remediation. No official patch or fix is available; the package itself is malicious.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-13779
- Osv Schema Version
- 1.7.4
- Aliases
- ["GHSA-cc5p-hf7h-rrjh"]
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a7c9b46bf8831d539cdd298
Added to database: 08/12/2026, 16:11:50 UTC
Last enriched: 08/12/2026, 16:54:53 UTC
Last updated: 08/12/2026, 16:54:53 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.
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.