memory-frnscs-vltlty

Performs memory forensics analysis using Volatility 3 to extract evidence of malware execution, process injection, network connections, and credential theft from RAM dumps captured during incident response. Covers memory acquisition, process analysis, DLL inspection, and malware detection. Activates for requests involving memory forensics, RAM analysis, Volatility framework, memory dump investigation, volatile evidence analysis, or live memory acquisition.

Ir para a instalação

Repositório: Undermybelt/hermes-skills
Última atividade na origem: 7 de junho de 2026 às 07:23
Idioma detectado do SKILL.md: inglês
Estrelas: 6
Forks: 1

Opções de instalação

Por padrão, está selecionado o prompt que primeiro revisa a origem. Você pode mudar para um comando direto ou baixar uma cópia local.

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.

npx skills add https://github.com/Undermybelt/hermes-skills --skill memory-frnscs-vltlty

O comando permanece em uma só linha. Role horizontalmente para revisá-lo antes de copiar.

Prefere uma cópia local? Baixe os arquivos disponíveis atualmente no SkillsMP.

Revise os arquivos de origem

Leia o SKILL.md e os arquivos complementares exibidos pelo SkillsMP antes de decidir se vai instalar.

Explorador de arquivos

4 arquivos

SKILL.md

Instruções da origem · Visualização somente leitura

Voltar à pesquisa Voltar à instalação

anti-entropy-governance

Use when retiring old logic, collapsing duplicate owners, removing fallbacks, or touching schema, persistence, or source-of-truth boundaries while deciding whether to delete old paths, retain compatibility, or stop for confirmation.

2026-06-07

brainstorming

Use when defining new features, product behavior, UI/component design, architecture choices, contract changes, or ambiguous medium/high-complexity work before implementation.

2026-06-07

communicating-concisely

Use when the user asks for caveman mode, fewer tokens, brief responses, compressed communication, or otherwise explicitly requests a much shorter answer.

2026-06-07

Ver todas deste repositório

name	memory-frnscs-vltlty
description	Performs memory forensics analysis using Volatility 3 to extract evidence of malware execution, process injection, network connections, and credential theft from RAM dumps captured during incident response. Covers memory acquisition, process analysis, DLL inspection, and malware detection. Activates for requests involving memory forensics, RAM analysis, Volatility framework, memory dump investigation, volatile evidence analysis, or live memory acquisition.
domain	cybersecurity
subdomain	incident-response
tags	["memory-forensics","volatility","RAM-analysis","process-injection","DFIR"]
mitre_attack	["T1003","T1055","T1620","T1574"]
version	1.0.0
author	mahipal
license	Apache-2.0
nist_csf	["RS.MA-01","RS.MA-02","RS.AN-03","RC.RP-01"]

Conducting Memory Forensics with Volatility

When to Use

An endpoint has been contained during an active incident and volatile evidence must be preserved
EDR alerts suggest process injection or fileless malware that only exists in memory
Encryption keys need to be recovered from a ransomware-infected system before shutdown
Credential theft (Mimikatz, LSASS dumping) is suspected and evidence must be confirmed
A rootkit or kernel-level compromise is suspected and disk-based analysis is insufficient

Do not use for analyzing disk images or file system artifacts; use disk forensics tools (Autopsy, FTK) for those tasks.

Prerequisites

Memory acquisition tool deployed or available: WinPmem, Magnet RAM Capture, DumpIt, or AVML (Linux)
Volatility 3 installed with Python 3.8+ and required symbol tables
Sufficient storage for memory dumps (equal to system RAM size, typically 8-64 GB)
YARA rules for malware detection in memory (Florian Roth's signature-base, custom rules)
Reference baseline of normal processes and DLLs for the OS version being analyzed
Chain of custody documentation for evidence handling

Workflow

Step 1: Acquire Memory Image

Capture RAM from the target system using a forensically sound method:

Windows (WinPmem):

winpmem_mini_x64.exe output.raw

Windows (Magnet RAM Capture):

MagnetRAMCapture.exe
# GUI-based, select output path, generates .raw file

Windows (DumpIt):

DumpIt.exe
# Creates memory dump in current directory automatically

Linux (AVML - Acquire Volatile Memory for Linux):

./avml output.lime

Document acquisition metadata:

Acquisition Record:
━━━━━━━━━━━━━━━━━
Target Host:      WKSTN-042
RAM Size:         16 GB
Dump File:        WKSTN-042_20251115_1445.raw
Dump Size:        16,843,612,160 bytes
SHA-256:          a4b3c2d1e5f6...
Acquisition Tool: WinPmem 4.0
Acquired By:      [Analyst Name]
Timestamp:        2025-11-15T14:45:00Z

Step 2: Identify the Operating System and Profile

Volatility 3 automatically identifies the OS, but verify:

# Get system information
vol -f WKSTN-042_20251115_1445.raw windows.info

# Output includes:
# OS: Windows 10 22H2 (Build 19045.3693)

Term	Definition
Volatile Evidence	Data that exists only in RAM and is lost when a system is powered off; includes running processes, network connections, encryption keys
Process Injection	Technique where malware inserts code into a legitimate process's memory space to evade detection (malfind detects this)
EPROCESS	Windows kernel data structure representing a process; psscan searches for these structures even when unlinked from the active process list
VAD (Virtual Address Descriptor)	Windows kernel structure tracking memory regions allocated to a process; malfind examines VADs for executable but non-file-backed regions
Symbol Tables	OS-specific data structures that Volatility 3 uses to parse memory; downloaded automatically based on detected OS version
PAGE_EXECUTE_READWRITE	Memory protection flag indicating a region is readable, writable, and executable; common indicator of injected malicious code
Memory-Resident Malware	Malware that operates entirely in RAM without writing persistent files to disk, making it invisible to traditional disk-based antivirus

memory-frnscs-vltlty

Opções de instalação

Revise os arquivos de origem

Conducting Memory Forensics with Volatility

When to Use

Prerequisites

Workflow

Step 1: Acquire Memory Image

Step 2: Identify the Operating System and Profile

Conducting Memory Forensics with Volatility

When to Use

Prerequisites

Workflow

Step 1: Acquire Memory Image

Step 2: Identify the Operating System and Profile

Step 3: Analyze Running Processes

Step 4: Investigate Network Connections

Step 5: Detect Process Injection and Malware

Step 6: Extract Credentials and Artifacts

Step 7: Generate Forensic Report

Key Concepts

Tools & Systems

Common Scenarios

Scenario: Detecting Cobalt Strike Beacon in Memory

Output Format

memory-frnscs-vltlty

Informações da origem

Opções de instalação

Revise os arquivos de origem

Mais deste repositório

Mais deste repositório

Conducting Memory Forensics with Volatility

When to Use

Prerequisites

Workflow

Step 1: Acquire Memory Image

Step 2: Identify the Operating System and Profile

Conducting Memory Forensics with Volatility

When to Use

Prerequisites

Workflow

Step 1: Acquire Memory Image

Step 2: Identify the Operating System and Profile

Step 3: Analyze Running Processes

Step 4: Investigate Network Connections

Step 5: Detect Process Injection and Malware

Step 6: Extract Credentials and Artifacts

Step 7: Generate Forensic Report

Key Concepts

Tools & Systems

Common Scenarios

Scenario: Detecting Cobalt Strike Beacon in Memory

Output Format