MalwarePublished 12 Aug 2026

@bikli/cli (npm) · Malicious Code

Affects @bikli/cliSource GCVE Database

Malicious package : remove @bikli/cli and rotate any secrets on hosts that installed it.

Data as of 12 Aug 2026, 16:54 UTC

Classification

Malicious package

Published to npm · OSV MAL-2026-13779

What to do

Remove @bikli/cli from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.

Affected software

Product	Affected	Fixed in
npm@bikli/cli	Affected =1.1.1 =1.1.0 =1.0.9	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

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.

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.

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.

References

Community reviews

Loading reviews…

What to do

Affected software

Description

AI analysisMachine-generated, updated 12 Aug 2026, 16:54 UTC

Technical details

References

Community reviews