OVHcloud is warning developers that attackers compromised its open-source command-line interface repository on GitHub and modified versions 0.11.0 through 0.15.0 to distribute information-stealing malware, BleepingComputer reports.

CEO Octave Klaba disclosed the breach, saying the malware's purpose was to "retrieve secrets from the disk." Only people who installed or updated during the exposure window were affected; the attack targeted macOS (Intel and ARM), Linux (x86_64 and ARM64), and Windows x86-64 binaries.

The striking detail is that none of OVHcloud's own defenses fired.

BleepingComputer reports the compromised release was detected and blocked after a customer reported it, and Klaba confirmed "the entire set of CI/CD pipelines with unit tests, functional tests, CVE detection, etc., were not impacted."

SQ Magazine explains that the customer's CI job pinned the SHA-256 of the Linux arm64 archive and began failing, prompting a public GitHub issue (number 300) that led OVHcloud to delete the swapped files.

The publisher's own checksum file had been swapped too, so it could not have raised the alarm — the only effective control sat outside the repository entirely.

Klaba shared, per BleepingComputer, that GitHub's release immutability setting had been disabled, allowing a sufficiently privileged account to modify existing releases without passing CI/CD checks; the setting only protects releases created after it is enabled.

The attackers uploaded locally built, malware-infected packages rather than tampering with CI/CD pipelines, researchers confirmed.

OpenSourceMalware, cited by BleepingComputer, links the attack to a GlassWorm operation known for campaigns since late 2025 across the VSCode, OpenVSX, GitHub, and npm ecosystems, noting the GitHub account had been compromised for more than half a year with a scripted history rewrite in March 2026.

Anyone who ran an affected binary should treat all secrets on the machine as compromised, since the CLI keeps OVHcloud API credentials in ~/.ovh.conf and reads them from environment variables.

Klaba urges a system cleanup and full secret rotation: "The quality of the binary is poor but it can go all the way." Homebrew users were protected because the cask pinned original SHA-256 hashes, and source builds and Docker images were unaffected.

OVHcloud has promised a detailed postmortem.