Windows Phantom DLL Created on Disk
Description
The following analytic detects creation of DLL files with names associated with phantom DLL hijacking opportunities. These DLLs are usually absent from standard Windows installations, but legitimate Windows components or services may attempt to load them when they are present in expected search paths such as System32. Phantom DLL hijacking involves placing a malicious DLL where a legitimate process will search for a non-existent dependency, allowing the attacker-controlled library to execute in that process context. ShieldBreak is one example where the exploit redirects a privileged Defender-driven write into C:\Windows\System32\phoneinfo.dll and then triggers Windows Error Reporting so wermgr.exe loads the planted DLL at SYSTEM integrity. If confirmed malicious, this activity can indicate preparation for code execution, persistence, or local privilege escalation through DLL search order hijacking.
Query · spl
| tstats `security_content_summariesonly`
count min(_time) as firstTime
max(_time) as lastTime
from datamodel=Endpoint.Filesystem where
Filesystem.action IN ("created","modified")
Filesystem.file_path IN (
"*:\\Windows\\System32\\axeonoffhelper.dll",
"*:\\Windows\\System32\\cdpsgshims.dll",
"*:\\Windows\\System32\\oci.dll",
"*:\\Windows\\System32\\offdmpsvc.dll",
"*:\\Windows\\System32\\shellchromeapi.dll",
"*:\\Windows\\System32\\TSMSISrv.dll",
"*:\\Windows\\System32\\TSVIPSrv.dll",
"*:\\Windows\\System32\\wbem\\wbemcomn.dll",
"*:\\Windows\\System32\\WLBSCTRL.dll",
"*:\\Windows\\System32\\wow64log.dll",
"*:\\Windows\\System32\\WptsExtensions.dll",
"*\\phoneinfo.dll",
"*\\SprintCSP.dll"
)
by Filesystem.action Filesystem.dest Filesystem.file_hash
Filesystem.file_name Filesystem.file_path Filesystem.process_id
Filesystem.user Filesystem.vendor_product
| `drop_dm_object_name(Filesystem)`
| `security_content_ctime(firstTime)`
| `security_content_ctime(lastTime)`
| `windows_phantom_dll_created_on_disk_filter`
Implementation guide
To successfully implement this search, you need file creation telemetry from Windows endpoints mapped into the Endpoint.Filesystem datamodel. If you are using Sysmon, enable EventID 11 and ensure the FileCreate configuration captures the full target filename for DLL creations in Windows system paths.
Known false positives
- Some legacy or third-party components may create DLLs with these names for legitimate compatibility reasons, but creation in Windows system paths should be uncommon. Review the creating process, signer, file hash, path, and whether the DLL is expected on the host before tuning.
Analyst notes
Known false positives: Some legacy or third-party components may create DLLs with these names for legitimate compatibility reasons, but creation in Windows system paths should be uncommon. Review the creating process, signer, file hash, path, and whether the DLL is expected on the host before tuning.