ATT&CK coverage › Technique

Process Injection: Dynamic-link Library Injection T1055.001

Adversaries may inject dynamic-link libraries (DLLs) into processes in order to evade process-based defenses as well as possibly elevate privileges. DLL injection is a method of executing arbitrary code in the address space of a separate live process.

Events covered

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

ProviderEvent IDTitle
Sysmon1Process creation
Sysmon7Image loaded
Sysmon8CreateRemoteThread
Security-Auditing4688A new process has been created.

Authoring guide

Patterns shared across the 8 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 (11 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
Image5ends_with 4, eq 1\dctask64.exe, \tracker.exe, \mavinject32.exe, \mavinject64.exe, "*\\wermgr.exe"
CommandLine3match 3 executecmd64 , injectDll , invokeexe , /INJECTRUNNING , /c
Hashes2match 2IMPHASH=6834B1B94E49701D77CCB3C0895E1AFD, IMPHASH=F1039CED4B91572AB7847D26032E6BBF, IMPHASH=FAA2AC19875FADE461C8D89DCF2710A3
ParentImage2eq 1, ends_with 1C:\Windows\System32\AppVClient.exe, \Msbuild\Current\Bin\MSBuild.exe, \Msbuild\Current\Bin\amd64\MSBuild.exe
OriginalFileName2eq 2mavinject32.exe, mavinject64.exe, "dynwrapx.dll"
EventID2eq 27, 8
StartAddress1ends_with 10C7C, 0B80, 0C88
Description1eq 1Tracker
ImageLoaded1eq 1"*\\dynwrapx.dll"
Product1eq 1"DynamicWrapperX"
TargetImage1in 1"*\\microsoftedgecp.exe", "*\\iexplore.exe", "*\\firefox.exe"

Top indicator values (34 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
Imageends_with\dctask64.exe22
HashesmatchIMPHASH=6834B1B94E49701D77CCB3C0895E1AFD22
HashesmatchIMPHASH=F1039CED4B91572AB7847D26032E6BBF22
HashesmatchIMPHASH=1BB6F93B129F398C7C4A76BB97450BBA22
HashesmatchIMPHASH=FAA2AC19875FADE461C8D89DCF2710A322
StartAddressends_with0B801
StartAddressends_with0C881
StartAddressends_with0C7C1
CommandLinematch injectDll 1
CommandLinematch executecmd64 1
CommandLinematch invokeexe 1
CommandLinematch /INJECTRUNNING 1
ParentImageeqC:\Windows\System32\AppVClient.exe1
ParentImageends_with\Msbuild\Current\Bin\MSBuild.exe1
DescriptioneqTracker1
CommandLinematch /ERRORREPORT:PROMPT 1
CommandLinematch /c 12
ParentImageends_with\Msbuild\Current\Bin\amd64\MSBuild.exe1
CommandLinematch /d 12
Imageends_with\tracker.exe1

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

Splunk 2 rules