DLL Search-Order Hijacking
Also called DLL Hijacking, DLL Preloading.
Planting a malicious library where a trusted program will load it.
What it is
Exploiting the order in which an application searches directories for a dynamic library by placing a malicious DLL in a location checked before the legitimate one. The trusted program then loads attacker code at startup.
Why it matters
Hijacking gives execution and persistence under the cover of a legitimate, often signed, application, which helps evade detection and allow-listing. Examining a process's loaded modules and their paths is the practical way to catch it.
In practice
A signed application is found loading a same-named DLL dropped into its own folder, silently running attacker code each time it launches.
What to look for
- A DLL with a system name loaded from the application folder instead of System32.
- Unsigned DLLs sitting next to a signed executable in a writable folder.
- A legitimate program copied into a temp or user folder with a DLL beside it.
Common mistake
Checking only that the executable is signed. The trusted program is the host; the planted DLL is the payload.
Practice it nearby
CyberKit has no tool for this term itself. These are the closest places to practice it.
- Map and Score
Map real procedures to ATT&CK techniques, then pick the CVSS v3.1 metrics for real vulnerabilities.
- Hunt Query Builder
Build a hunting query in KQL, SPL, LogScale or PowerQuery against documented field names, or start from a prebuilt hunt.
In the field
Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.
-
Atomic Red Team Open source
Small, scripted tests mapped to ATT&CK techniques, used to check whether a detection fires.
-
ATT&CK Navigator Open source
Lays techniques out on the ATT&CK matrix so teams can mark coverage, gaps and threat profiles.
-
Microsoft Defender for Endpoint Commercial
Tags its alerts with the ATT&CK techniques it observed on the host.
-
Sysmon Free
Supplies the host telemetry that most technique detections are written against. Our notes.
Read next
- Signed Binary Proxy Execution: Hiding code execution behind a trusted, signed system binary.
- COM Hijacking: Redirecting a registered COM object to attacker code via the registry.
- Masquerading: Disguising malicious files or processes as legitimate ones.