Ir al contenido

Volatility 2: Linux Commands with Examples

Note: --profile=Linux... is mandatory. Example base: sudo docker run --rm -v $PWD:/dumps:ro vol2 -f /dumps/victim.raw --profile=LinuxUbuntu_x64

0views

Note: --profile=Linux... is mandatory. Example base: sudo docker run --rm -v $PWD:/dumps:ro vol2 -f /dumps/victim.raw --profile=LinuxUbuntu_x64

  • Description: We list processes.
  • Example: sudo docker run --rm -v $PWD:/dumps:ro vol2 -f /dumps/victim.raw --profile=LinuxUbuntu_x64 linux_pslist
  • Why: Basic view of active processes.
  • Description: Process tree.
  • Example: sudo docker run --rm -v $PWD:/dumps:ro vol2 -f /dumps/victim.raw --profile=LinuxUbuntu_x64 linux_pstree
  • Why: We see parent-child relationships.
  • Description: Processes with arguments.
  • Example: sudo docker run --rm -v $PWD:/dumps:ro vol2 -f /dumps/victim.raw --profile=LinuxUbuntu_x64 linux_psaux
  • Why: We see full execution commands (malicious arguments).
  • Description: We scan processes (hidden).
  • Example: sudo docker run --rm -v $PWD:/dumps:ro vol2 -f /dumps/victim.raw --profile=LinuxUbuntu_x64 linux_psscan
  • Why: We find Rootkits that hide processes.
  • Description: Network connections.
  • Example: sudo docker run --rm -v $PWD:/dumps:ro vol2 -f /dumps/victim.raw --profile=LinuxUbuntu_x64 linux_netstat
  • Why: We detect C2 IPs and open ports.
  • Description: ARP table.
  • Example: sudo docker run --rm -v $PWD:/dumps:ro vol2 -f /dumps/victim.raw --profile=LinuxUbuntu_x64 linux_arp
  • Why: We see who has communicated on the local network (MITM attacks).
  • Description: Network interfaces.
  • Example: sudo docker run --rm -v $PWD:/dumps:ro vol2 -f /dumps/victim.raw --profile=LinuxUbuntu_x64 linux_ifconfig
  • Why: We check if the card is in promiscuous mode (sniffing).
  • Description: Open files.
  • Example: sudo docker run --rm -v $PWD:/dumps:ro vol2 -f /dumps/victim.raw --profile=LinuxUbuntu_x64 linux_lsof
  • Why: We see which files the malware is accessing.
  • Description: Bash history.
  • Example: sudo docker run --rm -v $PWD:/dumps:ro vol2 -f /dumps/victim.raw --profile=LinuxUbuntu_x64 linux_bash
  • Why: We recover the attacker's commands.
  • Description: Kernel modules.
  • Example: sudo docker run --rm -v $PWD:/dumps:ro vol2 -f /dumps/victim.raw --profile=LinuxUbuntu_x64 linux_lsmod
  • Why: We see loaded modules (LKM Rootkits).
  • Description: Mount points.
  • Example: sudo docker run --rm -v $PWD:/dumps:ro vol2 -f /dumps/victim.raw --profile=LinuxUbuntu_x64 linux_mount
  • Why: We see if there are external devices mounted.
  • Description: Kernel logs.
  • Example: sudo docker run --rm -v $PWD:/dumps:ro vol2 -f /dumps/victim.raw --profile=LinuxUbuntu_x64 linux_dmesg
  • Why: We look for errors or malicious driver loading messages.
  • Description: Code injections.
  • Example: sudo docker run --rm -v $PWD:/dumps:ro vol2 -f /dumps/victim.raw --profile=LinuxUbuntu_x64 linux_malfind
  • Why: We will find executable code injected into processes.
  • Description: We will verify network protocols.
  • Example: sudo docker run --rm -v $PWD:/dumps:ro vol2 -f /dumps/victim.raw --profile=LinuxUbuntu_x64 linux_check_afinfo
  • Why: We will detect network traffic manipulation in the kernel.
  • Description: We will verify credentials.
  • Example: sudo docker run --rm -v $PWD:/dumps:ro vol2 -f /dumps/victim.raw --profile=LinuxUbuntu_x64 linux_check_creds
  • Why: We will detect anomalous privilege escalation.
  • Description: We will verify syscalls.
  • Example: sudo docker run --rm -v $PWD:/dumps:ro vol2 -f /dumps/victim.raw --profile=LinuxUbuntu_x64 linux_check_syscall
  • Why: We will detect Syscall Hooking (classic rootkits).
  • Description: We will look for hidden modules.
  • Example: sudo docker run --rm -v $PWD:/dumps:ro vol2 -f /dumps/victim.raw --profile=LinuxUbuntu_x64 linux_hidden_modules
  • Why: We will find rootkits that have hidden themselves from lsmod.