Individual skill
detecting-supply-chain-attacks-in-ci-cd
Scans GitHub Actions workflows and CI/CD pipeline configurations for supply chain attack vectors including unpinned actions, script injection via expressions, dependency confusion, and secrets exposure. Uses PyGithub and YAML parsing for automated audit. Use when hardening CI/CD pipelines or investigating compromised build systems.
internal/tools/skills/data/security-operations/detecting-supply-chain-attacks-in-ci-cd/SKILL.md
Source commit d42f381ad34843e71a42658e5c57290c713e85af
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Instructions only
- Last checked
- Nov 9, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,323
- Repository last updated
- Nov 8, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- cybersecurity Repository topic
- security Repository topic
- bug-bounty Repository topic
- automation Repository topic
- autonomous-pentesting Repository topic
- ai-agent Repository topic
- ai-security Repository topic
- ethical-hacking Repository topic
- golang Repository topic
- penetration-testing Repository topic
- detecting Declared skill tag
- supply Declared skill tag
- chain Declared skill tag
- attacks Declared skill tag
- operations Derived category
- devops Derived category
- security Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
# Detecting Supply Chain Attacks in CI/CD
## When to Use
- When investigating security incidents that require detecting supply chain attacks in ci cd
- When building detection rules or threat hunting queries for this domain
- When SOC analysts need structured procedures for this analysis type
- When validating security monitoring coverage for related attack techniques
## Detection Gaps & Validation
- **SHA-pinning checks miss tag-pinning illusions:** flagging `@main`/`@v3` is right, but a `@v3` *tag* (or even a short SHA) is mutable/forgeable — only a full 40-char commit SHA is immutable. Also a pinned action can still pull unpinned transitive actions or `docker://image:latest` inside itself; recurse into reusable workflows (`uses: org/repo/.github/workflows/x.yml@ref`) and Dockerfile `FROM` lines.
- **Script-injection detection is broader than `github.event`:** untrusted input also flows through `github.head_ref`, `github.event.pull_request.title/body`, `github.event.issue.*`, and `env:` derived from them. Match the whole untrusted-context set in `run:` blocks, not just `github.event`.