Cicd Supply Chain logo

Cicd Supply Chain

Community
hypnguyen1209
cicd-supply-chain

Use when attacking or auditing a CI/CD pipeline or software supply chain — pwn requests, poisoned pipeline execution, compromised/mutable-tag actions, dependency confusion, registry worms, runner backdoors, OIDC trust abuse, SLSA/provenance

Overview

Publisherhypnguyen1209
Repositoryoffensive-claude
Skill namecicd-supply-chain
Stars
396
Forks
71
Bundled files
12
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 12 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by hypnguyen1209 on GitHub. Read the source before you install it.

Installation

Install the Cicd Supply Chain AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/hypnguyen1209/offensive-claude/tree/main/skills/cicd-supply-chain
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/hypnguyen1209/offensive-claude.git /tmp/offensive-claude
mkdir -p .claude/skills
cp -r /tmp/offensive-claude/skills/cicd-supply-chain .claude/skills/cicd-supply-chain
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Cicd Supply Chain in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Cicd Supply Chain on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Cicd Supply Chain is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

CI/CD Pipeline Poisoning & Supply-Chain Attacks

When to Activate

  • Auditing or attacking GitHub Actions / GitLab CI / Jenkins pipelines for code execution
  • Hunting pull_request_target / workflow_run "pwn requests" and Poisoned Pipeline Execution (PPE)
  • Assessing compromised third-party Actions, mutable version tags, and Actions cache poisoning
  • Dependency confusion, typo/slopsquatting, and malicious package/install-hook payloads
  • Self-hosted / non-ephemeral runner abuse and runner backdoors
  • CI secret exfiltration and OIDC cloud-role (AWS/GCP/Azure) trust-policy abuse
  • Validating SLSA build provenance and signing gates (defense / blue-team validation)

Technique Map

TechniqueATT&CKCWEReferenceScript
Pwn request (pull_request_target checkout of fork head)T1195.001CWE-269references/pipeline-poisoning.mdscripts/workflow_auditor.py
Script injection (${{ github.event.* }} into run:)T1059CWE-94references/pipeline-poisoning.mdscripts/workflow_auditor.py
Direct / Indirect PPE (workflow or build-file modification)T1195.001CWE-913references/pipeline-poisoning.mdscripts/workflow_auditor.py
GitLab .gitlab-ci.yml poisoning / pipeline-as-user (CVE-2024-6678)T1648CWE-863references/pipeline-poisoning.mdscripts/workflow_auditor.py
Compromised Action via mutable tag (CVE-2025-30066 tj-actions)T1195.001CWE-494references/action-dependency-compromise.mdscripts/malicious_action_scanner.py
Transitive Action compromise (CVE-2025-30154 reviewdog)T1195.001CWE-1357references/action-dependency-compromise.mdscripts/malicious_action_scanner.py
Actions cache poisoning (cross-workflow escalation)T1525CWE-349references/action-dependency-compromise.mdscripts/malicious_action_scanner.py
Dependency confusion (internal name on public registry)T1195.002CWE-427references/package-registry-attacks.mdscripts/dependency_confusion.py
Typo / slopsquatting + malicious install hookT1195.002CWE-829references/package-registry-attacks.mdscripts/dependency_confusion.py
Self-replicating registry worm (Shai-Hulud npm)T1195.002CWE-829references/package-registry-attacks.mdscripts/malicious_action_scanner.py
Self-hosted / non-ephemeral runner abuse & backdoorT1199CWE-668references/runner-attacks.mdscripts/runner_recon.sh
Jenkins Script Console RCE (/script, CVE-2024-23897)T1648CWE-306references/runner-attacks.mdscripts/runner_recon.sh
CI secret exfiltration (toJSON(secrets), GhostAction)T1552.004CWE-522references/secrets-oidc-abuse.mdscripts/oidc_trust_auditor.py
OIDC trust-policy abuse (missing/* sub, wrong org wildcard)T1078.004CWE-1390references/secrets-oidc-abuse.mdscripts/oidc_trust_auditor.py
Build provenance / signing gate validation (defense)T1195CWE-347references/build-integrity-defense.mdscripts/provenance_verify.sh

Quick Start

bash
# 0. Recon: enumerate workflows, triggers, used actions across an org (read-only token)
gh repo list ORG --limit 1000 --json nameWithOwner -q '.[].nameWithOwner' > repos.txt
python3 scripts/workflow_auditor.py --repos repos.txt --token "$GH_TOKEN" --out findings.json

# 1. Static audit any cloned repo for pwn-requests + injection sinks (offline, no token)
git clone https://github.com/ORG/REPO && python3 scripts/workflow_auditor.py --path REPO

# 2. Flag risky/mutable third-party Action refs (unpinned tags = supply-chain exposure)
python3 scripts/malicious_action_scanner.py --path REPO --check-pins --check-known-bad

# 3. Dependency confusion: find internal names not registered on public registries
python3 scripts/dependency_confusion.py --manifest REPO/package.json --registry npm
python3 scripts/dependency_confusion.py --manifest REPO/requirements.txt --registry pypi

# 4. OIDC abuse: audit AWS IAM trust policies tied to GitHub's OIDC provider
python3 scripts/oidc_trust_auditor.py --provider github --cloud aws --profile target

# 5. Runner recon (run ON a compromised self-hosted runner during an engagement)
bash scripts/runner_recon.sh

# 6. Defensive validation: verify SLSA provenance + cosign signature before promote
bash scripts/provenance_verify.sh --image ghcr.io/org/app:tag --repo org/app

Recommended OSS tooling: gato-x (offensive GHA enumeration/PPE), zizmor/octoscan/poutine/raven (static workflow analysis), step-security/harden-runner (egress control), cosign+slsa-verifier (gates).

OPSEC & Detection (summary)

TechniqueTelemetry / IOCDetection (Sigma/EDR)OPSEC note
Pwn request / PPEFork PR triggering privileged run; new .github/workflows/* in PR; outbound to non-allowlisted hostGH audit log workflows; Sigma on runner egress to new domains; zizmor in CIPayload runs in build log; public-repo logs are world-readable — assume detection
Compromised Action / mutable tagAction ref resolves to new SHA; tag force-push event; base64 in action sourceDiff resolved SHA vs lockfile; alert on tag re-point in audit logTag re-point is logged org-side; SHA-pin victims are immune
Cache poisoningCache key written by read-only/low-priv job, restored by release jobMonitor actions/cache save/restore key ownership; provenance mismatchSurvives across workflows; harder to attribute than direct edit
Dependency confusionInstall-time outbound from build host; package version anomaly (very high ver)EDR proc-tree npm/pip -> curl/node -e; registry telemetryHigher public version wins resolver; noisy if scoped registries enforced
Registry worm (Shai-Hulud)bundle.js postinstall; trufflehog filesystem /; public Shai-Hulud repo; shai-hulud-workflow.ymlEDR: npm child spawns trufflehog/git push; Sigma on workflow file creationSelf-propagating = loud and fast; burns the maintainer token
Runner backdoorRogue runner registration; persistent proc on host; outbound only to github.comRunner-host EDR; GH audit self_hosted_runner events; one-job-per-runnerTraffic blends with github.com; non-ephemeral = persistence
Secret exfil / toJSON(secrets)${{ toJSON(secrets) }} in run step; POST of base64 to webhookStatic scan for toJSON(secrets); egress allowlistGitHub masks *** in logs — encoding evades the mask
OIDC trust abuseAssumeRoleWithWebIdentity; CloudTrail userName = repo:org/repo:refCloudTrail filter on federated principals; IAM Access Analyzer external findingsShort-lived creds, attributed to repo in logs; AWS blocks new bad policies (Jun 2025)

Deep Dives

  • references/pipeline-poisoning.md — Pwn requests, PPE (direct/indirect), script injection, GitLab/Jenkins pipeline poisoning, with vulnerable+fixed YAML and a working exploit PR payload.
  • references/action-dependency-compromise.md — Third-party Action compromise, mutable git tags, the tj-actions (CVE-2025-30066) / reviewdog (CVE-2025-30154) chain, and Actions cache poisoning; SHA-pinning detection.
  • references/package-registry-attacks.md — Dependency confusion, typo/slopsquatting, malicious install hooks, and the Shai-Hulud self-replicating npm worm with concrete IOCs.
  • references/runner-attacks.md — Self-hosted / non-ephemeral runner abuse, JIT/ephemeral hardening, runner backdoors, and Jenkins Script Console RCE.
  • references/secrets-oidc-abuse.md — CI secret enumeration/exfiltration (GhostAction), toJSON(secrets), and AWS/GCP/Azure OIDC trust-policy misconfigurations.
  • references/build-integrity-defense.md — SLSA provenance, in-toto attestations, Sigstore/cosign keyless signing, slsa-verifier gates, and admission-control enforcement (the defensive counterweight).

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Cicd Supply Chain AI skill do?

Use when attacking or auditing a CI/CD pipeline or software supply chain — pwn requests, poisoned pipeline execution, compromised/mutable-tag actions, dependency confusion, registry worms, runner backdoors, OIDC trust abuse, SLSA/provenance

Why use Cicd Supply Chain on TypingMind?

Because you install it once and use it with any model. Cicd Supply Chain is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Cicd Supply Chain in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/hypnguyen1209/offensive-claude/tree/main/skills/cicd-supply-chain. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Cicd Supply Chain?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Cicd Supply Chain?

As many as you like. As long as a model supports skills, you can use Cicd Supply Chain with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Cicd Supply Chain AI skill free?

Yes. It is published on GitHub by hypnguyen1209 under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇