Case 8C3079 · Blue team / DFIR · L3 Applied
A Rare Task on Three Laptops
Live alertA stacking hunt finds a scheduled task named "OneDrive Standalone Update Task-S-1-5-21" on just 3 of 8,000 laptops, all in finance. It runs rundll32.exe on a DLL in %APPDATA%\Roaming every 4 hours. No alert ever fired.
Interview questionYour hunt found a scheduled task that only exists on three finance laptops. What do you do?
- 01 What happened?
- 02 What is the impact?
- 03 What do you do?
What a strong answer covers
Try it out loud first. Then check yourself:
- Validate: compare with the real OneDrive task (name, author, path, signer); a DLL in AppData run by rundll32 is not how OneDrive updates.
- Scope: search all hosts for the task, the DLL hash and its outbound connections, and find when and how each task was created (event 4698).
- Treat it as an incident: isolate the three hosts, collect memory and the DLL, and check what the finance users accessed.
- Close the gap: turn the hunt query into a detection, and ask why EDR and existing rules missed it.
If the interviewer pushes back
- The DLL is signed with a valid but unrelated vendor certificate. What does that tell you, and what do you do about trust in that certificate?