Ir al contenido

Volatility 2 Index: Information, Processes, and Network

This document collects basic commands to begin analysis and investigate system status and connections.

0views

This document compiles the basic commands to begin analysis and investigate system status and connections.

Description: We will analyze the memory image to identify the operating system, Service Pack version, and hardware architecture. This is the first mandatory step in Volatility 2.

What it's for: To obtain the profile (--profile) that we need for the rest of the commands. It also shows the date and time of the capture.

Example:

Ventana de terminal
sudo docker run --rm -v $PWD:/dumps:ro vol2 -f /dumps/victim.raw imageinfo

Description: We will list all processes running on the system by following the kernel's doubly linked list EPROCESS.

What it's for: To have an overview of what was running. Shows the PID, PPID (parent), and start time.

Example:

Ventana de terminal
sudo docker run --rm -v $PWD:/dumps:ro vol2 -f /dumps/victim.raw --profile=Win7SP1x64 pslist

Description: We will show processes in a visual tree format, demonstrating the parent-child relationship.

What it's for: Very useful for detecting anomalies, such as a svchost.exe that does not hang from services.exe or a cmd.exe executed by a web browser (possible exploit).

Example:

Ventana de terminal
sudo docker run --rm -v $PWD:/dumps:ro vol2 -f /dumps/victim.raw --profile=Win7SP1x64 pstree

Description: We compare the list of found processes using different methods (pslist, psscan, thrdproc, etc.).

What it's for: To find hidden processes (Rootkits). If a process appears as False in the pslist column but True in psscan, it is likely hiding.

Example:

Ventana de terminal
sudo docker run --rm -v $PWD:/dumps:ro vol2 -f /dumps/victim.raw --profile=Win7SP1x64 psxview

Description: We will show the command-line arguments used to launch each process.

What it's for: Vital to see if malware has been executed with specific parameters, or to see which files a legitimate program was opening.

Example:

Ventana de terminal
sudo docker run --rm -v $PWD:/dumps:ro vol2 -f /dumps/victim.raw --profile=Win7SP1x64 cmdline

Description: We will scan active, listening, or closed network connections. (Available for Windows Vista, 7 and higher).

What it's for: To find communications with malicious IPs (C2), suspicious open ports, or malware listening for incoming connections.

Example:

Ventana de terminal
sudo docker run --rm -v $PWD:/dumps:ro vol2 -f /dumps/victim.raw --profile=Win7SP1x64 netscan

Description: Equivalent to netscan but for older systems (Windows XP / 2003). We will look for _TCPT_OBJECT structures.

Purpose: Similar to netscan, but limited to active or recently closed TCP connections in legacy systems.

Example:

Ventana de terminal
sudo docker run --rm -v $PWD:/dumps:ro vol2 -f /dumps/victim.raw --profile=WinXPSP2x86 connscan

Description: We will list open sockets (Windows XP / 2003).

Purpose: To see which ports are open and which protocol (TCP/UDP) they use in legacy systems.

Example:

Ventana de terminal
sudo docker run --rm -v $PWD:/dumps:ro vol2 -f /dumps/victim.raw --profile=WinXPSP2x86 sockets