Skip to content

pale-knight/redteam-skill / skills/cicd

CI/CD pipeline and software-supply-chain exploitation: Jenkins, GitHub Actions, GitLab CI/CD, Azure DevOps, Gitea/Forgejo, self-hosted runners/agents, poisoned pipeline execution, artifact/cache abuse, dependency confusion, third-party Action trust, GitOps/registry poisoning, workload identity/OIDC, and emerging agentic CI/CD. Use this skill when the operator has access to a CI/CD system, source repository, build/deploy configuration, runner/agent, artifact/package/registry path, or software delivery trust chain.

references/cicd-attacks.md

View on GitHub
# CI/CD 攻击面总览

---

## 1. 攻击面矩阵

| 面 | 典型问题 | 结果 |
|---|---|---|
| Source | repo write / branch protection / reusable template | PPE / workflow control |
| Trigger | PR/issue/comment/workflow_run/downstream trigger | low-trust → privileged context |
| Workflow | expression injection / dangerous checkout | runner command execution |
| Token | GITHUB_TOKEN / CI_JOB_TOKEN / System.AccessToken | repo/project/package control |
| Runner | self-hosted persistent state | cross-job credential/deploy identity |
| Artifact | leakage / poisoning | secret exposure / privileged second-stage execution |
| Cache | low→high trust cache | cross-workflow execution |
| Action/Component | mutable refs / repo-jacking / vulnerable action | third-party supply-chain compromise |
| Dependency | confusion / package trust | build-time code execution |
| Registry | image/package write + consumer trust | downstream deployment compromise |
| Workload Identity | OIDC/federation | cloud identity acquisition |
| Agentic | prompt/tool/output trust | agent-driven repo/shell/deploy impact |

---

## 2. OWASP CI/CD风险映射(保留旧结构)

- Flow Control不足 → PPE / branch / approval / trigger trust
- IAM不足 → token/service connection/runner scope
- Dependency Chain Abuse → dependency confusion / third-party components
- PPE → workflow/Jenkinsfile/pipeline template modification
- PBAC不足 → secrets/identity传播
- Credential Hygiene → artifacts/logs/workspace/token persistence
- System Configuration → anonymous/admin/script console/runner isolation
- Third-party Services → Actions/Apps/Components/registries
- Artifact Integrity → artifact/cache/release/provenance
- Logging/Monitoring → runtime observation / audit gaps

---

## 3. 2026升级重点

Black-cat直接带来的增量:

```text
Poutine
Octoscan
artifact leakage
repo-jacking
Harden-Runner runtime observation
多生态 dependency confusion
```

在此基础上新增:

```text
Trajan(Gato/Glato继任)
zizmor
workflow_run / issue_comment / cache poisoning现代模式
reusable workflow + secrets: inherit
immutable release / artifact attestation trust
CI OIDC → AWS/Azure/GCP/Alibaba identity
GitLab新Runner authentication token模型
Azure DevOps templates/service connections/agent pools
Agentic CI/CD / GitHub Agentic Workflows
```
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall