Supply Chain Attack Analyst

Analyze software supply chain attacks and generate SIEM detection rules.

471|74|Updated Jan 13, 2026
One-click install
npx skills add https://github.com/MHaggis/Security-Detections-MCP --skill supply-chain-attack-analyst
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Supply Chain Attack Analyst
Source: https://github.com/MHaggis/Security-Detections-MCP/tree/main/.claude/skills/supply-chain-analyst
Command: npx skills add https://github.com/MHaggis/Security-Detections-MCP --skill supply-chain-attack-analyst

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps analyze and defend against sophisticated software supply chain attacks that target package registries, CI/CD pipelines, and container ecosystems.

Core Features & Use Cases

  • Attack Surface Analysis: Understand vectors like typosquatting, dependency confusion, and CI/CD poisoning.
  • Detection Engineering: Generate detection rules (Sigma, KQL, EQL) for various SIEM platforms.
  • Incident Response Guidance: Provides a structured checklist for investigating supply chain compromises.
  • Use Case: A security analyst can use this skill to understand the TTPs of a recent supply chain attack and generate detection rules for their SIEM to find similar malicious activity.

Quick Start

Analyze the provided GitHub Actions workflow for potential supply chain vulnerabilities.

Frequently Asked Questions about Supply Chain Attack Analyst

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

FAQPage Schema
How do I generate detection rules for a software supply chain attack?

To detect CI/CD poisoning and account takeover, you analyze software supply chain vulnerabilities across pipelines and package registries. The skill provides structured incident response checklists and generates Sigma, KQL, and EQL rules to find malicious activity in your SIEM.

What is dependency confusion and how does it target package registries?

Dependency confusion is a software supply chain attack vector targeting package registries by tricking build systems into pulling malicious public packages instead of internal ones. The skill analyzes this mechanism alongside typosquatting and CI/CD poisoning to map malicious TTPs.

Can I analyze GitHub Actions workflows for supply chain vulnerabilities?

Yes, you can analyze GitHub Actions workflows for supply chain vulnerabilities. The skill examines CI/CD pipelines and container ecosystems to identify potential poisoning and account takeover risks, translating those findings into actionable detection engineering patterns.

How do I investigate a package registry compromise during incident response?

You investigate a package registry compromise by applying a structured incident response checklist tailored to software supply chain attacks. The skill guides analysts through mapping attack vectors and generating detection rules to identify similar malicious activity across the environment.

Does this support generating KQL and EQL rules for container security incidents?

Yes, this supports generating KQL and EQL rules for container security incidents. The skill analyzes container ecosystems and CI/CD pipelines, outputting detection engineering patterns formatted for various SIEM platforms to catch supply chain compromises.