Which versions of @bitwarden/cli are malicious?

The following npm versions of @bitwarden/cli are flagged malicious: 2026.4.0. Treat any of these as compromised.

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

Remove @bitwarden/cli from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

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

If @bitwarden/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 @bitwarden/cli part of a known attack campaign?

Yes — @bitwarden/cli is associated with the GHSA-g98r-qjhg-4fmr 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 @bitwarden/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 @bitwarden/cli (version 2026.4.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @bitwarden/cli across your stack and pipelines.

Malicious package

@bitwarden/clinpm

Malicious code in @bitwarden/cli (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-3020

Immediate action

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

npm uninstall @bitwarden/cli

What this malware does

The package @bitwarden/cli was found to contain malicious code.

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

1 flagged

2026.4.0

Indicators of compromise (SHA-256)

8a8c7958926d5ec3795102e9114dfaa649ae3160afb9159ec2c46f044018b776

c6fb2336936a86f37fc2018f8e68dc9989ffc3e79aa23297bf470de178201f50

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @bitwarden/cli (version 2026.4.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @bitwarden/cli across your stack and pipelines.
If you installed it — respond
Remove @bitwarden/cli from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If @bitwarden/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 @bitwarden/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. @bitwarden/cli on npm has been identified as a malicious package (version 2026.4.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-g98r-qjhg-4fmr

References

github.com

Credits

Amazon Inspector · finder

Detect & block this

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

Malware detection Runtime egress monitoring