As reported by BleepingComputer, OVHcloud disclosed a supply chain compromise of its open-source CLI tool distributed via GitHub, with versions 0.11.0 through 0.15.0 containing information-stealing malware designed to harvest secrets from developer disks. The incident, while quickly detected and contained, exposes a configuration gap that more organizations should be auditing today.

Threat Alert: As reported by BleepingComputer, OVHcloud disclosed a supply chain compromise of its open-source CLI tool distributed via GitHub, with versions 0.11.0 through 0.15.0 containing information-stealing malware designed to harvest secrets from developer disks.

What Actually Happened — and Why It Matters

The attacker gained access to a developer's GitHub account that held sufficient privileges to modify existing releases. Critically, GitHub's release immutability feature was disabled on the repository, which meant a release artifact could be swapped after publication without triggering any CI/CD pipeline validation. The entire suite of unit tests, functional tests, and CVE scanning that OVHcloud had invested in became irrelevant — the malicious binary was built locally and uploaded as a replacement artifact, never passing through the pipeline at all.

This is the core lesson: CI/CD hardening is necessary but insufficient if release artifacts can be tampered with outside the pipeline. The integrity boundary must extend to the distribution channel itself.

GlassWorm: A Pattern, Not a One-Off

Threat intelligence from OpenSourceMalware links this attack to GlassWorm, an operation active since late 2025 that has systematically targeted developer ecosystems including VSCode extensions, OpenVSX, GitHub repositories, and npm packages. The use of a Solana blockchain memo as a dead drop for second-stage payloads is a notable evasion technique — it moves C2 infrastructure off traditional servers and onto a public ledger where takedowns are effectively impossible.

The compromised GitHub account had reportedly been under attacker control for over six months, with a scripted history rewrite dating to March 2026 — meaning the eventual CLI compromise may have been the visible culmination of a longer-dwell reconnaissance operation.

Who Is at Risk

  • Direct victims: Any developer or sysadmin who downloaded OVHcloud CLI versions 0.11.0–0.15.0 between October 19, 2026 14:47 UTC and 16:21 UTC.
  • Broader exposure: Organizations consuming open-source tools from GitHub repositories where release immutability is not enforced — particularly small-to-midsize projects where individual developer accounts hold elevated release permissions.
  • Higher-risk environments: CI/CD runners, developer workstations with stored cloud credentials, and any system where the CLI was used in automation scripts with API keys or tokens on disk.

Shield53 Recommendations

Immediate Actions

  • If you downloaded affected versions: Remove the CLI tool immediately, scan the host for indicators of compromise, and rotate all secrets that existed on that disk — API tokens, SSH keys, cloud credentials, .env files, and kubeconfigs. Assume total secret compromise.
  • Verify your version: Version 0.10.0 and 0.16.0 are confirmed clean. Anything in between should be treated as malicious.
  • Enable GitHub release immutability on all organizational repositories. This prevents modification of published release assets and is available in repository settings under Releases → Release immutability.

Hardening — Beyond This Incident

  • Adopt Sigstore or equivalent artifact signing so consumers can cryptographically verify that downloaded binaries match what the CI/CD pipeline produced — not just what was uploaded to a release page.
  • Enforce least privilege on release publishing. Individual developer accounts should not have the ability to overwrite release artifacts. Use machine identities or protected publishing workflows.
  • Monitor for dormant account compromise. The six-month dwell time in this case is a red flag for credential hygiene. Implement GitHub security alerts, review access tokens, and require SSO with MFA for any account with write access to public-facing repositories.
  • Block Solana memo and similar blockchain-based C2 channels at network egress where feasible. While content on-chain is immutable, the initial connection to read memo instructions is observable.

This incident reinforces a uncomfortable truth: your CI/CD pipeline's security only matters if it is the only path to your release artifacts. When distribution channels allow out-of-band modification, the most sophisticated pipeline hardening becomes theater.