Summary
This was a Windows threat-hunting exercise based on exported event logs. The task was to reconstruct an attack chain from the first user interaction through persistence, execution, privilege escalation, and the final suspicious process tree.
The answers were pulled from Sysmon and Security logs by correlating process creation, registry changes, and command-line evidence.
Analysis
The most useful telemetry was:
- Sysmon Event ID 1 for process creation
- Sysmon Event ID 10 for process access
- Sysmon Event ID 13 for registry changes
The chain became clear once those records were linked together:
- the payload started as
MicrosoftUpdate.cpl - the execution path used
explorer.exe -> control.exe -> rundll32.exe - persistence was set through a
Runregistry key - user enumeration followed with PowerShell
- escalation happened through
RunasCsand thenGodPotato
Exploitation
The relevant answers were:
MicrosoftUpdate.cpl10.13.52.111:8888explorer.exe-control.exe-rundll32.exemsedge.exeHKCU\Software\Microsoft\Windows\CurrentVersion\Run\MicrosoftUpdatepowershell.exe -Command Get-LocalUserRunasCs.exe steve.stevens P@ssw0rd "rundll32 shell32.dll,Control_RunDLL C:\Users\Public\MicrosoftUpdate.cpl"GodPotato-NET4.exe -cmd "cmd.exe /c rundll32 shell32.dll,Control_RunDLL C:\Users\Public\MicrosoftUpdate.cpl"SeImpersonatePrivilegeC:\Users\Public\explorer.exe
The important point is that all of those answers came from the same timeline, not isolated log lines.
Flag
Q1: MicrosoftUpdate.cpl
Q2: 10.13.52.111:8888
Q3: explorer.exe-control.exe-rundll32.exe
Q4: msedge.exe
Q5: HKCU\Software\Microsoft\Windows\CurrentVersion\Run\MicrosoftUpdate
Q6: powershell.exe -Command Get-LocalUser
Q7: RunasCs.exe steve.stevens P@ssw0rd "rundll32 shell32.dll,Control_RunDLL C:\Users\Public\MicrosoftUpdate.cpl"
Q8: GodPotato-NET4.exe -cmd "cmd.exe /c rundll32 shell32.dll,Control_RunDLL C:\Users\Public\MicrosoftUpdate.cpl"
Q9: SeImpersonatePrivilege
Q10: C:\Users\Public\explorer.exe