Windows endpoint forensics investigation using DeepBlueCLI — a PowerShell-based threat hunting tool from SANS that parses Windows event logs and surfaces suspicious activity without manual event-by-event review. The scenario involves a confirmed RDP compromise followed by Meterpreter deployment and attacker persistence.
Two log files provided in \Desktop\Investigation\:
Security.evtx — authentication, process creation, account managementSystem.evtx — service installation, system eventsDeepBlueCLI processes the Security log and automatically flags suspicious events including unusual process execution, obfuscated commands, and known attack patterns.
.\DeepBlue.ps1 .\Security.evtx

The output immediately surfaces Mike Smith as the account that executed GoogleUpdate.exe — a common masquerading technique where malware adopts legitimate-sounding names to blend in with normal system activity.
Shortly after, DeepBlueCLI flags likely Meterpreter activity at 4/10/2021 10:48:14 — Meterpreter leaves characteristic signatures in Windows event logs through its process injection and named pipe communication patterns.

MITRE: T1036.005 — Masquerading: Match Legitimate Name or Location
Running DeepBlueCLI against the System log reveals a suspicious service installation:
.\DeepBlue.ps1 .\System.evtx

The service rztbzn was created — a randomly generated six-character name consistent with Meterpreter’s service-based persistence mechanism. Meterpreter’s getsystem and persistence modules commonly install services with randomised names to avoid detection.
MITRE: T1543.003 — Create or Modify System Process: Windows Service
With DeepBlueCLI establishing the approximate attack timeline, drilling into Event Viewer for Event ID 4688 (process creation) between 10:30 and 10:50 AM on April 10, 2021 reveals the Meterpreter delivery mechanism:

Downloads\serviceupdate.exe was executed by Mike Smith — the malicious executable that established the Meterpreter reverse shell. The Downloads directory and generic service-themed name are both red flags, confirming this as the payload delivered post-RDP compromise.
MITRE: T1059.003 — Command and Scripting Interpreter: Windows Command Shell MITRE: T1021.001 — Remote Services: Remote Desktop Protocol
Checking Event ID 4720 (account creation) returns no results, meaning the attacker avoided the standard account creation event. However, filtering Event ID 4688 for net commands between 11:25 and 11:40 AM reveals the persistence mechanism:

The command net user ServiceAct /add was executed — creating a local account named ServiceAct, a service-themed name chosen to blend in with legitimate service accounts and avoid casual scrutiny.
MITRE: T1136.001 — Create Account: Local Account
The account was then added to two local groups to ensure RDP access would be available for future re-entry:

MITRE: T1098 — Account Manipulation
| Type | Value |
|---|---|
| Compromised User | Mike Smith |
| Malicious Executable | Downloads\serviceupdate[.]exe |
| Masquerading Binary | GoogleUpdate[.]exe |
| Suspicious Service | rztbzn |
| Persistence Account | ServiceAct |
| Meterpreter Activity | 2021-04-10 10:48:14 |
| Account Creation Command | net user ServiceAct /add |
| Groups Added To | Administrators, Remote Desktop Users |
| Technique | ID | Notes |
|---|---|---|
| Valid Accounts | T1078 | RDP brute force → Mike Smith account |
| Remote Desktop Protocol | T1021.001 | Initial access vector |
| Windows Command Shell | T1059.003 | serviceupdate.exe execution |
| Masquerading | T1036.005 | GoogleUpdate.exe disguise |
| Windows Service | T1543.003 | rztbzn service created by Meterpreter |
| Create Local Account | T1136.001 | net user ServiceAct /add |
| Account Manipulation | T1098 | Added to Administrators + RDP Users |
net user — always check 4688 process creation for net.exe commands as a fallback when account creation events are absentrztbzn is a strong Meterpreter persistence indicator; legitimate services use descriptive names. High-entropy short service names warrant immediate investigationGoogleUpdate.exe in an unexpected context, executed by a standard user rather than the SYSTEM account, is a reliable detection opportunity — process creation logging with 4688 makes this visible even when AV misses it