detecting-process-injection-techniques

Detects and analyzes process injection techniques using memory forensics, Sysmon events, and API monitoring.

954|172|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/xalgord/xalgorix --skill detecting-process-injection-techniques
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: detecting-process-injection-techniques
Source: https://github.com/xalgord/xalgorix/tree/main/internal/tools/skills/data/malware-analysis/detecting-process-injection-techniques
Command: npx skills add https://github.com/xalgord/xalgorix --skill detecting-process-injection-techniques

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Malware frequently hides inside legitimate Windows processes through injection techniques like DLL injection, process hollowing, and APC injection, making it invisible to basic process listing and file-based scans. This Skill provides a structured forensic workflow to detect, classify, and analyze injected code so analysts can confirm real compromises instead of chasing false positives.

Core Features & Use Cases

  • Memory Forensics Detection: Uses Volatility 3 plugins (malfind, hollowfind, vadinfo, ldrmodules) to find RWX regions, unbacked PE images, and hollowed processes in memory dumps.
  • Technique Classification: Maps artifacts to specific injection methods including classic DLL injection, process hollowing, APC injection, thread hijacking, reflective loading, doppelganging, and AtomBombing.
  • Sysmon Event Analysis: Parses Event IDs 1, 8, and 10 to reconstruct injection timelines and identify source processes even after they terminate.
  • Payload Analysis & Detection Engineering: Dumps and disassembles injected code, scans it with YARA, maps findings to MITRE ATT&CK T1055 sub-techniques, and produces Sigma detection rules.
  • Use Case: An EDR alerts on svchost.exe making unusual HTTPS connections; follow the workflow to dump memory, confirm hollowing via image-hash mismatch, extract a Cobalt Strike Beacon, and generate a Sigma rule to catch recurrence.

Quick Start

Analyze this memory dump for process injection and tell me which technique was used against svchost.exe.

Frequently Asked Questions about detecting-process-injection-techniques

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect process injection with Volatility?

Run the malfind plugin against the memory dump to find PAGE_EXECUTE_READWRITE regions and PE headers in non-image memory. Corroborate with ldrmodules for unlinked modules, vadinfo for suspicious VAD entries, and hollowfind for image-vs-disk mismatches.

How to detect process hollowing in a memory dump?

Use Volatility's hollowfind plugin to compare the in-memory image base and headers against the on-disk file hash. Also check the parent process lineage and whether the process was created in a suspended state, which are strong hollowing indicators.

Which Sysmon events detect process injection?

Sysmon Event ID 8 logs CreateRemoteThread calls and Event ID 10 logs ProcessAccess with rights like PROCESS_VM_WRITE and PROCESS_CREATE_THREAD. Event ID 1 helps reconstruct parent-child relationships for hollowing detection.

Why does malfind miss some injected code?

malfind misses injections using non-RWX protections or stripped MZ/PE headers, since stealthy loaders flip page protections after allocation or zero the header. Use ldrmodules, vadinfo, and pe-sieve or hollows_hunter to corroborate.

What are the limitations of CreateRemoteThread detection?

CreateRemoteThread monitoring only catches classic injection; APC injection, thread hijacking via SetThreadContext, SetWindowsHookEx, and NtCreateThreadEx variants leave no Event ID 8. Pivot to thread start addresses outside known modules and ProcessAccess events instead.

Can legitimate software trigger process injection alerts?

Yes, antivirus and EDR agents, .NET and Java JIT compilers, and accessibility or IME software legitimately allocate executable memory or hook other processes. Validate the signer, parent process, and behavior before flagging RWX regions or cross-process access.