Windows Process Creation: Renamed jusched.exe Execution via Java Scheduler Names

Alerts when Java Update Scheduler descriptions are used to execute a process ending with \jusched.exe on Windows.

FreeReviewedSigma · High · v1
Product
windows
Category
process_creation
Author
Markus Neis, Swisscom (SigmaHQ), DRL 1.1
Published
2019-06-04
Updated
2026-07-30

ATT&CK techniques

Defense Evasion
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Cred Access

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule flags Windows process creation events where the process description matches Java Update Scheduler variants, but the executable name ends with \jusched.exe. Attackers may rename or masquerade legitimate-sounding binaries to blend in with expected system activity. The detection relies on Windows process creation telemetry, matching the Description field and enforcing an executable path suffix of \jusched.exe while excluding a specific image filter.

Related detections9 linkedT1036.003 — drag to rearrange
Renamed Autohotkey Binary
Suspicious Masqueraded Rundll32 with Mismatched Original Filename (via process_creation)
Suspicious Renamed git Binary gcmd.exe Execution (via process_creation)
Renamed Execution of a Renamed Windows System Utility (via process_creation)
Suspicious Renamed Pythonw Interpreter Execution via XWorm Loader (via process_creation)
Suspicious PowerShell Masquerading as Windows Terminal via process_creation
Windows Schtasks Execution with Renamed schtasks.exe Binary
Windows RMM Tool MeshAgent Execution with Renamed MeshServiceName
macOS Process Creation: MeshAgent renamed execution via --meshServiceName
Windows Process Creation: Renamed jusched.exe Execution via Java Scheduler Names
Pivot detection · T1036.003 · 9 related

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