Ir al contenido

Volatility 3: Linux Commands with examples

Note: Installed symbol tables. Example base: sudo docker run --rm -v $PWD:/dumps:ro vol3 -f /dumps/Snapshot19.vmem

0views

Note: Symbol tables installed. Example base: sudo docker run --rm -v $PWD:/dumps:ro vol3 -f /dumps/Snapshot19.vmem

  • Description: Listing active processes.
  • Example: sudo docker run --rm -v $PWD:/dumps:ro vol3 -f /dumps/Snapshot19.vmem linux.pslist
  • Why: To get an overview of what was running.
  • Description: Process tree.
  • Example: sudo docker run --rm -v $PWD:/dumps:ro vol3 -f /dumps/Snapshot19.vmem linux.pstree
  • Why: To see inheritance relationships and suspicious processes.
  • Description: Scanning memory for processes.
  • Example: sudo docker run --rm -v $PWD:/dumps:ro vol3 -f /dumps/Snapshot19.vmem linux.psscan
  • Why: To detect Rootkits that unlink processes from the list.
  • Description: Processes with arguments.
  • Example: sudo docker run --rm -v $PWD:/dumps:ro vol3 -f /dumps/Snapshot19.vmem linux.psaux
  • Why: To see how a process was launched (e.g.: nc -e /bin/bash).
  • Description: Call stack.
  • Example: sudo docker run --rm -v $PWD:/dumps:ro vol3 -f /dumps/Snapshot19.vmem linux.pscallstack
  • Why: To see what a function locked to the kernel is executing.
  • Description: Processes via hash table.
  • Example: sudo docker run --rm -v $PWD:/dumps:ro vol3 -f /dumps/Snapshot19.vmem linux.pidhashtable
  • Why: Alternative technique to find hidden processes.
  • Description: Network connections and sockets.
  • Example: sudo docker run --rm -v $PWD:/dumps:ro vol3 -f /dumps/Snapshot19.vmem linux.sockstat
  • Why: To identify communications with C2 servers.
  • Description: IP addresses.
  • Example: sudo docker run --rm -v $PWD:/dumps:ro vol3 -f /dumps/Snapshot19.vmem linux.ip.Addr
  • Why: To know which IP the machine had at the time of capture.
  • Description: Layer 2 information.
  • Example: sudo docker run --rm -v $PWD:/dumps:ro vol3 -f /dumps/Snapshot19.vmem linux.ip.Link
  • Why: To identify the MAC or promiscuous mode.
  • Description: Firewall hooks.
  • Example: sudo docker run --rm -v $PWD:/dumps:ro vol3 -f /dumps/Snapshot19.vmem linux.netfilter.Netfilter
  • Why: To see if the firewall rules have been modified.

We will run these commands to analyze the processes and the network on the Linux operating system using Volatility 3. We must run each command to obtain the necessary information. We will use the provided examples to get an overview of active processes, network connections, and IP addresses. We will also use these tools to detect potential Rootkits and modify firewall rules.

  • Description: Command history.
  • Example: sudo docker run --rm -v $PWD:/dumps:ro vol3 -f /dumps/Snapshot19.vmem linux.bash
  • Why: Critical. Shows what the attacker has typed.
  • Description: Open files.
  • Example: sudo docker run --rm -v $PWD:/dumps:ro vol3 -f /dumps/Snapshot19.vmem linux.lsof
  • Why: To see which files a malicious process is reading.
  • Description: Kernel modules.
  • Example: sudo docker run --rm -v $PWD:/dumps:ro vol3 -f /dumps/Snapshot19.vmem linux.lsmod
  • Why: To see if there are Rootkits loaded as modules.
  • Description: Mount points.
  • Example: sudo docker run --rm -v $PWD:/dumps:ro vol3 -f /dumps/Snapshot19.vmem linux.mountinfo
  • Why: To view mounted external devices.
  • Description: Kernel messages.
  • Example: sudo docker run --rm -v $PWD:/dumps:ro vol3 -f /dumps/Snapshot19.vmem linux.dmesg
  • Why: May contain malware errors during loading.
  • Description: Active log buffer.
  • Example: sudo docker run --rm -v $PWD:/dumps:ro vol3 -f /dumps/Snapshot19.vmem linux.kmsg
  • Why: OS or driver alerts.
  • Description: Mapped ELF binaries.
  • Example: sudo docker run --rm -v $PWD:/dumps:ro vol3 -f /dumps/Snapshot19.vmem linux.elfs
  • Why: To identify fileless executables.
  • Description: Memory maps.
  • Example: sudo docker run --rm -v $PWD:/dumps:ro vol3 -f /dumps/Snapshot19.vmem linux.proc.Maps
  • Why: To view assigned memory regions.
  • Description: Environment variables.
  • Example: sudo docker run --rm -v $PWD:/dumps:ro vol3 -f /dumps/Snapshot19.vmem linux.envars
  • Why: To view modifications to PATH or USER.
  • Description: I/O map.
  • Example: sudo docker run --rm -v $PWD:/dumps:ro vol3 -f /dumps/Snapshot19.vmem linux.iomem
  • Why: Low-level hardware information.
  • Description: Boot time.
  • Example: sudo docker run --rm -v $PWD:/dumps:ro vol3 -f /dumps/Snapshot19.vmem linux.boottime
  • Why: To establish a timeline.
  • Description: Kernel symbols.
  • Example: sudo docker run --rm -v $PWD:/dumps:ro vol3 -f /dumps/Snapshot19.vmem linux.kallsyms
  • Why: For advanced analysts needing function addresses.
  • Description: Kernel threads.
  • Example: sudo docker run --rm -v $PWD:/dumps:ro vol3 -f /dumps/Snapshot19.vmem linux.kthreads
  • Why: To detect suspicious kernel threads.
  • Description: Loaded libraries.
  • Example: sudo docker run --rm -v $PWD:/dumps:ro vol3 -f /dumps/Snapshot19.vmem linux.library_list
  • Why: To detect Library Injection.
  • Description: Files in cache memory.
  • Example: sudo docker run --rm -v $PWD:/dumps:ro vol3 -f /dumps/Snapshot19.vmem linux.pagecache.Files
  • Why: To view recently accessed files.
  • Description: Inode pages.
  • Example: sudo docker run --rm -v $PWD:/dumps:ro vol3 -f /dumps/Snapshot19.vmem linux.pagecache.InodePages
  • Why: Recover file fragments.
  • Description: Filesystem recovery.
  • Example: sudo docker run --rm -v $PWD:/dumps:ro vol3 -f /dumps/Snapshot19.vmem linux.pagecache.RecoverFs
  • Why: Recover files without disk access.
  • Description: Looking for injections.
  • Example: sudo docker run --rm -v $PWD:/dumps:ro vol3 -f /dumps/Snapshot19.vmem linux.malware.malfind.Malfind
  • Why: It is a primary tool for finding injected malicious code.
  • Description: We verify the network.
  • Example: sudo docker run --rm -v $PWD:/dumps:ro vol3 -f /dumps/Snapshot19.vmem linux.check_afinfo.Check_afinfo
  • Why: We detect network rootkits.
  • Description: We verify credentials.
  • Example: sudo docker run --rm -v $PWD:/dumps:ro vol3 -f /dumps/Snapshot19.vmem linux.check_creds.Check_creds
  • Why: We detect privilege escalation.
  • Description: Verifying IDT.
  • Example: sudo docker run --rm -v $PWD:/dumps:ro vol3 -f /dumps/Snapshot19.vmem linux.check_idt.Check_idt
  • Why: Detecting IDT Hooking (Legacy rootkits).
  • Description: Verifying modules.
  • Example: sudo docker run --rm -v $PWD:/dumps:ro vol3 -f /dumps/Snapshot19.vmem linux.check_modules.Check_modules
  • Why: Detecting hidden modules.
  • Description: We verify syscalls.
  • Example: sudo docker run --rm -v $PWD:/dumps:ro vol3 -f /dumps/Snapshot19.vmem linux.check_syscall.Check_syscall
  • Why: We detect if sys_read or sys_write have been modified.
  • Description: Hidden modules.
  • Example: sudo docker run --rm -v $PWD:/dumps:ro vol3 -f /dumps/Snapshot19.vmem linux.hidden_modules.Hidden_modules
  • Why: We recover hidden malicious modules.
  • Description: Keyboard notifiers.
  • Example: sudo docker run --rm -v $PWD:/dumps:ro vol3 -f /dumps/Snapshot19.vmem linux.keyboard_notifiers.Keyboard_notifiers
  • Why: We detect keyloggers at the kernel level.
  • Description: We verify TTY.
  • Example: sudo docker run --rm -v $PWD:/dumps:ro vol3 -f /dumps/Snapshot19.vmem linux.tty_check.tty_check
  • Why: We detect SSH session interception.
  • Description: eBPF programs.
  • Example: sudo docker run --rm -v $PWD:/dumps:ro vol3 -f /dumps/Snapshot19.vmem linux.ebpf.EBPF
  • Why: We detect modern malware (BPFDoor).
  • Description: We verify ftrace.
  • Example: sudo docker run --rm -v $PWD:/dumps:ro vol3 -f /dumps/Snapshot19.vmem linux.tracing.ftrace.CheckFtrace
  • Why: We check if malware uses ftrace to intercept functions.
  • Description: We verify tracepoints.
  • Example: sudo docker run --rm -v $PWD:/dumps:ro vol3 -f /dumps/Snapshot19.vmem linux.tracing.tracepoints.CheckTracepoints
  • Why: We intercept system execution.
  • Description: Yara in VMA.
  • Example: sudo docker run --rm -v $PWD:/dumps:ro vol3 -f /dumps/Snapshot19.vmem linux.vmayarascan.VmaYaraScan --yara-file reglas.yara
  • Why: We look for specific patterns within the memory of the processes.