← ClaudeAtlas

detect-shellcode-injectionlisted

Detection and hunting methodology for shellcode injection and in-memory execution: CreateRemoteThread injection, PE and DLL injection, process hollowing, thread execution hijacking, APC injection, and reflective code loading (MITRE ATT&CK T1055 with .001 .002 .003 .004 .012 .008 .009, T1620, T1106). Keys off Windows endpoint telemetry: Sysmon EID 8, 10, 25, 7, and 1 / Security 4688, the Microsoft-Windows-Threat-Intelligence ETW provider, Microsoft Defender for Endpoint DeviceEvents, plus Linux ptrace and memfd signals. Gives the allocate-write-execute footprint, unbacked-memory signals, a memory-forensics hunt, and exploit-protection, application-control, and EDR hardening. Use when triaging a suspected process-injection or in-memory implant, hunting for CreateRemoteThread into unbacked memory or process hollowing, investigating RWX private memory, reviewing EDR injection alerts, or hardening a fleet against fileless execution.
umbrasec-labs/umbra-blue · ★ 0 · DevOps & Infrastructure · score 62
Install: claude install-skill umbrasec-labs/umbra-blue
# Shellcode Injection and In-Memory Execution - Defensive Methodology > **Tier 2 - methodology skill.** No bespoke UMBRASEC detection rule ships with this skill yet. It gives the defender's method, the log sources and signals, the hunt, and the hardening, and points to public rule sources by URL. Promotion to Tier 1 (a sourced, tuned UMBRASEC rule) is tracked in [COVERAGE.md](https://github.com/umbrasec-labs/umbra-blue/blob/main/COVERAGE.md). Do not treat the content below as citing a UMBRASEC rule; there is none for this threat yet. ## TL;DR for defenders Shellcode injection runs attacker code inside a process that is already trusted, without writing an executable to disk. Every variant is some order of the same three primitives: allocate executable memory, write a payload into it, and execute it, either in the current process or across a process boundary. The highest-value signals are a thread whose start address sits in private memory with no backing module, a process opening a handle to another process with write-and-execute rights, and an image replaced in memory after it loaded. This is Windows-primary (CreateRemoteThread, process hollowing, reflective .NET loaders, module stomping), with a Linux tail (`ptrace` writes, `process_vm_writev`, `memfd_create` fileless exec). The hard truth up front: plain Sysmon never records the allocate or write step, only the remote thread and the handle open, so full coverage needs your EDR's kernel telemetry or the `Microsoft-Windows