Suspicious Application Config File Dropped Beside Trusted .NET Binary for App Domain Manager Injection

PremiumReviewedSigma · Medium · v1
Product
windows
Category
file_event
Author
HuntRule
Published
2026-09-27
Updated
2026-09-27

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 detects creation of an application configuration file with the .exe.config extension in a user-writable location, the delivery step for App Domain Manager injection where the config redirects a trusted signed .NET binary to load an attacker assembly. The config declares an appDomainManagerAssembly that the runtime honors on startup, executing attacker code under the trusted process. A dropped .exe.config in a temporary or user directory beside a signed binary is a strong hijack indicator.

Related detections9 linkedT1574.001 — drag to rearrange
Malicious DLL Execution from Browser Cache via rundll32.exe (via process_creation)
Malicious DLL ServerLevelPluginDll Registration - "serverlevelplugindll" Feature Abuse (via dns-server)
Malicious DLL Sideloading via Cisco Webex ptService Loading wbxtrace From Non-Standard Path (via image_load)
APT32 DLL Sideloading via Analyzer.exe Loading mglobal.dll (via image_load)
Suspicious DLL Sideloaded by a Signed Binary From a User-Writable Path (via image_load)
Suspicious C2Looper DLL Side-Loading via OneDrive wtsapi32 (via file_event)
Suspicious Tablacus Explorer Execution from ProgramData for DLL Search-Order Hijacking
Suspicious calc.exe Quit Execution From Non-System Directory via DLL Side-Loading
Suspicious ctfmon.exe Execution From Non-System Directory via DLL Side-Loading
Suspicious Application Config File Dropped Beside Trusted .NET Binary for App Domain Manager Injection
Pivot detection · T1574.001 · 9 related

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