Hunt for DCOM-based lateral movement by detecting abuse of MMC20.Application, ShellBrowserWindow, and ShellWindows COM objects through Sysmon Event ID 1 (process creation) and Event ID 3 (network connection) correlation, WMI event analysis, RPC endpoint mapper traffic on port 135, and DCOM-specific parent-child process relationships.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Une commande directe contourne le prompt de vérification. Examinez la source avant de l'exécuter.
Hunt for DCOM-based lateral movement by detecting abuse of MMC20.Application, ShellBrowserWindow, and ShellWindows COM objects through Sysmon Event ID 1 (process creation) and Event ID 3 (network connection) correlation, WMI event analysis, RPC endpoint mapper traffic on port 135, and DCOM-specific parent-child process relationships.
Authorized Testing Disclaimer: The offensive techniques and attack simulations described in this skill are intended exclusively for authorized penetration testing, red team engagements, purple team exercises, and security research conducted with explicit written permission from the system owner. Unauthorized use of these techniques against systems you do not own or have permission to test is illegal and unethical. Always operate within the scope of your engagement and comply with applicable laws and regulations.
Overview
Distributed Component Object Model (DCOM) enables remote execution of COM objects across a network using RPC. Adversaries abuse specific DCOM objects -- MMC20.Application (CLSID {49B2791A-B1AE-4C90-9B8E-E860BA07F889}), ShellBrowserWindow (CLSID {C08AFD90-F2A1-11D1-8455-00A0C91F3880}), and ShellWindows (CLSID {9BA05972-F6A8-11CF-A442-00A0C90A8F39}) -- to execute commands on remote hosts without dropping files, making this a stealthy lateral movement technique mapped to MITRE ATT&CK T1021.003. This skill provides detection strategies using Sysmon telemetry, Windows Security Event correlation, network monitoring, and SIEM detection rules to identify DCOM abuse in enterprise environments.
When to Use
Proactively hunting for lateral movement in Active Directory environments where DCOM is enabled
Investigating alerts for suspicious mmc.exe, dllhost.exe, or explorer.exe child process creation on servers
Building detection rules for MITRE ATT&CK T1021.003 (Remote Services: Distributed Component Object Model)
Correlating Sysmon Event ID 1 (Process Create) and Event ID 3 (Network Connection) to trace DCOM-based command execution chains
Auditing DCOM exposure across the domain to reduce lateral movement attack surface
During purple team exercises validating detection coverage for DCOM-based techniques
Do not use as a replacement for EDR-based lateral movement detection, without Sysmon or equivalent process telemetry deployed on endpoints, or in isolation without correlating network-level and host-level indicators.
Prerequisites
Sysmon deployed on endpoints with configuration capturing Event ID 1 (Process Create), Event ID 3 (Network Connection), Event ID 7 (Image Loaded), and Event ID 10 (Process Access)
Windows Security Event Logs forwarded to SIEM (Event IDs 4624, 4672, 4688)
SIEM platform (Splunk, Elastic, Microsoft Sentinel) with correlation capability
Network monitoring for RPC traffic (TCP 135 and dynamic high ports 49152-65535)
Baseline inventory of legitimate DCOM usage in the environment
Understanding of MITRE ATT&CK Lateral Movement tactic (TA0008) and T1021.003
Workflow
Step 1: Understand DCOM Lateral Movement Attack Vectors
DCOM lateral movement exploits three primary COM objects. Each has distinct forensic artifacts.
MMC20.Application -- The attacker instantiates the MMC snap-in remotely and calls ExecuteShellCommand to run arbitrary commands on the target. This spawns mmc.exe as a child of svchost.exe (DcomLaunch service) on the target.
ShellBrowserWindow -- Uses the Document.Application.ShellExecute method to execute commands through an existing explorer.exe process. Unlike MMC20, this does not create a new process for the COM server itself, making it stealthier.
ShellWindows -- Similar to ShellBrowserWindow, it activates within an existing explorer.exe instance and executes child processes from explorer.exe. The absence of a new COM server process makes it harder to detect without proper telemetry.
# ATTACK SIMULATION (authorized testing only)
# These commands demonstrate what adversaries execute -- use only in lab environments
# MMC20.Application lateral movement
# $dcom = [System.Activator]::CreateInstance(
# [Type]::GetTypeFromProgID("MMC20.Application", "TARGET_IP"))
# $dcom.Document.ActiveView.ExecuteShellCommand(
# "cmd.exe", $null, "/c whoami > C:\temp\output.txt", "7")
# ShellWindows lateral movement
# $dcom = [System.Activator]::CreateInstance(
# [Type]::GetTypeFromCLSID(
# [guid]"9BA05972-F6A8-11CF-A442-00A0C90A8F39", "TARGET_IP"))
# $dcom.item().Document.Application.ShellExecute(
# "cmd.exe", "/c calc.exe", "C:\windows\system32", $null, 0)
# ShellBrowserWindow lateral movement
# $dcom = [System.Activator]::CreateInstance(
# [Type]::GetTypeFromCLSID(
# [guid]"C08AFD90-F2A1-11D1-8455-00A0C91F3880", "TARGET_IP"))
# $dcom.Document.Application.ShellExecute(
# "cmd.exe", "/c net user", "C:\windows\system32", $null, 0)
Step 2: Configure Sysmon for DCOM Detection
<!-- Sysmon configuration excerpt for DCOM lateral movement detection --><!-- Add these rules to your existing Sysmon config --><Sysmonschemaversion="4.90"><EventFiltering><!-- Event ID 1: Process Creation - Detect DCOM-spawned processes --><RuleGroupname="DCOM_ProcessCreate"groupRelation="or"><ProcessCreateonmatch="include"><!-- MMC20.Application: mmc.exe spawning child processes --><ParentImagecondition="end with">mmc.exe</ParentImage><!-- DcomLaunch service spawning COM servers --><ParentCommandLinecondition="contains">DcomLaunch</ParentCommandLine><!-- dllhost.exe spawning suspicious children --><ParentImagecondition="end with">dllhost.exe</ParentImage><!-- explorer.exe spawning cmd/powershell (ShellWindows/ShellBrowserWindow) --><RulegroupRelation="and"><ParentImagecondition="end with">explorer.exe</ParentImage><Imagecondition="end with">cmd.exe</Image></Rule><RulegroupRelation="and"><ParentImagecondition="end with">explorer.exe</ParentImage><Imagecondition="end with">powershell.exe</Image></Rule></ProcessCreate></RuleGroup><!-- Event ID 3: Network Connection - Track DCOM RPC connections --><RuleGroupname="DCOM_NetworkConnect"groupRelation="or"><NetworkConnectonmatch="include"><!-- RPC Endpoint Mapper --><DestinationPortcondition="is">135</DestinationPort><!-- DCOM processes making network connections --><Imagecondition="end with">mmc.exe</Image><Imagecondition="end with">dllhost.exe</Image><!-- svchost.exe DcomLaunch connections --><RulegroupRelation="and"><Imagecondition="end with">svchost.exe</Image><DestinationPortcondition="more than">49151</DestinationPort></Rule></NetworkConnect></RuleGroup><!-- Event ID 7: Image Loaded - DCOM-related DLLs --><RuleGroupname="DCOM_ImageLoaded"groupRelation="or"><ImageLoadonmatch="include"><ImageLoadedcondition="end with">comsvcs.dll</ImageLoaded><ImageLoadedcondition="end with">ole32.dll</ImageLoaded><ImageLoadedcondition="end with">rpcrt4.dll</ImageLoaded></ImageLoad></RuleGroup></EventFiltering></Sysmon>
Step 3: Build SIEM Detection Rules for DCOM Object Abuse
# Sigma Rule: MMC20.Application DCOM Lateral Movementtitle:DCOMLateralMovementviaMMC20.Applicationid:8a3b5f2e-c1d4-4a9f-b237-1e6f8d2c3a4bstatus:stabledescription:>
Detects remote instantiation of MMC20.Application DCOM object by monitoring
for mmc.exe spawned by svchost.exe DcomLaunch service with subsequent child
process creation, indicating T1021.003 lateral movement.
references:-https://attack.mitre.org/techniques/T1021/003/-https://www.cybereason.com/blog/dcom-lateral-movement-techniques-https://www.mdsec.co.uk/2020/09/i-like-to-move-it-windows-lateral-movement-part-2-dcom/logsource:category:process_creationproduct:windowsdetection:selection_parent:ParentImage|endswith:'\mmc.exe'selection_child:Image|endswith:-'\cmd.exe'-'\powershell.exe'-'\pwsh.exe'-'\wscript.exe'-'\cscript.exe'-'\mshta.exe'-'\rundll32.exe'-'\regsvr32.exe'filter_legitimate:ParentCommandLine|contains:-'devmgmt.msc'-'diskmgmt.msc'-'services.msc'-'compmgmt.msc'condition:selection_parentandselection_childandnotfilter_legitimatelevel:hightags:-attack.lateral_movement-attack.t1021.003falsepositives:-LegitimateremoteMMCadministrationbyauthorizedITstaff-SCCMorothermanagementtoolsusingDCOMforremotemanagement
# Sigma Rule: ShellWindows/ShellBrowserWindow DCOM Lateral Movementtitle:DCOMLateralMovementviaShellWindowsorShellBrowserWindowid:2f7c9d1e-a8b3-4c5f-9012-3e4d5f6a7b8cstatus:stabledescription:>
Detects DCOM lateral movement using ShellWindows (CLSID 9BA05972) or
ShellBrowserWindow (CLSID C08AFD90) by monitoring for explorer.exe spawning
cmd.exe or powershell.exe on systems where no user is interactively logged on,
or where the network logon (Type 3) precedes the process creation.
references:-https://attack.mitre.org/techniques/T1021/003/-https://www.elastic.co/guide/en/security/8.19/incoming-dcom-lateral-movement-with-shellbrowserwindow-or-shellwindows.htmllogsource:category:process_creationproduct:windowsdetection:selection:ParentImage|endswith:'\explorer.exe'Image|endswith:-'\cmd.exe'-'\powershell.exe'-'\pwsh.exe'-'\mshta.exe'-'\wscript.exe'-'\cscript.exe'filter_interactive:LogonId:'0x3e7'condition:selectionandnotfilter_interactivelevel:mediumtags:-attack.lateral_movement-attack.t1021.003falsepositives:-UserslaunchingcommandpromptsfromExplorercontextmenus-Softwareinstallerslaunchingchildprocessesfromexplorer.exe
# Sigma Rule: Sysmon Network Connection to RPC Endpoint Mapper from DCOM Processtitle:DCOMProcessInboundRPCConnectionFollowedbyProcessCreationid:4d9e2f1a-b3c5-4a7f-8901-2c3d4e5f6a7bstatus:experimentaldescription:>
Correlates Sysmon Event ID 3 (Network Connection) on port 135 with
subsequent Event ID 1 (Process Create) from DCOM parent processes
(mmc.exe, dllhost.exe, explorer.exe) within a short time window.
logsource:product:windowsservice:sysmondetection:network_connection:EventID:3DestinationPort:135Initiated:'false'process_creation:EventID:1ParentImage|endswith:-'\mmc.exe'-'\dllhost.exe'-'\svchost.exe'timeframe:30scondition:network_connection|nearprocess_creationlevel:hightags:-attack.lateral_movement-attack.t1021.003
Step 4: Deploy Splunk and KQL Detection Queries
# Splunk: Detect MMC20.Application DCOM Lateral Movement
# Correlates network logon (4624 Type 3) with mmc.exe process creation
index=wineventlog sourcetype="XmlWinEventLog:Microsoft-Windows-Sysmon/Operational"
EventCode=1 ParentImage="*\\mmc.exe"
(Image="*\\cmd.exe" OR Image="*\\powershell.exe" OR Image="*\\pwsh.exe"
OR Image="*\\wscript.exe" OR Image="*\\cscript.exe" OR Image="*\\mshta.exe")
| eval target_host=ComputerName
| join target_host type=inner
[search index=wineventlog EventCode=4624 LogonType=3
| where AuthenticationPackageName="NTLM" OR AuthenticationPackageName="Kerberos"
| eval target_host=ComputerName
| rename IpAddress as source_ip, TargetUserName as logon_user
| fields target_host source_ip logon_user _time]
| where abs(_time - relative_time(now(), "-5m")) < 300
| table _time target_host Image ParentImage CommandLine source_ip logon_user
| sort -_time
# Splunk: Detect ShellWindows/ShellBrowserWindow DCOM Lateral Movement
# Identifies explorer.exe spawning suspicious child processes on servers
index=wineventlog sourcetype="XmlWinEventLog:Microsoft-Windows-Sysmon/Operational"
EventCode=1 ParentImage="*\\explorer.exe"
(Image="*\\cmd.exe" OR Image="*\\powershell.exe" OR Image="*\\pwsh.exe")
| eval target_host=ComputerName
| join target_host type=inner
[search index=wineventlog sourcetype="XmlWinEventLog:Microsoft-Windows-Sysmon/Operational"
EventCode=3 DestinationPort=135 Initiated="false"
| eval target_host=ComputerName
| rename SourceIp as dcom_source_ip
| fields target_host dcom_source_ip _time]
| where abs(_time - relative_time(now(), "-2m")) < 120
| stats count values(Image) as child_processes values(CommandLine) as commands
by target_host dcom_source_ip
| where count > 0
| table target_host dcom_source_ip child_processes commands count
# Splunk: DCOM RPC Endpoint Mapper Connection Anomaly
# Identifies hosts receiving unusual volumes of inbound RPC connections
index=wineventlog sourcetype="XmlWinEventLog:Microsoft-Windows-Sysmon/Operational"
EventCode=3 DestinationPort=135 Initiated="false"
| stats dc(SourceIp) as unique_sources count by ComputerName
| where unique_sources > 3 OR count > 10
| sort -unique_sources
| table ComputerName unique_sources count
-- Microsoft Sentinel KQL: DCOM Lateral Movement via MMC20.Application
let dcom_network = SysmonEvent
| where EventID == 3
| where DestinationPort == 135
| where InitiatedConnection == false
| project NetworkTime=TimeGenerated, TargetComputer=Computer,
SourceIP=SourceIp, DestPort=DestinationPort;
let dcom_process = SysmonEvent
| where EventID == 1
| where ParentImage endswith "\\mmc.exe"
or ParentImage endswith "\\dllhost.exe"
| where Image endswith "\\cmd.exe"
or Image endswith "\\powershell.exe"
or Image endswith "\\pwsh.exe"
or Image endswith "\\wscript.exe"
or Image endswith "\\mshta.exe"
| project ProcessTime=TimeGenerated, TargetComputer=Computer,
ParentImage, Image, CommandLine, User;
dcom_network
| join kind=inner (dcom_process) on TargetComputer
| where abs(datetime_diff('second', NetworkTime, ProcessTime)) < 60
| project NetworkTime, ProcessTime, TargetComputer, SourceIP,
ParentImage, Image, CommandLine, User
| sort by NetworkTime desc
-- Microsoft Sentinel KQL: ShellWindows DCOM Lateral Movement
SecurityEvent
| where EventID == 4624 and LogonType == 3
| where AuthenticationPackageName in ("NTLM", "Kerberos")
| project LogonTime=TimeGenerated, TargetComputer=Computer,
SourceIP=IpAddress, LogonUser=TargetUserName
| join kind=inner (
SysmonEvent
| where EventID == 1
| where ParentImage endswith "\\explorer.exe"
| where Image endswith "\\cmd.exe"
or Image endswith "\\powershell.exe"
or Image endswith "\\pwsh.exe"
| project ProcessTime=TimeGenerated, TargetComputer=Computer,
Image, CommandLine, User
) on TargetComputer
| where ProcessTime between (LogonTime .. (LogonTime + 2m))
| project LogonTime, ProcessTime, TargetComputer, SourceIP,
LogonUser, Image, CommandLine
| sort by LogonTime desc
# Audit DCOM configuration across the domain
# Enumerate remotely accessible DCOM objects
# List DCOM applications registered on local system
Get-CimInstance -ClassName Win32_DCOMApplication |
Select-Object AppID, Name |
Sort-Object Name |
Format-Table -AutoSize
# Check DCOM launch permissions for high-risk objects
$clsids = @{
"MMC20.Application" = "{49B2791A-B1AE-4C90-9B8E-E860BA07F889}"
"ShellWindows" = "{9BA05972-F6A8-11CF-A442-00A0C90A8F39}"
"ShellBrowserWindow" = "{C08AFD90-F2A1-11D1-8455-00A0C91F3880}"
"Excel.Application" = "{00024500-0000-0000-C000-000000000046}"
"Outlook.Application" = "{0006F03A-0000-0000-C000-000000000046}"
}
foreach ($name in $clsids.Keys) {
$clsid = $clsids[$name]
$regPath = "HKLM:\SOFTWARE\Classes\CLSID\$clsid"
if (Test-Path $regPath) {
$launchPermission = (Get-ItemProperty -Path "$regPath" -Name "LaunchPermission" -ErrorAction SilentlyContinue)
Write-Host "[*] $name ($clsid): $(if ($launchPermission) { 'Custom permissions set' } else { 'DEFAULT permissions (potentially exploitable)' })"
} else {
Write-Host "[-] $name ($clsid): Not found on this system"
}
}
# Check if DCOM is enabled (should be restricted on servers that don't need it)
$dcomEnabled = (Get-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Ole" -Name "EnableDCOM").EnableDCOM
Write-Host "`n[*] DCOM Enabled: $dcomEnabled"
# Check remote launch and activation permissions
$remoteLaunch = (Get-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Ole" -Name "DefaultLaunchPermission" -ErrorAction SilentlyContinue)
Write-Host "[*] Default Launch Permission: $(if ($remoteLaunch) { 'Custom' } else { 'System Default' })"
# Hardening: Restrict DCOM remote access via Group Policy
# These settings should be applied via GPO in production
# Disable DCOM on systems that do not require it
# Computer Configuration > Administrative Templates > System > Distributed COM >
# Application Compatibility > Enable Distributed COM on this computer = Disabled
# Restrict DCOM launch permissions via registry
# Set-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Ole" -Name "EnableDCOM" -Value "N"
# Block RPC/DCOM at the host firewall for non-admin traffic
# New-NetFirewallRule -DisplayName "Block Inbound DCOM/RPC" `
# -Direction Inbound -LocalPort 135 -Protocol TCP `
# -Action Block -RemoteAddress "Any" `
# -Group "DCOM Hardening"
#
# New-NetFirewallRule -DisplayName "Allow DCOM from Admin Subnets" `
# -Direction Inbound -LocalPort 135 -Protocol TCP `
# -Action Allow -RemoteAddress "10.10.0.0/24" `
# -Group "DCOM Hardening"
# Windows Firewall: Restrict dynamic RPC port range
# netsh int ipv4 set dynamicport tcp start=49152 num=1024
Key Concepts
Term
Definition
DCOM (T1021.003)
Distributed Component Object Model -- extends COM to allow remote object instantiation and method invocation over RPC, abused for lateral movement
COM object (CLSID {9BA05972-F6A8-11CF-A442-00A0C90A8F39}) that activates within an existing explorer.exe process, executing commands without creating a new COM server process
ShellBrowserWindow
COM object (CLSID {C08AFD90-F2A1-11D1-8455-00A0C91F3880}) similar to ShellWindows, uses Document.Application.ShellExecute for stealthy command execution
RPC Endpoint Mapper
Service on TCP port 135 that maps RPC interfaces to dynamic ports; all DCOM communication begins with an endpoint mapper query
Sysmon Event ID 1
Process Create event capturing parent-child process relationships, command lines, and user context -- critical for identifying DCOM-spawned processes
Sysmon Event ID 3
Network Connection event capturing source/destination IPs and ports -- used to correlate RPC connections with subsequent process creation
DcomLaunch
Windows service (svchost.exe -k DcomLaunch) that manages DCOM server process activation; parent process of COM servers spawned via remote DCOM calls
WMI-Activity ETW
Event Tracing for Windows provider that logs WMI method calls, instance creations, and queries -- provides visibility into DCOM-triggered WMI operations
Tools & Systems
Tool
Purpose
Sysmon
Endpoint telemetry for process creation (EID 1), network connections (EID 3), and image loads (EID 7) essential for DCOM detection
Splunk / Elastic SIEM
Log aggregation and correlation platform for DCOM detection rules and threat hunting queries
Microsoft Sentinel
Cloud SIEM with built-in KQL queries and analytics rules for DCOM lateral movement detection
Sigma
Vendor-agnostic detection rule format for portable DCOM detection rules
Zeek
Network security monitor for DCE-RPC protocol analysis and RPC endpoint mapper traffic monitoring
Atomic Red Team
MITRE ATT&CK test framework with T1021.003 atomics for validating DCOM detection coverage
Impacket (dcomexec.py)
Python-based DCOM execution tool used by attackers and red teamers for testing DCOM lateral movement
CIMSession / PowerShell
Native Windows tooling for DCOM object instantiation used in both legitimate administration and attacks
Common Scenarios
Scenario 1: MMC20.Application Lateral Movement to File Server
Context: A SOC analyst receives an alert for mmc.exe spawning cmd.exe on a file server (10.10.20.50) at 03:22 UTC. No administrator activity is scheduled at this time.
Approach:
Query Sysmon Event ID 1 on 10.10.20.50: confirm mmc.exe (parent: svchost.exe -k DcomLaunch) spawned cmd.exe with command line /c net user /domain > C:\temp\users.txt
Query Sysmon Event ID 3 on 10.10.20.50: identify inbound TCP connection on port 135 from 10.10.5.30 at 03:22:01, followed by a high-port connection at 03:22:02
Correlate Event ID 4624 on 10.10.20.50: find LogonType 3 from 10.10.5.30 at 03:22:00 with admin credentials
Investigate 10.10.5.30: check for compromise indicators -- find Mimikatz artifacts in memory, evidence of credential dumping at 03:15
Trace the attack chain: initial phishing compromise at 02:45, credential theft at 03:15, DCOM lateral movement at 03:22
Contain: isolate 10.10.5.30 and 10.10.20.50, force password reset for compromised admin account, block inbound RPC from non-admin subnets
Pitfalls:
Dismissing mmc.exe activity as legitimate MMC administration without checking the parent process and command line
Not correlating the network logon (4624) with the process creation to identify the true source host
Failing to investigate the source host for initial compromise indicators
Scenario 2: ShellWindows Stealthy Lateral Movement
Context: During a threat hunt, an analyst queries for explorer.exe spawning cmd.exe on domain controllers and finds several instances on DC01 with no interactive logon sessions.
Approach:
Verify no interactive sessions: query Event ID 4624 LogonType 2 or 10 on DC01 -- none found during the time window
Query Sysmon Event ID 1: explorer.exe spawning cmd.exe with encoded PowerShell commands at 14:05, 14:12, and 14:18
Decode the PowerShell: reveals reconnaissance commands (Get-ADUser, Get-ADGroup, Get-ADComputer)
Query Sysmon Event ID 3: inbound RPC connections from 10.10.3.15 preceding each process creation
Identify the ShellWindows pattern: no new mmc.exe or dllhost.exe process created -- commands execute through existing explorer.exe, consistent with ShellWindows/ShellBrowserWindow DCOM abuse
Investigate 10.10.3.15: compromised workstation with Cobalt Strike beacon artifacts
Pitfalls:
Missing the attack because ShellWindows does not create a separate COM server process -- requires monitoring explorer.exe child processes
Not having Sysmon Event ID 3 configured to capture network connections from explorer.exe
Filtering out explorer.exe as a legitimate parent process without considering the server context
