Parent PID and Command Line Spoofing: What the Kernel Still Knows

Article banner for Parent PID and command line spoofing: red-team spoofed explorer.exe parent and blanked command line on the left, blue-team kernel truth via CreatingThreadId, ETW-TI and Event 4688 on the right

Both techniques make a process lie about itself, and both are on nearly every engagement. But they fail differently under scrutiny: one leaves a clean mechanical tell the spoof cannot erase, the other leaves nothing to compare against. Where the truth actually lives.

In-Memory .NET: Where the CLR’s Telemetry Actually Lives

Article banner for In-Memory .NET: red-team execute-assembly with no disk on the left, blue-team CLR ETW, AMSI and out-of-process detection on the right

Patch ETW and the CLR goes dark, load from a byte array and you dodge AMSI, Sysmon catches the DLL load anyway. Two of those are wrong on modern .NET and the third is structurally impossible. Where the telemetry for in-memory .NET really is, and which signals survive an operator inside the process.

Detecting Driver Loading: sc.exe vs. devcon.exe

Article banner for Detecting Driver Loading: sc.exe versus devcon.exe

Loading kernel drivers is a “Holy Grail” operation for attackers, granting Ring 0 privileges for persistence or EDR blinding. We analyze the forensic difference between the loud method (sc.exe) and the stealthy method (devcon.exe) to help Blue Teams build resilient detections.