mirror of
https://github.com/HackTricks-wiki/hacktricks.git
synced 2025-10-10 18:36:50 +00:00
41 lines
1.4 KiB
Markdown
41 lines
1.4 KiB
Markdown
# Memory dump analysis
|
||
|
||
{{#include ../../../banners/hacktricks-training.md}}
|
||
|
||
## Start
|
||
|
||
Start **searching** for **malware** inside the pcap. Use the **tools** mentioned in [**Malware Analysis**](../malware-analysis.md).
|
||
|
||
## [Volatility](volatility-cheatsheet.md)
|
||
|
||
**Volatility is the main open-source framework for memory dump analysis**. This Python tool analyzes dumps from external sources or VMware VMs, identifying data like processes and passwords based on the dump's OS profile. It's extensible with plugins, making it highly versatile for forensic investigations.
|
||
|
||
[**Find here a cheatsheet**](volatility-cheatsheet.md)
|
||
|
||
## Mini dump crash report
|
||
|
||
When the dump is small (just some KB, maybe a few MB) then it's probably a mini dump crash report and not a memory dump.
|
||
|
||
.png>)
|
||
|
||
If you have Visual Studio installed, you can open this file and bind some basic information like process name, architecture, exception info and modules being executed:
|
||
|
||
.png>)
|
||
|
||
You can also load the exception and see the decompiled instructions
|
||
|
||
.png>)
|
||
|
||
.png>)
|
||
|
||
Anyway, Visual Studio isn't the best tool to perform an analysis of the depth of the dump.
|
||
|
||
You should **open** it using **IDA** or **Radare** to inspection it in **depth**.
|
||
|
||
|
||
|
||
{{#include ../../../banners/hacktricks-training.md}}
|
||
|
||
|
||
|