Runs a hypothesis-driven threat hunt for supply-chain compromise (T1195) by querying SIEM/EDR logs for trojanized software updates, compromised dependencies, unauthorized code modifications, and tampered build artifacts. Use when hunting after threat intel flags a compromised vendor/dependency, scoping a build-pipeline compromise, or reviewing update/build integrity.
Start a fresh conversation. Replace the highlighted placeholders.
Use hunting-for-supply-chain-compromise to Conduct an authorized supply-chain-compromise threat hunt for [suspected vendor, dependency, or build incident] using the available SIEM and EDR telemetry, and deliver the documented hunt report with validated findings, confidence, risk, and recommended actions.
Required inputs
[suspected vendor, dependency, or build incident]
User-approved starter prompt based on a pinned source version; check current skill requirements before running. Task evidence ↗
SKILL.md
name: hunting-for-supply-chain-compromisedescription: Runs a hypothesis-driven threat hunt for supply-chain compromise (T1195) by querying SIEM/EDR logs for trojanized software updates, compromised dependencies, unauthorized code modifications, and tampered build artifacts. Use when hunting after threat intel flags a compromised vendor/dependency, scoping a build-pipeline compromise, or reviewing update/build integrity.domain: cybersecuritysubdomain: threat-huntingtags: - threat-hunting- mitre-attack- supply-chain- initial-access- t1195- proactive-detectionversion: '1.0'author: mahipallicense: Apache-2.0d3fend_techniques: - Platform Hardening- Restore Object- Restore Software- Software Update- Asset Inventorynist_csf: - DE.CM-01- DE.AE-02- DE.AE-07- ID.RA-05mitre_attack: - T1046- T1057- T1082- T1083- T1195
Hunting For Supply Chain Compromise
When to Use
When proactively hunting for indicators of hunting for supply chain compromise in the environment
After threat intelligence indicates active campaigns using these techniques
During incident response to scope compromise related to these techniques
When EDR or SIEM alerts trigger on related indicators
During periodic security assessments and purple team exercises
Prerequisites
EDR platform with process and network telemetry (CrowdStrike, MDE, SentinelOne)
SIEM with relevant log data ingested (Splunk, Elastic, Sentinel)
Sysmon deployed with comprehensive configuration
Windows Security Event Log forwarding enabled
Threat intelligence feeds for IOC correlation
Workflow
Formulate Hypothesis: Define a testable hypothesis based on threat intelligence or ATT&CK gap analysis.
Identify Data Sources: Determine which logs and telemetry are needed to validate or refute the hypothesis.
Execute Queries: Run detection queries against SIEM and EDR platforms to collect relevant events.
Analyze Results: Examine query results for anomalies, correlating across multiple data sources.
Validate Findings: Distinguish true positives from false positives through contextual analysis.
Correlate Activity: Link findings to broader attack chains and threat actor TTPs.
Document and Report: Record findings, update detection rules, and recommend response actions.