Windows Java Process Started with Remote Debugging Enabled for Non-Localhost Connections

Identifies Java processes started with JDWP dt_socket remote debugging on a non-localhost address.

FreeReviewedSigma · Medium · v2
Product
windows
Category
process_creation
Author
Florian Roth (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2019-01-16
Updated
2026-07-31

ATT&CK techniques

Execution
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Persistence

  5. Priv Esc

  6. Defense Evasion

  7. Cred Access

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule identifies Windows process creation events where a Java command line includes JDWP remote debugging settings (transport=dt_socket,address=) and does not restrict connections to localhost. Allowing remote debugging beyond 127.0.0.1 or localhost can expose an interactive debugging interface that attackers may leverage for inspection or control. The detection relies on process creation command-line telemetry, matching the presence of JDWP parameters while excluding common local-only address configurations.

Related detections9 linkedT1203 — drag to rearrange
Suspicious Child Process Spawned by WinRAR via Process Creation
Malicious Script Execution from WinRAR Extraction Directory via CVE-2023-38831
Suspicious Execution From WinRAR Temporary Extraction Path via Command Line (via process_creation)
Malicious Shell Execution via Foomatic-rip Print Filter through CUPS Exploit
Suspicious Network Connection From CUPS Foomatic-Rip Child Process
Antivirus signatures matching APT malware naming patterns
Antivirus Remote Access Tool Signature Matches Known RAT Names
Malicious Microsoft Word Spawning Anomalous Child Process via CVE-2023-36884 (via process_creation)
Possible ExifTool CVE-2026-3102 Command Injection via Child Process Spawn (via process_creation)
Windows Java Process Started with Remote Debugging Enabled for Non-Localhost Connections
Pivot detection · T1203 · 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.