ATT&CK coverage › Technique

Supply Chain Compromise T1195

Adversaries may manipulate products or product delivery mechanisms prior to receipt by a final consumer for the purpose of data or system compromise.

Events covered

9 catalog events are tagged with this technique by at least one rule.

ProviderEvent IDTitle
Sysmon3Network connection
Sysmon11FileCreate
Sysmon23FileDelete (File Delete archived)
Sysmon26FileDeleteDetected (File Delete logged)
Security-Auditing4663An attempt was made to access an object.
Security-Auditing5156The Windows Filtering Platform has permitted a connection.
Defender-DeviceFileEvents9002000File activity (any)
Defender-DeviceInfo9008000Device inventory snapshot
Defender-DeviceNetworkEvents9004001Connection succeeded

Authoring guide

Patterns shared across the 7 rules above: which fields they filter on, what specific values they look for, and what they exclude. Field names are normalized across vendors so Sigma's Image, Elastic's process.name, and Splunk's process_name collapse into one row. Each rule contributes at most once per row.

Fields filtered most (5 distinct)

The fields most rules look at when detecting this technique. The How column shows the operators authors use (eq, wildcard, regex_match, match) and how often each appears. Sample values are concrete examples to start from, not an exhaustive list.

FieldRulesHowSample values
TargetFilename3in 2, ends_with 1\AppData\Local\Microsoft\Cache134.dat, \AppData\Local\Microsoft\ExplorerSync.db, "*\\.github\\workflows\\*.yaml", "*/.github/workflows/*.yaml", "*/.github/workflows/*.yml"
MD51eq 1SunburstMD5, SupernovaMD5
TargetFileMD51eq 1SunburstMD5, SupernovaMD5
DestinationHostname1eq 1SunburstURL
ActionType1eq 1ConnectionSuccess

Top indicator values (28 distinct)

Specific (field, operator, value) combinations the rules check for, ranked by how many rules under this technique use each one. The Corpus reach column counts how many rules across the entire catalog (any technique) check the same combination. High numbers point to widely-used indicators that are likely noisy on their own; combine them with another condition for useful signal. Blank means the combination is specific to rules under this technique.

FieldKindValueRules (here)Corpus reach
MD5eqSupernovaMD51
MD5eqSunburstMD51
TargetFileMD5eqSunburstMD51
TargetFileMD5eqSupernovaMD51
ActionTypeeqConnectionSuccess1
DestinationHostnameeqSunburstURL1
TargetFilenameends_with\AppData\Local\Microsoft\ExplorerSync.db1
TargetFilenameends_with\AppData\Local\Microsoft\Cache134.dat1
TargetFilenamein"*\\.github\\workflows\\*.yaml"1
TargetFilenamein"*\\.github\\workflows\\*.yml"1
TargetFilenamein"*/.github/workflows/*.yaml"1
TargetFilenamein"*/.github/workflows/*.yml"1
TargetFilenamein"*\\.github\\workflows\\shai-hulud-workflow.yml"1
TargetFilenamein"*/.github/workflows/shai-hulud-workflow.yaml"1
TargetFilenamein"*\\.github\\workflows\\shai-hulud-workflow.yaml"1
TargetFilenamein"*\\.github\\workflows\\formatter_*.yaml"1
TargetFilenamein"*/.github/workflows/discussion.yml"1
TargetFilenamein"*/.github/workflows/formatter_*.yaml"1
TargetFilenamein"*/.github/workflows/shai-hulud.yaml"1
TargetFilenamein"*\\.github\\workflows\\discussion.yaml"1

Rules under this technique

Every rule in the catalog tagged with this technique, grouped by vendor. Click a rule title for its full predicates, exclusions, and indicators.

Sigma 1 rule

Splunk 2 rules

Kusto Query Language 4 rules