supply-chain-attack-recon

To detect dependency confusion, you analyze public repositories and package registries to identify unclaimed internal package names that could be hijacked by attackers. This reconnaissance validates findings against known vulnerability patterns.

Auditing GitHub Actions workflows involves scanning CI/CD configurations for dangerous patterns like pull_request_target injection or secret exposure. This process requires tools like actionlint and semgrep to validate insecure build artifacts.

Scanning Docker images and SBOMs for leaked secrets requires mining build artifacts using tools like trufflehog and gitleaks. This analysis identifies exposed credentials and known-vulnerability chaining within container registries.

Yes, you need Docker and GitHub CLI installed to perform supply-chain reconnaissance. The analysis also requires jq, trufflehog, gitleaks, actionlint, and semgrep to validate findings against known vulnerability patterns.

Typosquatting detection works by analyzing public-facing software ecosystems and package registries to identify potential injection or confusion vectors. It targets external assets to find packages masquerading as legitimate dependencies.

Yes, you can use semgrep and actionlint together to find insecure GitHub Actions configurations. They scan workflows for dangerous patterns like pull_request_target injection and validate findings against known vulnerability patterns.