CyberKit

Network ports

Port 135/tcp: MSRPC Endpoint Mapper (DCE/RPC)

Category: Remote Management & Administration. Range: well-known. Status: iana registered.

What runs here

Windows' RPC locator service: a client connects to port 135 and asks which dynamic high port (typically 49152-65535 on modern Windows) a specific RPC interface (a WMI provider, a DCOM activation request, a remote service-control call) is actually listening on, then opens a second connection to that port to do the real work. DCOM is itself built on top of this same MSRPC transport.

Why it matters

Port 135 is almost always the first hop of Windows RPC-based lateral movement rather than the whole story: DCOM lateral movement (ATT&CK T1021.003) and remote WMI execution both start here before the substantive traffic moves to a dynamic high port, which is why blocking or tightly scoping 135 breaks both techniques outright. It is also a pure information-disclosure surface on its own, enumerating what's registered on the endpoint mapper reveals what RPC-based services a host exposes.

Where you see it

Legitimately: normal Windows RPC activity (WMI queries, DCOM activation, remote service management from admin tooling). Anomalously/maliciously: DCOM lateral movement via objects like MMC20.Application or ShellWindows, remote WMI process creation (Win32_Process.Create), or reconnaissance enumerating registered RPC interfaces.

What to look for

Indicators
SignalWhat it means
135 followed by a high dynamic portA connection to tcp/135 immediately followed by a second connection from the same source to a port in the 49152-65535 range is the signature DCE/RPC two-step, visible in Sysmon Event ID 3 (Network Connection) chains.
DCOM errors (10009/10028)System-log events 10009 (older Windows) / 10028 (Windows Server 2016+) ("DCOM was unable to communicate with the computer") are a byproduct signal of an attempted, if failed or blocked, DCOM/RPC connection, not proof of a successful one.

In practice

A workstation-to-workstation connection to tcp/135 followed within seconds by a connection to a high dynamic port, with no corresponding helpdesk or admin activity, matches the DCOM lateral-movement pattern documented for objects like MMC20.Application. Worth pivoting on the source process on the initiating host.

Related ports

  • 445/tcp: SMB (Server Message Block) / CIFS
  • 5985/tcp: WinRM (Windows Remote Management): HTTP

ATT&CK techniques

Sources