What is confirmed
OVHcloud confirms that a compromised developer GitHub account was used to replace CLI binaries for releases 0.11.0 to 0.15.0 on 19 October from 14:47 to 16:21 Paris time.
A customer alerted the company. The malicious assets were removed and version 0.16.0 was released as a clean replacement. OVHcloud estimates around 250 downloads during the exposure window.
The malicious binaries targeted cloud credentials, SSH keys and developer configurations. OVHcloud says its source code and internal build infrastructure were not compromised.
What it means
A familiar GitHub release version number does not guarantee binary integrity when attached artifacts can be replaced after publication.
The exposure concerns versions downloaded or updated during the stated 93-minute window, not every historical installation of those versions.
What was actually affected
The described vector was a hijacked account and release artifacts, not a general compromise of OVHcloud hosting. The modified binaries included a component collecting local secrets.
Why release verification matters
The response includes immutable releases, a clean replacement and planned improvements to signatures and publisher-account controls.
What to do
If the CLI was downloaded during the window, do not rerun it: compare hashes against the official advisory and install the clean version.
Revoke or rotate keys and tokens accessible from the affected workstation, including SSH, AWS, Azure, GCP and development secrets.
Audit unexpected sign-ins and key creation; prefer short-lived credentials and verified release artifacts.
SecurCheck helps review suspicious indicators; determining actual secret exposure requires host and log investigation.