Webapp Analyzing Heap Spray Exploitation

---
name: webapp-analyzing-heap-spray-exploitation
description: Detect and analyze heap spray attacks in memory dumps using Volatility3 plugins to identify NOP sled patterns, shellcode landing zones, and suspicious large allocations in process virtual address space.
domain: webapp
category: endpoint-security
hide: true
license: Apache-2.0
metadata:
  manifest_entry: src/corpus/webapp-analyzing-heap-spray-exploitation/SKILL.md
---
# Analyzing Heap Spray Exploitation

## Overview

Heap spraying is an exploitation technique that fills large regions of a process's heap with attacker-controlled data (typically NOP sleds followed by shellcode) to increase the reliability of code execution exploits. This skill covers detecting heap spray artifacts in memory dumps using Volatility3's malfind, vadinfo, and memmap plugins, identifying suspicious contiguous memory allocations, scanning for NOP sled patterns (0x90, 0x0c0c0c0c), and extracting embedded shellcode for analysis.


## When to Use

- When investigating security incidents that require analyzing heap spray exploitation
- When building detection rules or threat hunting queries for this domain
- When SOC analysts need structured procedures for this analysis type
- When validating security monitoring coverage for related attack techniques

## Detection Gaps & Validation

- **NOP sleds are rarely just `0x90`.** Real sprays use `0x0c0c0c0c` (doubles as a benign `OR` and a heap address), polymorphic sleds of valid single-byte instructions, or JIT-sprayed code, so a scan for `\x90` runs misses them. Search for repeated 4-byte address patterns and large identical-page runs, not only classic sleds.
- **`malfind` keys on RWX, which modern exploits avoid.** With DEP/ASLR, payloads often land in RW (then ROP flips protections), so `windows.malfind` shows nothing. Cross-check `windows.vadinfo` for abnormally large contiguous private allocations regardless of the execute bit.
- **Wrong process / wrong layer.** Browser sprays live in renderer/child processes and plugin hosts (`iexplore.exe`, `WerFault`, Flash/Java), not the parent; pick the exploited process.
- **Confirm a hit:** dump the suspect VAD region (`vol3 windows.vadinfo --dump` / `windows.memmap`), then disassemble and run it through `scdbg`/libemu or capa to prove it is executable shellcode rather than data, and correlate with the triggering document/exploit.
- **False positives:** JIT engines (V8, SpiderMonkey, .NET, JVM), GPU/graphics buffers, and media decoders legitimately create large RWX/contiguous high-entropy allocations. Confirm decodable shellcode before calling a large allocation a spray.

## Prerequisites

- Python 3.9+ with `volatility3` framework installed
- Memory dump file (.raw, .vmem, .dmp format)
- Understanding of virtual memory layout and VAD (Virtual Address Descriptor) trees
- Familiarity with common shellcode patterns and NOP sled encodings

## Steps

### Step 1: Identify Suspicious Processes
Use Volatility3 windows.malfind to scan for processes with executable injected memory regions.

### Step 2: Analyze VAD Entries
Examine VAD tree entries using windows.vadinfo for large contiguous allocations with RWX permissions.

### Step 3: Scan for NOP Sled Patterns
Search suspicious memory regions for NOP sled signatures (0x90 sequences, 0x0c0c0c0c patterns).

### Step 4: Extract and Analyze Shellcode
Dump suspicious memory regions and identify shellcode using byte pattern analysis.

## Expected Output

JSON report with suspicious processes, heap spray indicators, NOP sled locations, memory region sizes, and extracted shellcode hashes.