Ir al contenido

Volatility 3: Windows Commands (Full List with Examples)

Note: We don't need a profile. Example base: sudo docker run --rm -v $PWD:/dumps:ro vol3 -f /dumps/Snapshot19.vmem

0views

Note: No profile needed. Example base: sudo docker run --rm -v $PWD:/dumps:ro vol3 -f /dumps/Snapshot19.vmem

  • Description: System information.
  • Example: sudo docker run --rm -v $PWD:/dumps:ro vol3 -f /dumps/Snapshot19.vmem windows.info
  • Why: To identify the Windows version and architecture.
  • Description: List of active processes.
  • Example: sudo docker run --rm -v $PWD:/dumps:ro vol3 -f /dumps/Snapshot19.vmem windows.pslist
  • Why: Basic listing to identify running programs.
  • Description: Scans processes (hidden).
  • Example: sudo docker run --rm -v $PWD:/dumps:ro vol3 -f /dumps/Snapshot19.vmem windows.psscan
  • Why: To find processes that hide from the official list.
  • Description: Process tree.
  • Example: sudo docker run --rm -v $PWD:/dumps:ro vol3 -f /dumps/Snapshot19.vmem windows.pstree
  • Why: To see anomalous parent-child relationships.
  • Description: Command arguments.
  • Example: sudo docker run --rm -v $PWD:/dumps:ro vol3 -f /dumps/Snapshot19.vmem windows.cmdline
  • Why: To see how a process has been executed (for example, encoded PowerShell).
  • Description: Process users.
  • Example: sudo docker run --rm -v $PWD:/dumps:ro vol3 -f /dumps/Snapshot19.vmem windows.getsids
  • Why: To know which user launched the process.
  • Description: Detects code injections.
  • Example: sudo docker run --rm -v $PWD:/dumps:ro vol3 -f /dumps/Snapshot19.vmem windows.malfind
  • Why: To find malicious code running in memory (Shellcode).
  • Description: VAD information.
  • Example: sudo docker run --rm -v $PWD:/dumps:ro vol3 -f /dumps/Snapshot19.vmem windows.vadinfo
  • Why: To manually investigate suspicious memory regions.
  • Description: Scans with Yara.
  • Example: sudo docker run --rm -v $PWD:/dumps:ro vol3 -f /dumps/Snapshot19.vmem yarascan --yara-rules "detect_malware"
  • Why: To search for known malware patterns.
  • Description: List DLLs.
  • Example: sudo docker run --rm -v $PWD:/dumps:ro vol3 -f /dumps/Snapshot19.vmem windows.dlllist
  • Why: To see which libraries a process uses.
  • Description: Detects unlinked DLLs.
  • Example: sudo docker run --rm -v $PWD:/dumps:ro vol3 -f /dumps/Snapshot19.vmem windows.ldrmodules
  • Why: To find hidden DLLs (stealth injections).
  • Description: Scans drivers.
  • Example: sudo docker run --rm -v $PWD:/dumps:ro vol3 -f /dumps/Snapshot19.vmem windows.driverscan
  • Why: To detect Rootkits installed as drivers.
  • Description: Scans network.
  • Example: sudo docker run --rm -v $PWD:/dumps:ro vol3 -f /dumps/Snapshot19.vmem windows.netscan
  • Why: To see active connections and open ports.
  • Description: Network status.
  • Example: sudo docker run --rm -v $PWD:/dumps:ro vol3 -f /dumps/Snapshot19.vmem windows.netstat
  • Why: Another view of network structures.
  • Description: We scan files.
  • Example: sudo docker run --rm -v $PWD:/dumps:ro vol3 -f /dumps/Snapshot19.vmem windows.filescan
  • Why: To find files open in memory.
  • Description: We extract files.
  • Example: sudo docker run --rm -v $PWD:/dumps:ro vol3 -f /dumps/Snapshot19.vmem windows.dumpfiles --virtaddr 0x...
  • Why: To recover a suspicious file for analysis.
  • Description: We list keys.
  • Example: sudo docker run --rm -v $PWD:/dumps:ro vol3 -f /dumps/Snapshot19.vmem windows.registry.hivelist
  • Why: To locate the registry in memory.
  • Description: We print keys.
  • Example: sudo docker run --rm -v $PWD:/dumps:ro vol3 -f /dumps/Snapshot19.vmem windows.registry.printkey --key "Software\Microsoft\Windows\CurrentVersion\Run"
  • Why: To check registry persistence.
  • Description: Extracting hashes.
  • Example: sudo docker run --rm -v $PWD:/dumps:ro vol3 -f /dumps/Snapshot19.vmem windows.registry.hashdump
  • Why: To obtain passwords.
  • Description: We scan services.
  • Example: sudo docker run --rm -v $PWD:/dumps:ro vol3 -f /dumps/Snapshot19.vmem windows.svcscan
  • Why: To view malicious services.
  • Description: Kernel callbacks.
  • Example: sudo docker run --rm -v $PWD:/dumps:ro vol3 -f /dumps/Snapshot19.vmem windows.callbacks
  • Why: To detect advanced persistence mechanisms.
  • Description: Syscall table.
  • Example: sudo docker run --rm -v $PWD:/dumps:ro vol3 -f /dumps/Snapshot19.vmem windows.ssdt
  • Why: To detect kernel hooking (Rootkits).
  • Description: Kernel timers.
  • Example: sudo docker run --rm -v $PWD:/dumps:ro vol3 -f /dumps/Snapshot19.vmem windows.timers
  • Why: Some malware uses timers to reactivate periodically.
  • Description: We list threads.
  • Example: sudo docker run --rm -v $PWD:/dumps:ro vol3 -f /dumps/Snapshot19.vmem windows.threads
  • Why: For granular analysis of execution within processes.
  • Description: We scan Mutexes.
  • Example: sudo docker run --rm -v $PWD:/dumps:ro vol3 -f /dumps/Snapshot19.vmem windows.mutantscan
  • Why: To find indicators of compromise (many malware use unique Mutexes to avoid running twice).
  • Description: We detect name spoofing.
  • Example: sudo docker run --rm -v $PWD:/dumps:ro vol3 -f /dumps/Snapshot19.vmem windows.malware.pebmasquerade
  • Why: To see if a process is lying about its name.

windows.malware.processghosting.ProcessGhosting

Sección titulada «windows.malware.processghosting.ProcessGhosting»
  • Description: We detect Process Ghosting.
  • Example: sudo docker run --rm -v $PWD:/dumps:ro vol3 -f /dumps/Snapshot19.vmem windows.malware.processghosting
  • Why: Advanced technique to execute malware deleted from the disk.

windows.malware.hollowprocesses.HollowProcesses

Sección titulada «windows.malware.hollowprocesses.HollowProcesses»
  • Description: We detect Process Hollowing.
  • Example: sudo docker run --rm -v $PWD:/dumps:ro vol3 -f /dumps/Snapshot19.vmem windows.malware.hollowprocesses
  • Why: A very common technique in which malware empties a legitimate process and places itself inside.