Endpoint case
Fake PDF viewer installs a hidden scheduled task
A new scheduled task under the Windows Update folder, created by a user instead of SYSTEM. Windows Update does not do that.
- IntermediateLevel
- 25 minAbout
- New detailsEvery attempt
- KQL or SPLQuery language
Free. Read the briefing as a guest; investigating needs a free account.
The alert
Scheduled task created in a Microsoft path by a user process
New scheduled task under \Microsoft\Windows\WindowsUpdate on RID-WS-0517, created by jjohnson (not SYSTEM). Windows Update doesn't do that, right? Escalating.
From one version of the case: the company, the people and the details change with every attempt.
About this kind of alert
Scheduled tasks as persistence: a classic way to survive a reboot, often hidden among the many tasks Windows creates itself.
What you do
- Read the escalation from an L1 colleague and the events they attached.
- Hunt the logs in KQL (Microsoft Sentinel) or SPL (Splunk) and pin the evidence.
- Find the root cause and scope the incident: which accounts and hosts are affected.
- Map what you found to MITRE ATT&CK, set the severity and choose the response.
- Get a debrief: what happened, the evidence you missed, and what the attacker does next if you were wrong.
Logs you will query
| Microsoft Sentinel | Splunk |
|---|---|
WebProxy_CL | index=proxy sourcetype=cisco:cloud_security:proxy |
Sysmon | index=sysmon sourcetype=XmlWinEventLog |
SecurityEvent | index=wineventlog sourcetype=XmlWinEventLog |


