Supply-chain attacks keep coming, and this one goes straight after developers who use AI coding tools. For about an hour and a half on October 19, the official OVHcloud CLI downloads on GitHub were malware.
What happened
- A compromised OVHcloud developer GitHub account replaced the release binaries for v0.11.0 through v0.15.0 between 14:47 and 16:21 Paris time (about 7:47 to 9:21 a.m. CT) on October 19. Roughly 250 downloads happened in that window.
- A customer caught it because their CI pinned the SHA-256 of the download and the build started failing. That’s the hero of the story.
- The root cause goes back a year: the developer installed a malicious editor extension tied to the Glassworm group on a personal Mac, and the stolen keys were used later.
- Source code and the build chain weren’t touched. Only the release assets were swapped, because the repo didn’t have immutable releases turned on.
What it stole
The trojaned CLI went after Cursor and VS Code state databases, Continue and Cody chat history, OpenCode’s database, Hermes agent sessions and history, the ~/.claude folder, SSH keys, Git config, .netrc, and AWS, Google Cloud, Azure, Docker, Kubernetes, npm, DigitalOcean and Terraform credentials.
What to do
- If you downloaded or updated the OVHcloud CLI in that window and ran it, treat every secret on that machine as burned and rotate it.
- Look in your temp folder for an
envchecker-directory with random digits. The stealer never cleans it up. - Update to v0.16.0, which has a signed tag and immutable release.
- If you publish on GitHub, turn on immutable releases. If you download in CI, pin hashes.
My take
Look at that target list. Agent histories and sessions are now loot, right next to cloud keys. Our AI tools know a lot about us and our systems, so treat their data folders like you treat ~/.ssh.
Have a blessed day! And Happy Hacking!
