offensive-supply-chain skillF
offensive-supply-chain is agent-read markdown (skill) from snailsploit/claude-red: Comprehensive offensive methodology for software supply chain attacks covering the full kill chain from reconnaissance through exploitation. Addresses dependency confusion across npm, PyPI, and NuGet ecosystems where internal registry override allows an attacker to inject malicious packages that shadow private dependencies. Covers typosquatting techniques for popular packages, compromised package injection via maintainer account takeover or social engineering, and build system attacks through Ma.
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Offensive Supply Chain Attacks Software supply chain attacks exploit the trust relationships between developers, package registries, build systems, and deployment pipelines. You target the components and processes that organizations depend on but rarely audit with the same rigor as their own code. A single compromised dependency can propagate across thousands of downstream consumers, making supply chain the highest leverage attack surface in modern software ecosystems. This skill covers the offensive lifecycle: reconnaissance of internal package names, exploitation of registry resolution logic, build system hook abuse, CI/CD pipeline tampering, and container image supply chain attacks. Every technique maps to authorized red team engagement patterns with safe callback mechanisms. ## Quick Workflow 1. Enumerate internal package names from target artifacts (lock files, source maps, error messages, GitHub repos). 2. Identify the package ecosystem (npm, PyPI, NuGet, Maven, Go, Ruby) and registry configuration. 3. Select attack vector: dependency confusion, typosquatting, build hook injection, CI/CD tampering, or container supply chain. …
Read the whole file at its exact version.
How to install
mdr add snailsploit/claude-red/offensive-supply-chain@git:20260825.8cffe5dmdr add snailsploit/claude-red/offensive-supply-chain@sha256:5457988a8e2fd3d8Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_byhexnjnvdci3mq3)
1 badge views in 30 days
Versions
Audit of the latest version
- FAIL, critical: No link to an exfiltration or paste host (matched: https://your-canary.oastify.com)
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (18507 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
snailsploit/claude-red · 6,831 stars · license MIT · pushed 2026-09-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_byhexnjnvdci3mq3 GET https://markdownregistry.com/api/v1/resolve?ref=snailsploit/claude-red/offensive-supply-chain GET https://markdownregistry.com/api/v1/blob/5457988a8e2fd3d846e3ad62908957fb9f3eff877e393ad6cec8d9c7750a2a56
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
More from snailsploit/claude-red
Every file in snailsploit/claude-red