In a startling display of automated aggression, a supply chain attack dubbed “Megalodon” has infected over 5,500 GitHub repositories in a single six-hour window. Discovered by cybersecurity researchers at SafeDep on May 18, 2026, this campaign represents a significant escalation in the targeting of CI/CD pipelines, leveraging a technique known as direct Poisoned Pipeline Execution (d-PPE) to harvest sensitive credentials at scale.
The Attack Vector: Direct Poisoned Pipeline Execution
Unlike traditional supply chain attacks that compromise package dependencies, Megalodon targeted the build process itself. Attackers utilized accounts with write access to inject malicious GitHub Actions workflows directly into repository definitions. When these workflows executed, they triggered attacker-controlled commands designed to exfiltrate secrets from the CI/CD environment.
The primary targets were high-value credentials, including:
- Cloud Provider Keys: AWS, Google Cloud, and Microsoft Azure credentials.
- Authentication Tokens: SSH keys, API tokens, and GitHub Actions OIDC tokens.
- Deployment Secrets: Environment variables used for production deployments.
Automation and Evasion Tactics
The Megalodon campaign was characterized by its industrial-scale automation. Attackers deployed a network of fake GitHub accounts with random eight-character names, often impersonating automated services such as “build-bot,” “auto-ci,” and “pipeline-bot.”
SafeDep analysis identified two primary infection methods:
- SysDiag: Adding a new, seemingly benign workflow file that exfiltrates data in the background.
- Optimize-Build: Replacing existing system files with a dormant backdoor that can be activated remotely via the GitHub API.
Real-World Impact: The Tiledesk Incident
The downstream consequences of Megalodon extend beyond code repositories. Live chat and chatbot service Tiledesk was a notable victim, with hackers compromising nine of its GitHub code areas. This led to the unintentional publication of seven infected versions of their product to the public npm package registry, effectively spreading the infection from the source code level to the package ecosystem.
GitHub’s Security Posture
While GitHub has not publicly commented on the Megalodon attack specifically, the incident coincides with a separate disclosure regarding unauthorized access to approximately 3,800 internal GitHub-owned repositories via a compromised employee device. This dual revelation underscores a critical vulnerability in the software supply chain: even platforms designed for secure development are not immune to credential-based attacks.
For developers and maintainers, we recommend:
- Audit Workflow Files: Review all
.github/workflowsfiles for unauthorized changes or suspicious job steps. - Rotate Secrets: Immediately rotate any cloud credentials, API tokens, or SSH keys that may have been exposed to CI/CD pipelines.
- Pin Actions: Use SHA-hashed references for GitHub Actions instead of version tags to prevent tampering.
- Review Commit History: Look for commits from unknown accounts, especially those with bot-like names pushing workflow changes.
