CYBERSECURITYTRACKER
Permanent story citation

Hunting In Memory

This page keeps the story as Cybersecurity Tracker first published it. If the tracker later corrects it, the correction appears below the original and never replaces it.

Back to newsStory 5197

As cited

Copy frozen at (site build).

threat intel

Hunting In Memory

No summary had been written when this copy was frozen.

First seen by Cybersecurity Tracker

Source attribution

Correction

Correction recorded as of .

threat intel

Hunting In Memory

Memory resident malware techniques, which hide malicious code in process memory rather than on disk, have grown in popularity and accessibility among attackers of all sophistication levels over the past decade. Common techniques include shellcode injection, reflective DLL injection, memory module loading, process hollowing, module overwriting, and Gargoyle, each with distinct detection signatures such as unbacked executable memory sections or suspended processes. Threat hunters can identify these attacks by examining thread start addresses, memory permissions, and call stacks, with tools like Get-InjectedThreads providing low-noise detection across multiple technique categories.

Why it matters: Security operations and threat hunting teams need visibility into memory-based attacks because most endpoint products lack generic detection at scale, leaving a significant coverage gap; hunters should understand these common techniques and implement memory analysis methods to identify adversaries already resident on their networks.

Source published
First seen by Cybersecurity Tracker

Source attribution

Correction

Correction recorded as of .

threat intel

Hunting In Memory

Memory resident malware techniques, which hide malicious code in process memory rather than on disk, have grown in popularity and accessibility among attackers of all sophistication levels over the past decade. Common techniques include shellcode injection, reflective DLL injection, memory module loading, process hollowing, module overwriting, and Gargoyle, each with distinct detection signatures such as unbacked executable memory sections or suspended processes. Threat hunters can identify these attacks by examining thread start addresses, memory permissions, and call stacks, with tools like Get-InjectedThreads providing low-noise detection across multiple technique categories.

Why it matters: Security operations and threat hunting teams need visibility into memory-based attacks because most endpoint products lack generic detection at scale, leaving a significant coverage gap; hunters should understand these common techniques and implement memory analysis methods to identify adversaries already resident on their networks.

VendorsOracle
Source published
First seen by Cybersecurity Tracker

Source attribution

Glossary