T1195 Supply Chain Compromise — Detection & Response
Adversaries may manipulate products or product delivery mechanisms prior to receipt by a final consumer for the purpose of data or system compromise. Supply chain compromise can take place at any stage of the supply chain including manipulation of development tools, source code repositories, open source dependencies, update mechanisms, or other mechanisms used to ship compiled code.
Coverage at a glance
- Detections shipped
- 4
- Avg. verdict time
- < 5 min
- Data sources
- 4+
Threat context
How adversaries use T1195 Supply Chain Compromise — Detection & Response
Adversaries may manipulate products or product delivery mechanisms prior to receipt by a final consumer for the purpose of data or system compromise. Supply chain compromise can take place at any stage of the supply chain including manipulation of development tools, source code repositories, open source dependencies, update mechanisms, or other mechanisms used to ship compiled code.
The SolarWinds SUNBURST attack defined the modern supply chain threat model — a single compromised update delivered malware to 18,000+ organisations. npm and PyPI package hijacking (T1195.001) is increasingly common for developer workstation compromise. CI/CD pipeline poisoning injects malicious code into the build process, often by compromising secrets stored in GitHub Actions or Jenkins. Software bill of materials (SBOM) gaps make detecting compromised dependencies difficult without continuous SCA scanning.
Detections ManySignal ships
Ready-to-deploy detection rules
| Rule name | Severity | Data source |
|---|---|---|
| Dependency Confusion Attack Pattern — Package install from public repo matching private package name A build or install process downloads a package from the public registry that shadows an internal private package name. | High | Build System Logs / CrowdStrike |
| CI/CD Secrets Exfiltration — Build process accesses and exfiltrates secret A CI/CD workflow step accesses a secret and makes an outbound connection to a non-approved endpoint, suggesting secret exfiltration. | Critical | GitHub Audit Log / AWS CodeBuild |
| Critical CVE in Production Dependency — Known exploited vulnerability in deployed package A dependency with a known exploited vulnerability (CISA KEV) is present in a production service. | High | Snyk / GitHub Dependabot |
| Typosquat Package Installed — Package with name similar to popular library installed A package with a name differing by one character from a popular library is installed — classic typosquatting pattern. | High | Build System Logs |
Related techniques and tactics
T1078 Valid Accounts — Detection & Response
ATT&CK Technique
T1110 Brute Force — Detection & Response
ATT&CK Technique
T1566 Phishing — Detection & Response
ATT&CK Technique
T1059 Command and Scripting Interpreter — Detection & Response
ATT&CK Technique
T1053 Scheduled Task/Job — Detection & Response
ATT&CK Technique
T1548 Abuse Elevation Control Mechanism — Detection & Response
ATT&CK Technique
T1068 Exploitation for Privilege Escalation — Detection & Response
ATT&CK Technique
T1134 Access Token Manipulation — Detection & Response
ATT&CK Technique
T1098 Account Manipulation — Detection & Response
ATT&CK Technique
T1136 Create Account — Detection & Response
ATT&CK Technique
T1556 Modify Authentication Process — Detection & Response
ATT&CK Technique
T1621 Multi-Factor Authentication Request Generation — Detection & Response
ATT&CK Technique
T1195 Supply Chain Compromise — Detection & Response: frequently asked questions
Can ManySignal detect supply chain attacks in real time?
ManySignal detects behavioural indicators of supply chain compromise: unusual outbound connections from build agents, secrets accessed during anomalous build steps, and dependency downloads from unexpected registries. Pre-compromise supply chain risks (vulnerable dependencies) require SCA tool integration (Snyk, Dependabot), whose alerts ManySignal ingests and correlates with runtime signals.
See the agentic SOC in action
Watch AI agents work a real alert queue — verdicts, evidence, and confidence scores included. In-house SOC or MDR, your call.