Every CLI You Run Has Your SSH Keys, Your `.env`, and Your Cloud Tokens. Here's a 100-Line Fence Around That.
In April 2026, a malicious version of the Bitwarden CLI was published to npm. It was live for about ninety minutes. In that window it read SSH keys, .env files, and AWS, Azure and GCP credentials off the machine of anyone who installed it. In October, the official OVHcloud CLI's repository was briefly compromised the same way — a bad build, caught and blocked in 94 minutes, but only after a…
In April 2026, a malicious version of the Bitwarden CLI was published on npm. This version quickly accessed SSH keys, `.env` files, and cloud credentials from any machine on which it was installed. Similarly, the official OVHcloud CLI repository was compromised in October due to a bad build, though it was detected and blocked within 94 minutes.
Both incidents highlight the risk of trusted tools with compromised updates, which can circumvent antivirus scans and run with full access to a user's home folder, including `.ssh`, cloud credentials, browser profiles, and `.env` files.
A new tool called ghl-jail has been designed to mitigate this risk. It runs a single command and restricts its operations to a designated project folder, preventing the tool from accessing any other parts of the user's system. This includes denying access to `.ssh` directories, cloud credentials, and environment tokens. By default, ghl-jail also runs without network access, further limiting potential harm.
This approach is meant for harm reduction, providing a protective barrier around a tool before deciding to trust it, rather than offering a complete security guarantee. Ghl-jail is open-source, free, and only available for Windows, and its website and GitHub repository are linked in the source material.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
