A trusted package release can now steal the secrets of the systems that install it. In this case, the compromise was not just tampering with code. It turned a normal CLI update into a way to pull GitHub tokens, npm credentials, SSH keys, .env files, shell history, and cloud secrets from downstream environments and CI runs.
Socket says @bitwarden/cli@2026.4.0 was published with malicious code in bw1.js after attackers abused a compromised GitHub Action in Bitwarden’s CI/CD pipeline. The rogue version is no longer on npm, but the impact is broader than the package itself because the same workflow path can expose secrets already present in build jobs and developer machines.
The non-obvious risk is persistence. Once CI secrets or developer credentials are exposed, patching the package does not undo the theft, and the stolen tokens can be used to push more malicious workflow changes or package updates.