supply-chain-attack-recon

Identifies and maps external supply-chain attack surfaces from public GitHub, registries, and SBOMs.

3.3k|507|Updated May 5, 2026

Search Tags:#security #github #supply-chain #dependency-confusion #osint #recon #typosquat

Ready to run

npx skills add https://github.com/elementalsouls/Claude-BugHunter --skill supply-chain-attack-recon-elementalsouls

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: supply-chain-attack-recon
Source: https://github.com/elementalsouls/Claude-BugHunter/tree/main/skills/supply-chain-attack-recon
Command: npx skills add https://github.com/elementalsouls/Claude-BugHunter --skill supply-chain-attack-recon-elementalsouls

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Detects and maps external supply-chain attack surfaces for software organizations, helping security teams identify risks like dependency-confusion, typosquats, and vulnerable workflows before exploitation.

Core Features & Use Cases

OSINT-driven discovery of target orgs, public repositories, workflows, and artifacts
Assessment of internal-looking package names, registry exposures, and SBOM leakage
Detection of insecure CI/CD configurations and vulnerable workflow patterns that enable supply-chain abuse
Use Case: During external assessments, surface potential dependency-confusion targets and typosquat candidates to prioritize defensive hardening and monitoring

Quick Start

Run the external-recon workflow against a target with public GitHub orgs and registries to surface dependency-confusion, typosquats, and SBOM leakage.

Frequently Asked Questions about supply-chain-attack-recon

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I detect dependency-confusion risks in public GitHub organizations?▼

To detect dependency-confusion risks, this Skill collects OSINT from public GitHub organizations and registries to identify internal-looking package names and assess registry exposures. It analyzes SBOM data and CI/CD configurations to surface actionable findings with severity and remediation guidance.

What is supply-chain attack surface mapping for software ecosystems?▼

Supply-chain attack surface mapping identifies and exposes external risks like dependency-confusion, typosquats, and vulnerable workflows in software ecosystems. It collects OSINT from GitHub, public registries, and SBOM data to analyze exposure patterns before exploitation occurs.

Can I use OSINT to find typosquat candidates in public registries?▼

Yes, you can use OSINT to find typosquat candidates by running the external-recon workflow against targets with public registries. The Skill analyzes public package names and registry exposures to surface potential typosquat targets for defensive hardening.

How do I check CI/CD workflows for vulnerable injection patterns?▼

To check CI/CD workflows for vulnerable injection patterns, the Skill analyzes public GitHub workflow configurations and artifacts. It detects insecure CI/CD configurations and vulnerable workflow patterns that enable supply-chain abuse, then outputs actionable findings with remediation guidance.

What's the best way to assess SBOM leakage in external security assessments?▼

The best way to assess SBOM leakage is using OSINT-driven discovery to collect and analyze SBOM data from public repositories. This Skill surfaces dependency-confusion targets and SBOM leakage during external assessments to prioritize defensive monitoring.

Do I need public GitHub repositories to map external supply-chain risks?▼

Yes, you need targets with public GitHub organizations, public registries, or SBOMs to map external supply-chain risks. The Skill relies on collecting OSINT from these public sources to identify dependency-confusion, typosquat, and workflow-injection exposures.