GlassWorm Backdoors OVHcloud CLI on GitHub: What Developer and Cloud Security Teams Must Do Now
Executive Summary
In October 2026, OVHcloud disclosed that its open-source CLI tool hosted on GitHub was backdoored by the GlassWorm threat actor after attackers compromised a developer's GitHub account that had been silently controlled since at least March 2026. Versions 0.11.0 through 0.15.0 were trojanized with an infostealer designed to harvest secrets stored on disk. The malicious releases were live for approximately 94 minutes before detection following a customer report. GitHub's release immutability feature had been disabled, allowing tampered binaries to bypass CI/CD pipelines entirely. Affected platforms include macOS, Linux, and Windows, and all secrets on exposed machines should be treated as compromised.
This incident underscores a growing and sophisticated pattern in supply-chain attacks where threat actors target developer tooling ecosystems—GitHub, npm, VSCode, and OpenVSX—to silently poison trusted distribution channels. With GlassWorm active since late 2025 and expanding its targeting scope, organizations relying on open-source CLI tools and package managers face escalating credential-theft risk with minimal detection windows.
Why This Matters Now
GlassWorm's campaign against developer ecosystems is accelerating in 2026, having now hit GitHub, npm, VSCode, and OpenVSX in rapid succession. As cloud infrastructure increasingly depends on CLI tooling and automated pipelines, a single compromised developer account can silently exfiltrate production credentials at scale—making supply-chain hygiene and egress monitoring urgent priorities for any cloud-native organization.
Attack Path Analysis
GlassWorm threat actors compromised a developer's GitHub account (dormant for over six months post-compromise) to gain write access to the OVHcloud CLI repository, then silently replaced legitimate release binaries with locally-built trojanized versions across five version tags (0.11.0–0.15.0) by exploiting a disabled GitHub release immutability setting — bypassing all CI/CD pipeline checks. The malicious binaries, which used a hidden preinstall.js loader and a Solana blockchain memo dead-drop for second-stage payload delivery, executed on developer and administrator endpoints across macOS, Linux, and Windows to harvest secrets from disk and transmit them to attacker-controlled infrastructure, resulting in widespread credential compromise for any user who ran an affected build.
Kill Chain Progression
This analysis maps confirmed threat intelligence to the full cloud kill chain to show where defensive gaps would emerge as an attack progresses.
Initial Compromise
Description
Attackers compromised a developer's GitHub account, likely through phishing or credential theft, at least six months prior to the attack. This account had write access to the OVHcloud CLI repository. The absence of GitHub release immutability allowed the attacker to overwrite existing release artifacts (v0.11.0–v0.15.0) with trojanized binaries built locally — entirely outside the CI/CD pipeline — without triggering any automated security checks. The CNSF Cloud Native Security Fabric, with its inline enforcement and real-time inspection capabilities, could have flagged anomalous automation patterns such as out-of-band binary pushes or unexpected release mutations against the repository's behavioral baseline.
MITRE ATT&CK® Techniques
Compromise Software Supply Chain
Compromise Accounts: Cloud Accounts
Compromise Host Software Binary
Unsecured Credentials: Credentials In Files
Obfuscated Files or Information
Application Layer Protocol: Web Protocols
Exfiltration Over Web Service
Stage Capabilities: Upload Malware
Potential Compliance Exposure
Mapping incident impact across multiple compliance frameworks.
NIST SP 800-53 Rev. 5 – Provenance
Control ID: SR-4
CISA Zero Trust Maturity Model 2.0 – Continuous Monitoring of Application Integrity
Control ID: Application Pillar — App Security (Visibility & Analytics)
NIS2 Directive – Supply Chain Security and Secure Software Development
Control ID: Article 21 — Cybersecurity Risk Management Measures
PCI DSS 4.0 – Inventory and Integrity of Bespoke and Custom Software
Control ID: Requirement 6.3.2
DORA (EU Regulation 2022/2554) – Software Supply Chain Risk and Vendor Tool Integrity
Control ID: Article 28 — ICT Third-Party Risk Management
ISO/IEC 27001:2022 – Secure Software Development and Release Integrity Controls
Control ID: Annex A 8.30 — Outsourced Development / A 8.25 — Secure Development Lifecycle
Sector Implications
Industry-specific impact of the vulnerabilities, including operational, regulatory, and cloud security risks.
Computer Software/Engineering
GlassWorm's backdoored OVHcloud CLI directly targets software engineers via compromised GitHub releases, enabling infostealer exfiltration of developer secrets, API keys, and CI/CD credentials across multicloud environments.
Information Technology/IT
IT administrators using OVHcloud CLI for cloud automation face supply-chain infostealer risk; compromised credentials enable lateral movement and exfiltration, undermining Zero Trust segmentation and egress security controls.
Computer/Network Security
Security teams face compounded supply-chain risk as GlassWorm bypassed CI/CD pipelines via GitHub release mutability, exposing gaps in egress policy enforcement, anomaly detection, and multicloud visibility controls.
Internet
Cloud and hosting platform ecosystems like OVHcloud are prime supply-chain targets; backdoored CLI tools enable mass secret harvesting from internet infrastructure operators, with downstream exfiltration evading standard encrypted traffic controls.
Sources
- OVHcloud CLI releases backdoored on GitHub to steal developer secretshttps://www.bleepingcomputer.com/news/security/ovhcloud-cli-releases-backdoored-on-github-to-steal-developer-secrets/Verified
- Octave Klaba (OVHcloud CEO) disclosure on X (Twitter) regarding compromised CLI versionshttps://x.com/olesovhcom/status/2112225308589834260Verified
- OpenSourceMalware: GlassWorm Hacks OVHcloud CLI Toolhttps://opensourcemalware.com/blog/glassworm-hacks-ovh-clouds-cli-toolVerified
- GlassWorm malware hits 400+ code repos on GitHub, npm, VSCode, OpenVSXhttps://www.bleepingcomputer.com/news/security/glassworm-malware-hits-400-plus-code-repos-on-github-npm-vscode-openvsx/Verified
- Self-spreading GlassWorm malware hits OpenVSX VS Code registrieshttps://www.bleepingcomputer.com/news/security/self-spreading-glassworm-malware-hits-openvsx-vs-code-registries/Verified
Frequently Asked Questions
Cloud Native Security Fabric Mitigations and ControlsCNSF
Based on the attack progression modeled above, these are the defensive controls that would constrain each stage.
Aviatrix Zero Trust CNSF is directly relevant to this supply chain attack because the malicious CLI binaries executed across developer and administrator endpoints connected to cloud environments, creating lateral reach and exfiltration pathways that segmentation and egress enforcement could have meaningfully constrained. By limiting workload reachability and controlling outbound traffic from affected endpoints, the blast radius across OVHcloud credentials, CI/CD systems, and downstream cloud infrastructure would likely have been reduced even after the trojanized binary executed.
Control: Cloud Native Security Fabric (CNSF)
Mitigation: Inline behavioral inspection across cloud-connected build and release workflows could have surfaced anomalous out-of-band binary push patterns, likely reducing the window during which trojanized artifacts remained undetected in the release pipeline.
Control: Zero Trust Segmentation
Mitigation: Identity-aware, least-privilege segmentation policies enforced on repository roles and cloud-connected build systems could have constrained the scope of what a single compromised identity was permitted to affect, reducing the attacker's effective release authority.
Control: East-West Traffic Security
Mitigation: East-west enforcement monitoring workload-to-workload communication could have detected and constrained anomalous lateral flows originating from developer endpoints newly behaving as credential sources transmitting toward attacker infrastructure, reducing the attacker's ability to move freely across connected systems.
Control: Multicloud Visibility & Control
Mitigation: Centralized traffic observability across cloud-connected developer environments could have surfaced repeated or anomalous outbound connections toward Solana RPC endpoints, reducing the attacker's ability to operate an undetected blockchain-based C2 channel over time.
Control: Egress Security & Policy Enforcement
Mitigation: Outbound egress controls with FQDN filtering and policy-enforced destination allowlists would likely have constrained the malware's ability to reach attacker-controlled exfiltration infrastructure, reducing the volume of secrets successfully transmitted even from machines where the binary had already executed.
Had prior CNSF controls constrained lateral movement and egress pathways, the pool of successfully exfiltrated credentials would likely have been smaller, reducing the number of downstream cloud environments and CI/CD systems reachable by the attacker and narrowing the scope of required incident response and secret rotation.
Impact at a Glance
Affected Business Functions
- Cloud Infrastructure Management (CLI/API Automation)
- Developer Secrets and Credentials Management
- CI/CD Pipeline Integrity and Software Supply Chain
- Customer-Facing Hosting and Cloud Service Operations
Estimated downtime: 1 days
Estimated loss: N/A
Developer and system administrator secrets stored on disk were targeted, including API keys, authentication tokens, SSH private keys, and cloud service credentials for OVHcloud-managed environments. All users who executed a compromised CLI binary (versions 0.11.0 through 0.15.0) on macOS (Intel/ARM), Linux (x86_64/ARM64), or Windows (x86-64) should treat all on-disk secrets as fully compromised. The exposure window spanned approximately 94 minutes on October 19, 2026 (14:47 to 16:21). The malware was described as poor quality but capable of full secret exfiltration. Downstream risk includes unauthorized access to OVHcloud-managed cloud resources, infrastructure takeover, and lateral movement into connected enterprise environments.
Recommended Actions
Key Takeaways & Next Steps
- • Enforce Zero Trust Segmentation on developer identity and release pipelines: Apply least-privilege identity-based policies (NIST.800-53.AC-6, ZTMM.Network) to restrict which accounts can publish or modify release artifacts; require secondary approval workflows for any release mutation to prevent a single compromised account from weaponizing official distribution channels.
- • Deploy Egress Security & Policy Enforcement with FQDN filtering on developer endpoints and CI/CD runners: Block outbound connections to unauthorized or anomalous destinations (including blockchain RPC endpoints used as C2 dead-drops) using egress firewall controls aligned to ZTMM.Data and NIST.CSF.PR.DS-5 to choke off both C2 beacon traffic and secret exfiltration channels.
- • Activate Multicloud Visibility & Control with behavioral baselining for developer workstations and pipeline agents: Use centralized traffic observability to detect anomalous outbound patterns — such as unexpected Solana RPC connections, high-volume file reads followed by outbound HTTPS bursts, or new external destinations post-binary execution — aligned to ZTMM.CrossCutting.Visibility and NIST.800-53.AU-6.
- • Integrate Inline IPS (Suricata) signatures for known GlassWorm and supply chain infostealer indicators: Ensure that signature sets covering known GlassWorm binary hashes, preinstall.js loader patterns, and Solana memo dead-drop patterns are active on egress inspection paths (PCI.4.0.6.4.1, NIST.800-53.SI-4) to block payload delivery and exfiltration traffic at the network layer.
- • Leverage CNSF Cloud Native Security Fabric for real-time, inline enforcement across the software delivery control plane: Instrument the artifact publication and distribution pipeline with cloud-native enforcement policies that can detect out-of-band binary modifications, repository history rewrites, and anomalous CI/CD bypass patterns in real time, aligned to ZTMM.CrossCutting.Automation and NIST.CSF.ID.RA-3, ensuring that even a privileged compromised account cannot silently introduce malicious artifacts into trusted release channels.
