During a live-response investigation on a compromised Ubuntu web server, analysts capture a memory image to examine suspicious behavior observed within a running process. The goal is to identify evidence of anomalous memory regions that may indicate unauthorized code execution within the address space of a specific process. How should investigators use Volatility to locate this type of memory anomaly?
Correct Answer: D
The correct answer is D because malfind is the Volatility plugin specifically intended to locate suspicious memory regions that may contain injected or otherwise unauthorized executable content inside a process address space. Volatility documentation describes malfind as a way to identify hidden or injected code by examining memory protections and suspicious VAD or mapped regions, which is exactly the forensic goal in the question. linux.pslist can enumerate processes, linux.lsof lists open files, and linux.mount shows mount information, but none of those plugins is designed to identify anomalous executable memory regions. CHFI v11 includes Linux memory forensics and malware behavior analysis, so candidates are expected to select the analysis method that directly matches the target artifact. In memory forensics, code injection or unauthorized execution often leaves traces in regions with unusual permissions or content patterns, and malfind is built to surface those anomalies for further review. Because the investigators want to find suspicious in-process memory areas that may reveal unauthorized code execution, the correct Volatility choice is linux.malfind.