Investigating Windows 3.x
Overview — A Blue Team forensics challenge in which you receive an endpoint plus the evidence collected from it (a Process Monitor capture, an Autoruns snapshot, PowerShell transcripts and Sysmon logs) and must reconstruct the attack. The story: a Run-key persistence entry loads a Base64 PowerShell payload from the registry, that payload tampers with the Fax and Print services, a second-stage PowerShell Empire stager calls home, and the agent injects itself intoexplorer.exewithInvoke-PSInject.
| Platform | TryHackMe |
| Category | Blue Team & SOC |
| Difficulty | Medium |
| Room | Investigating Windows 3.x |
Attack map
HKCU\...\Run\Updater (Sysmon EID 13, T1547.001)
| powershell -c "$x = (HKCU:\Software\Microsoft\Windows\CurrentVersion Debug).Debug;
| powershell -Win Hidden -enc $x"
v
Registry value "Debug" = Base64 (UTF-16LE) PowerShell, stage 1
| sc.exe start Fax + TCP connect to localhost:9299
| sends a second Base64 blob
v
Stage 2: kill FXSSVC, delete C:\Windows\System32\ualapi.dll
| disable ScriptBlock logging + AMSI bypass
| download from /admin/get.php (PowerShell Empire default profile)
v
powershell.exe PID 3088 (Sysmon EID 1, -noP -sta -w 1 -enc ...)
| CreateRemoteThread (Sysmon EID 8) Invoke-PSInject (T1055)
v
explorer.exe PID 2684 -> C2 over HTTP to an EC2-hosted server
Setup and the evidence on the box
The suggested background rooms are Core Windows Processes, Windows Event Logs, Sysinternals, Sysmon, YARA and MITRE. Connect over RDP as Administrator with the lab-provided password (blueT3aming!) and open an elevated command prompt and PowerShell. The target does not respond to ping and needs a few minutes to boot.
xfreerdp /v:MACHINE_IP /cert:ignore /u:Administrator /p:'blueT3aming!' /h:1024 /w:1500 +clipboard
The Desktop holds two pieces of evidence, and the Documents folder holds a third:
| Artifact | What it is | Use it for |
|---|---|---|
Logfile.PML | Process Monitor capture (about 126 MB) | Process tree, network, registry and file activity with timestamps |
WIN-Q5JJRDM876J.arn | Autoruns snapshot | Persistence entries (Logon, Services, WMI...) |
Documents\20210121\PowerShell_transcript.*.txt | Four PowerShell transcript files | Everything typed or run in PowerShell, including decoded payloads |
Transcripts matter a lot here. When PowerShell transcription is on, the full session text, including commands that were originally Base64-encoded, is written to disk in clear text. The Sysmon operational log (Event Viewer, Applications and Services Logs, Microsoft, Windows, Sysmon, Operational) is the fifth source and the best one for exact timestamps and process IDs.
Root Access unlocks the content you can't see — everything else on the site is already open.
See Root Access plansNo account? Create one free then upgrade from your console.