Act nowSupply chain

OVHcloud CLI was hijacked to steal secrets, including AI tool data

For about 94 minutes on 19 Oct 2026, OVHcloud's official command-line tool was replaced with a version that steals credentials. What it took, and what to do if you ran it.

How urgent

Act now

Who is affected

Anyone who downloaded or ran OVHcloud CLI versions 0.11.0 to 0.15.0 on 19 Oct 2026 between 14:47 and 16:21 (UTC+2)

What to do

If you ran it in that window, delete it, update to 0.16.0 and rotate every secret stored on that computer

Published 22 Oct 2026 · Sources last checked 22 Oct 2026No. 7 / 87

What happened

On 19 October 2026 an attacker replaced the downloadable files of the OVHcloud CLI, the official command-line tool for managing OVHcloud services. The replacement versions, 0.11.0 to 0.15.0, contained a program that searches the computer for secretsSecret (API key, token, password) Any piece of text that proves to a service that you are allowed in, such as an API key, a database password or an access token. Tap again to open the glossary and sends them out.

OVHcloud's own advisory, rated High, says the bad files were online between 14:47 and 16:21 (UTC+2). That is about 94 minutes. The advisory cites about 250 downloads. A customer noticed suspicious activity and reported it on GitHub at 15:50.

How it got in

According to OVHcloud's post-mortem, the attacker used the GitHub account of one of its developers and swapped the release files using stolen keys. The source code and build process were not touched, and no other repository was affected.

OVHcloud traces the root cause back to October 2025. The developer installed a code-editor extension on a personal laptop that was linked to a known threat group called Glassworm. The advisory says personal repositories of the same account were compromised again in March 2026. It also says the repository was not set up to prevent releases from being changed after publishing, and that this is now fixed across the organisation.

What the malware looked for

The advisory lists what the stealer collected from the computer it ran on:

  • Data stored by code editors and AI assistants: VS Code, Cursor, Continue, Sourcegraph Cody, OpenCode, Hermes and Claude.
  • Cloud credentials for AWS, Google Cloud, Azure and DigitalOcean.
  • Docker and Kubernetes configuration.
  • Package and infrastructure settings: npm, Terraform, .netrc and global Git configuration.
  • SSH keys.

It copied the files into a folder named envchecker- followed by random digits in the temporary directory, which is never deleted, then packed and uploaded them.

Who is affected

Only people who downloaded or ran those versions during the window. The advisory says versions up to 0.10.0 are fine, and so are 0.16.0 and later. Anyone who downloaded 0.11.0 to 0.15.0 before the window is not affected either. If you never used the OVHcloud CLI, nothing here applies to you.

What to do

  1. Work out if you were exposed. Did you download or run the OVHcloud CLI on 19 October, between 14:47 and 16:21 (UTC+2)? The advisory includes file fingerprints you can compare without running the file.
  2. Look in your temporary folder for any folder starting with envchecker-.
  3. If you were exposed, rotate or disable every secret that computer could reach: cloud keys, SSH keys, API keys, tokens and the credentials AI tools hold.
  4. Delete the affected files and install version 0.16.0 or later.

If you build with AI tools

Our advice, not from the advisory: this attack is a good reminder that the keys on your laptop are only as safe as the tools you install. Keep API keys out of plain files where you can, give each tool its own key with the smallest permissions, and write down where each key lives so you can rotate it in minutes. Our runbook #2 (API Key Incident) walks through exactly that.

Terms explained in this article

  • Supply chain attack: An attack that reaches you through something you already trust and install, such as a code package, a tool or a provider.

Comments

No account needed. Add a nickname if you like, or leave it empty to comment anonymously. Comments are reviewed before they appear. Links are not allowed.

    We store your comment, your nickname and a scrambled form of your connection that we use only to limit spam. We do not store your IP address or set cookies. Cloudflare Turnstile checks that you are not a bot.

    Sources and verification

    We use primary sources first and say when we rely on a news report. Dates are the day we last checked each source.

    Spotted a mistake? Email [email protected] and we will correct it and note the change.

    Get the free runbooks

    One-page security checklists for founders who build with AI. You get a confirmation email first, then the runbooks.

    Send me the runbooks