Stealthy injectors
Goals
Execute foreign code in a target process/kernel with minimal artifacts versus EDR/AC.
Usermode technique ladder
- CreateRemoteThread + LoadLibrary — noisy baseline (know it to avoid)
- NtCreateThreadEx + manual map
- Thread hijack (suspend/context/RIP swap/resume)
- QueueUserAPC / special user APC on alertable threads
- Module stomping / module overloading (execute in legit module RX)
- Transacted/ghost / dual-mapping variants
- Process hollowing / doppelgänging / herpaderping (know detection cost)
- SetWindowsHookEx (only if UI-thread delivery fits)
- Instrumentation callback / VEH abuse for redirect
Manual map checklist
- Map sections with correct protections; apply relocs; resolve imports (including API sets)
- TLS callbacks decision; exception directory; cookie
- Erase PE headers optional; fix or avoid module list visibility intentionally
- Prefer RW→RX transitions; avoid long RWX
Kernel injection ladder
- APC to user thread from kernel
- Attach process + write + context
- Thread creation in target via NtCreateThreadEx from kernel
- Shared sections + user trigger
OPSEC
- Call stacks, allocation stubs, RWX, cross-process handle rights, abnormal module ranges
- Clean handles; avoid known bad patterns in public GH gists
- Test under target AC/EDR with telemetry capture
Pair with
kernel-dev, game-hacking, windows-internals, hypervisor-dev.