Potential DLL Sideloading via DeviceEnroller.exe Using /PhoneDeepLink

Alerts on deviceenroller.exe runs with /PhoneDeepLink, a potential DLL sideloading trigger referencing ShellChromeAPI.dll.

FreeReviewedSigma · Medium · v2
Product
windows
Category
process_creation
Author
@gott_cyber (SigmaHQ), DRL 1.1
Published
2022-08-29
Updated
2026-07-31

ATT&CK techniques

Execution → Defense Evasion
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Cred Access

  9. Discovery

  10. Lateral Movement

  11. Collection

  12. C2

  13. Exfiltration

  14. Impact

What it detects

This rule flags process creation events where DeviceEnroller.exe is launched with the /PhoneDeepLink parameter. The matching pattern indicates an execution flow that may attempt DLL sideloading of a non-existent file named ShellChromeAPI.dll. Attackers may use this mechanism to execute attacker-controlled code by arranging a renamed DLL for loading. The detection relies on Windows process creation telemetry, specifically the executable name and command-line contents.

Related detections9 linkedT1574.001 — drag to rearrange
Malicious DLL Sideloading via consent.exe Loading msimg32.dll (via image_load)
Malicious Bumblebee DLL Sideload of msimg32 by consent from Non-System Path (via image_load)
Suspicious BugSplat Binary Sideloading bugsplatrc.dll via DLL Search Order Hijack
Suspicious SentinelOne Binary Sideloading sentinelagentcore.dll
Suspicious 7-Zip Executable Sideloading 7z.dll Loader
Suspicious Loading of Masqueraded EndpointDlp.dll Backdoor
Suspicious Trend Micro Binary Sideloading tmdglog.dll
Suspicious DLL Sideloading via ProtonVPN Executable (via image_load)
Suspicious DLL Sideloading via OneDriveStandaloneUpdater (via image_load)
Potential DLL Sideloading via DeviceEnroller.exe Using /PhoneDeepLink
Pivot detection · T1574.001 · 9 related

Changelog

v2
  1. v2
    Candidate ingested via manual entry.2026-07-31
  2. v1
    No changelog recorded for this version.2026-07-30

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.