Possible .NET Remoting Deserialisation Exploitation via REM Endpoint

PremiumReviewedSigma · Medium · v1
Category
webserver
Author
HuntRule
Published
2026-10-17
Updated
2026-10-17

ATT&CK techniques

Initial Access → Lateral Movement
  1. Recon

  2. Resource Dev

  3. Execution

  4. Persistence

  5. Priv Esc

  6. Defense Evasion

  7. Cred Access

  8. Discovery

  9. Collection

  10. C2

  11. Exfiltration

  12. Impact

What it detects

This rule detects POST or M-POST requests to a .rem endpoint used by .NET Remoting over HTTP, the transport abused to deliver serialized gadget payloads for remote code execution through insecure deserialisation. Requests to these remoting endpoints, especially with the rare M-POST verb, indicate probing or exploitation of an exposed .NET Remoting service.

Related detections9 linkedT1190 — drag to rearrange
Possible xrdp RCE Exploitation via ts_info_utf16_in Buffer Overflow (via application)
Zeek HTTP POST to /wsman without Authorization — Possible OMIGOD unauthenticated RCE (CVE-2021-38647)
Windows Terminal Service Parent Process Spawn (svchost.exe termsvcs)
Apache thread assertion error in error.log
Possible Qlik Sense Unauthenticated Path Probe via TTF Extension Bypass
Possible Nagios XI Path Traversal via Graphtemplates Directory Parameter
Possible Shellshock Bash Function Definition Injection via Process Creation
Malicious Recon Output Staged in Qlik Sense Fonts Directory by Cactus Ransomware
Possible SharePoint ToolShell Exploitation via ToolPane POST with SignOut Referer
Possible .NET Remoting Deserialisation Exploitation via REM Endpoint
Pivot detection · T1190 · 9 related

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