Which versions of @bikli/cli are malicious?

The following npm versions of @bikli/cli are flagged malicious: 1.0.9, 1.1.0, 1.1.1. Treat any of these as compromised.

How do I remediate @bikli/cli if I installed it?

@bikli/cli is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed @bikli/cli — how do I know if it already compromised me?

If @bikli/cli was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is @bikli/cli part of a known attack campaign?

Yes — @bikli/cli is associated with the GHSA-cc5p-hf7h-rrjh, IN-MAL-2026-017477, IN-MAL-2026-017475, IN-MAL-2026-017476 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find @bikli/cli across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @bikli/cli (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @bikli/cli across your stack and pipelines.

Malicious package

@bikli/clinpm

@bikli/cli is a confirmed malicious npm package (MAL-2026-13779) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.9, 1.1.0, 1.1.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @bikli/cli (npm)

MAL-2026-13779

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall @bikli/cli

What this malware does

No a static rule matches and no traced behavioral findings were produced for this package version. The scanned files contain no evidence of install-time code execution from external sources, credential or environment scraping, silent relay of caller data to hardcoded destinations, or persistent backdoor mechanisms.

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.

Malicious versions

3 flagged

1.0.91.1.01.1.1

Indicators of compromise (SHA-256)

1a9b2a03c00edb8569c03384143eabcddf958064c718223cc6f733c1d268b6e5

494fd55b20aca27d1d7353454574b7575074d84eee1367b6854c159f274c4dcc

86d6c7f2d723a740f82f63a9de880ffb8d7f3312720d4a7da46e90d9bf01a6d4

9f28f9dbabf78f07b1662642b7a3181843e8d47e853cb442773f16c4b01a42ec

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @bikli/cli (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @bikli/cli across your stack and pipelines.
If you installed it — respond
@bikli/cli is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If @bikli/cli was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks @bikli/cli before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. @bikli/cli on npm has been identified as a malicious package (versions 1.0.9, 1.1.0, 1.1.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-cc5p-hf7h-rrjhIN-MAL-2026-017477IN-MAL-2026-017475IN-MAL-2026-017476

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @bikli/cli-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database