Executive Summary
Supply Chain Compromise (T1195) is a MITRE ATT&CK technique associated with Initial Access. Adversaries may manipulate products or product delivery mechanisms prior to receipt by a final consumer for the purpose of data or system compromise.
Why Attackers Use It
Attackers use Supply Chain Compromise because it provides a reliable way to advance their objective within the Initial Access tactic, often with a favorable balance of impact versus detectability on Linux, Windows, macOS, SaaS environments. Defenders should assess this behavior in the context of the affected platform and adjacent activity rather than treating it as a standalone indicator.
MITRE Description
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
- Manipulation of a development environment
- Manipulation of source code repositories (public or private)
- Manipulation of source code in open-source dependencies
- Manipulation of software update/distribution mechanisms
- Compromised/infected system images (removable media infected at the factory)(Citation: IBM Storwize)(Citation: Schneider Electric USB Malware)
- Replacement of legitimate software with modified versions
- Sales of modified/counterfeit products to legitimate distributors
- Shipment interdiction
While supply chain compromise can impact any component of hardware or software, adversaries looking to gain execution have often focused on malicious additions to legitimate software in software distribution or update channels.(Citation: Avast CCleaner3 2018)(Citation: Microsoft Dofoil 2018)(Citation: Command Five SK 2011) Adversaries may limit targeting to a desired victim set or distribute malicious software to a broad set of consumers but only follow up with specific victims.(Citation: Symantec Elderwood Sept 2012)(Citation: Avast CCleaner3 2018)(Citation: Command Five SK 2011) Popular open-source projects that are used as dependencies in many applications may also be targeted as a means to add malicious code to users of the dependency.(Citation: Trendmicro NPM Compromise)
In some cases, adversaries may conduct “second-order†supply chain compromises by leveraging the access gained from an initial supply chain compromise to further compromise a software component.(Citation: Krebs 3cx overview 2023) This may allow the threat actor to spread to even more victims.
Attack Flow
- Attacker gains the prerequisite access or context described below.
- Attacker executes Supply Chain Compromise to achieve its tactical objective (Initial Access).
- Resulting access/data/effect is leveraged to advance the broader attack chain (see Related Techniques).
Prerequisites
- Platform(s): Linux, Windows, macOS, SaaS
- ATT&CK does not define one universal permission requirement for this technique. Establish the required access from the observed implementation and affected platform.
Common Tools
- Tool attribution is implementation-specific. Use ATT&CK procedure examples and local telemetry to identify the binaries, services, scripts, accounts, or cloud resources involved.
Commands
No universal command represents Supply Chain Compromise. Capture the exact command line, arguments, parent process, account, host, and execution time from the investigated environment; do not operationalize unverified examples.
Network Traffic
- Network observability is implementation-dependent. Review DNS, proxy, firewall, flow, authentication, and packet telemetry around the activity window, then correlate remote endpoints and protocol behavior with host evidence.
Windows Events
| Event ID | Log Channel | What It Indicates |
|---|
| Environment-specific | Relevant Windows channel(s) | Correlate authentication, process, object-access, and configuration events with the observed execution context. |
Sysmon Events
| Sysmon Event ID | Name | Why It's Relevant Here |
|---|
| Environment-specific | Validate configured telemetry | Use process, network, file, registry, DNS, or image-load telemetry only when relevant and enabled. |
Detection Opportunities
No MITRE detection guidance published for this technique.
Relevant ATT&CK Data Sources: N/A
Sigma Rules
A universal Sigma rule would create unreliable results because this technique has no single guaranteed observable. Build detection logic from a documented behavior and supported data source, scope it to the affected platform, and validate it against benign administrative activity before deployment.
Splunk Queries
Start with the data sources named in the detection section. Scope searches by asset, identity, and time window; correlate the primary behavior with preceding access and subsequent actions. A portable query is intentionally not provided where the technique lacks a universal schema or observable.
Investigation Workflow
- Confirm that the observed behavior is consistent with Supply Chain Compromise and rule out expected administrative or application activity.
- Establish the first-seen time, initiating identity, source system, target system, and affected resources.
- Collect relevant host, identity, network, cloud, and application telemetry for the surrounding time window.
- Correlate parent and child activity, remote connections, file or configuration changes, and related ATT&CK techniques.
- Determine scope by searching for the same observable across peer assets and identities.
- Preserve volatile evidence and record confidence, assumptions, and telemetry gaps before containment.
Containment
- Isolate affected host(s)/account(s) identified during investigation.
- Revoke or rotate any credentials/tokens potentially exposed.
- Apply the mitigations listed below where not already enforced.
- Validate no related techniques (see Related Techniques) were chained against the same asset.
Mitigation
- M1046 -- Boot Integrity: Boot Integrity ensures that a system starts securely by verifying the integrity of its boot process, operating system, and associated components.
- M1013 -- Application Developer Guidance: Application Developer Guidance focuses on providing developers with the knowledge, tools, and best practices needed to write secure code, reduce vulnerabilities, and implement secure design principles.
- M1051 -- Update Software: Software updates ensure systems are protected against known vulnerabilities by applying patches and upgrades provided by vendors.
- M1018 -- User Account Management: User Account Management involves implementing and enforcing policies for the lifecycle of user accounts, including creation, modification, and deactivation.
- M1016 -- Vulnerability Scanning: Vulnerability scanning involves the automated or manual assessment of systems, applications, and networks to identify misconfigurations, unpatched software, or other security weaknesses.
- M1033 -- Limit Software Installation: Prevent users or groups from installing unauthorized or unapproved software to reduce the risk of introducing malicious or vulnerable applications.
Related Techniques
- T1027.013
- T1041
- T1071.001
- T1082
- T1113
- T1119
- T1140
- T1195.001
- T1195.002
- T1195.003
- T1539