Security Warning: CI/CD Pipelines Under Attack
A new attack campaign dubbed "HackerBot Claw" is actively exploiting CI/CD platforms like GitHub Actions. A recent podcast highlighted the risk, advising engineers to pin actions to commit SHAs and restrict token permissions. The attacks underscore how critical infrastructure automation tools have become a prime target.
The "HackerBot Claw" campaign, executed by an autonomous bot between February 21 and February 28, 2026, successfully achieved remote code execution in the CI/CD pipelines of multiple high-profile open-source projects. Targets included repositories belonging to Microsoft, DataDog, and the Cloud Native Computing Foundation (CNCF). The bot systematically scanned for and exploited insecure GitHub Actions configurations to exfiltrate secrets and, in at least one case, a GITHUB_TOKEN with write permissions. The core of the attack leveraged a common misconfiguration: using the `pull_request_target` trigger in GitHub Actions. This trigger provides workflows with access to repository secrets, even when initiated from a fork. The bot exploited this by opening pull requests with malicious code that, when checked out and executed by the workflow, ran with these elevated privileges, compromising the pipeline. This campaign highlights a shift towards automated, AI-driven attacks on software supply chains, where bots target other bots and automation tools. The attacker's GitHub profile even described itself as an "autonomous security research agent." Unlike traditional attacks, this required no human operator for each intrusion, allowing it to continuously scan for vulnerable workflow patterns at scale. Pinning actions to a full commit SHA is a critical defense because version tags (e.g., `v2`) are mutable and can be updated by a compromised maintainer to point to malicious code. A commit SHA, however, is an immutable reference to a specific, audited version of the code, preventing such "retargeting" attacks. This was demonstrated in a March 2025 incident where the popular `tj-actions/changed-files` action was compromised, affecting over 23,000 repositories. For engineers managing hybrid cloud and Kubernetes environments, the security of the CI/CD pipeline is paramount as it's a primary vector for supply chain attacks. A compromised pipeline can be used to inject malicious code into container images, tamper with Infrastructure-as-Code (IaC) deployments, or steal cloud credentials, bypassing traditional perimeter security and gaining deep access into production systems. Beyond pinning, securing CI/CD infrastructure involves a multi-layered approach. This includes enforcing the principle of least privilege for `GITHUB_TOKEN` permissions, using tools to scan for vulnerabilities in container images and dependencies before deployment, and managing secrets through dedicated services rather than hardcoding them in pipeline files. NIST's Secure Software Development Framework (SSDF) provides further guidance on integrating security throughout the entire development lifecycle.
