ATT&CK coverage › Technique

System Binary Proxy Execution: Regsvcs/Regasm T1218.009

Adversaries may abuse Regsvcs and Regasm to proxy execution of code through a trusted Windows utility. Regsvcs and Regasm are Windows command-line utilities that are used to register .NET Component Object Model (COM) assemblies. Both are binaries that may be digitally signed by Microsoft.

Events covered

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

ProviderEvent IDTitle
Sysmon1Process creation
Sysmon3Network connection

Authoring guide

Patterns shared across the 6 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 (7 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
Image4ends_with 4\Regasm.exe, \Regsvcs.exe, \RegAsm.exe, \regasm.exe
OriginalFileName3eq 3RegAsm.exe, RegSvcs.exe
CommandLine3match 2, ends_with 1\PerfLogs\, \AppData\Local\Temp\, \Microsoft\Windows\Start Menu\Programs\Startup\, .dat, .jpeg
process_name2eq 2regasm.exe, regsvcs.exe
EventID2eq 23
Initiated1eq 1true
dest_ip1cidr_match 110.0.0.0/8, ::1/128, fe80::/10

Top indicator values (33 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
OriginalFileNameeqRegAsm.exe36
Imageends_with\Regsvcs.exe22
OriginalFileNameeqRegSvcs.exe25
Imageends_with\Regasm.exe22
EventIDeq324
CommandLinematch\AppData\Local\Temp\116
CommandLinematch\Microsoft\Windows\Start Menu\Programs\Startup\13
CommandLinematch\PerfLogs\12
CommandLinematch\Users\Public\117
CommandLinematch\Windows\Temp\110
CommandLinematch.jpg17
CommandLinematch.txt17
CommandLinematch.dat12
CommandLinematch.gif16
CommandLinematch.jpeg16
CommandLinematch.png17
CommandLineends_withRegAsm1
Imageends_with\RegAsm.exe13
CommandLineends_withRegAsm.exe1
CommandLineends_withRegAsm.exe"1

Common exclusions (23 distinct)

Field/operator/value combinations that rules under this technique routinely exclude (top-level not() clauses). These are the false-positive paths the community has learned to filter out. A new rule that ignores the high-count entries here will likely fire on the same noisy paths.

FieldKindValueRules excluding
dest_ipin"192.175.48.0/24"2
dest_ipin"192.88.99.0/24"2
dest_ipin"224.0.0.0/4"2
dest_ipin"192.168.0.0/16"2
dest_ipin"192.0.0.10/32"2
dest_ipin"198.51.100.0/24"2
dest_ipin"192.0.0.170/32"2
dest_ipin"192.0.0.0/29"2
dest_ipin"192.52.193.0/24"2
dest_ipin"127.0.0.0/8"2
dest_ipin"100.64.0.0/10"2
dest_ipin"192.0.0.0/24"2
dest_ipin"240.0.0.0/4"2
dest_ipin"10.0.0.0/8"2
dest_ipin"203.0.113.0/24"2

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 4 rules

Splunk 2 rules