BITWARDEN CLI NPM PACKAGE POISONED WITH CREDENTIAL STEALER

A malicious version of the Bitwarden CLI package appeared on the npm registry with a credential-stealing payload. The compromised @bitwarden/cli package was designed to harvest sensitive developer credentials and propagate to dependent projects. The attack exploited npm's package distribution system to distribute the malware to developers downloading the tool. Bitwarden, a popular open-source password manager, uses its CLI tool for command-line access to stored credentials—making it an attractive target for attackers seeking to compromise developer environments. The malicious payload enabled lateral movement across development pipelines, potentially spreading to other projects that depend on the Bitwarden CLI. This amplification mechanism could have exposed credentials across multiple organizations if the compromise had remained undetected longer. Bitwarden promptly removed the compromised package once the threat was identified. The organization has not disclosed the exact infection vector used to upload the malicious code, though npm package repositories remain vulnerable to account takeovers and dependency confusion attacks. This incident underscores ongoing security challenges in open-source package ecosystems. Developers often install tools with elevated permissions, making package poisoning a direct path to credential theft. Similar attacks have targeted other widely-used packages, including those from Node.js, Python, and Ruby repositories. Users who installed the compromised @bitwarden/cli package during the vulnerability window should assume their credentials may be exposed and rotate sensitive access tokens immediately. Bitwarden recommends reviewing npm logs to verify installation timestamps and updating to the latest verified version from official sources. The npm registry has implemented several protections including two-factor authentication and package signature verification, but human error and account compromise remain vectors for supply chain attacks. Security teams should monitor dependency updates and implement approval workflows before deploying package upgrades to production environments.