Back to Feed
Supply ChainOct 24, 2026

OVHcloud CLI Compromised via GitHub Release Swap: Detonating the Real GlassWorm Loader and What We Found

OVHcloud CLI GitHub releases swapped with malware, impacting ~250 downloads.

Vendor Watch

Run OVHcloud?

Get an email when a reviewed story names OVHcloud, usually within the hour.

Free. Your list stays private and never appears in a subject line. One click stops it. How Vendor Watch worksPrivacy

Summary

An attacker compromised OVHcloud's CLI by swapping release binaries on GitHub, remaining undetected for 94 minutes and affecting approximately 250 downloads. The attacker used an OVHcloud contributor's GitHub account, with initial access traced back to March 2026. The compromised binaries contained a credential stealer, targeting AI agents, cloud CLIs, and sensitive configuration files.

The lesson from this incident

Full lesson

An attacker who had compromised an OVHcloud contributor's GitHub account swapped legitimate CLI release binaries with malicious ones containing a credential stealer, remaining undetected for 94 minutes and infecting roughly 250 users. The root cause is a combination of weak account security on a trusted contributor's identity and an absence of binary integrity verification in the release pipeline. This matters because developers and AI agents implicitly trust official release assets, making a tampered binary a high-yield, low-noise attack vector. The 94-minute detection gap demonstrates that without automated release integrity monitoring, supply chain substitutions can achieve significant reach before any alert fires.

What helps against this

How we list vendors

Indicators of Compromise

  • url — https://github.com/ovh/ovhcloud-cli/releases
  • malware — GlassWorm loader

Entities

OVHcloud (vendor)ovhcloud-cli (product)HassenBF (threat_actor)