A high-speed memory forensics tool for analyzing physical memory dumps to find/extract processes and hypervisors using virtual machine introspection.
inVtero.net is a high-speed memory forensics tool that analyzes physical memory dumps to extract processes and hypervisors using Virtual Machine Introspection (VMI). It solves the problem of forensic analysis in multi-gigabyte memory snapshots by operating independently of OS structures and microarchitecture, enabling reliable detection even in manipulated environments.
Digital forensics analysts, security researchers, and incident responders who need to inspect physical memory dumps for malware, hypervisors, or process extraction across various platforms.
Developers choose inVtero.net for its high-speed processing (Gbps), OS-agnostic analysis using VMI techniques, and ability to handle nested hypervisors without relying on easily manipulated OS structures.
inVtero.net: A high speed (Gbps) Forensics, Memory integrity & assurance. Includes offensive & defensive memory capabilities. Find/Extract processes, hypervisors (including nested) in memory dumps using microarchitechture independent Virtual Machiene Introspection techniques
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Uses multi-core optimization to achieve multi-gigabyte per second analysis rates, with example runs in the README showing speeds over 300 MB/s on a laptop.
Employs self-pointer and recursive page directory techniques to identify processes without OS dependencies, ensuring reliability against manipulation, as emphasized in the philosophy.
Works with Windows, Linux, BSD, and hypervisor formats like VMWARE and XEN, enabling broad forensic analysis across diverse environments.
Integrates DLR for dynamic scripting, allowing custom forensic workflows via Python, exemplified by the analyze.py script in the README.
Admits to being in alpha with limitations, such as initial bugs in dumping user-space memory from guest VMs and incomplete features, per the 'Bugs' section.
Requires manual registration of msdia140.dll on Windows, adding an error-prone step that complicates deployment, as highlighted in the IMPORTANT note.
For unknown VMCS mappings, it may resort to brute-forcing possible values, which, while fast, can be less precise and rely on trial-and-error, as mentioned in the 'Speed' section.