Malicious code in @bikli/cli (npm)
MAL-2026-13779 · GHSA-cc5p-hf7h-rrjh
Published · Modified
Dependency scanning
Check whether @bikli/cli is in your codebase
Corgea flags malicious and compromised dependencies with reachability analysis, so you fix the packages that actually run in your application instead of working through the whole lockfile.
Description
__
Source: amazon-inspector (494fd55b20aca27d1d7353454574b7575074d84eee1367b6854c159f274c4dcc)
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.
Source: ghsa-malware (1a9b2a03c00edb8569c03384143eabcddf958064c718223cc6f733c1d268b6e5)
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.
Ready to move
Start Securing
Free, no credit card | First findings in minutes