Source:
tldr: A supply chain attack dubbed “Megalodon” is targeting GitHub repositories by injecting malicious commits into CI/CD workflows. Around 5,561 repositories were hit in a 6-hour window using fake bot accounts to push poisoned GitHub Actions pipelines that auto-run on pull requests.
What is happening
- Fake bot accounts (
build-bot,ci-bot,pipeline-bot) are committing malicious workflow files directly into repositories. - The attack targets GitHub Actions and CI pipelines configured to auto-run on PRs.
- Around 5,561 repositories were affected within a single 6-hour window.
- The malicious workflows execute attacker-controlled code in the context of the target repository’s CI environment — potentially leaking secrets, tokens, and build artifacts.
What to do
- Audit your repository’s recent commits — especially anything touching
.github/workflows/from unfamiliar bot accounts. - Review collaborator and outside contributor access for any unexpected accounts.
- Require approval for workflow runs from first-time contributors (
pull_request_targetis particularly dangerous). - Rotate any secrets or tokens that may have been exposed through CI runs triggered by the malicious commits.
- Review the SafeDep writeup for IOCs and detection guidance.