Crates.io | physpatch |
lib.rs | physpatch |
version | 0.2.1 |
source | src |
created_at | 2023-04-30 22:50:15.675913 |
updated_at | 2024-11-10 11:47:30.856368 |
description | PhysPatch performs physical memory scans and patches of the entire Windows kernel |
homepage | https://github.com/sonodima/physpatch |
repository | https://github.com/sonodima/physpatch |
max_upload_size | |
id | 853053 |
size | 77,474 |
PhysPatch performs physical memory scans and patches of the entire Windows kernel.
Scan for "488b??????????48" in the virtual machine named "TargetVM" and write "488b0000" to all matches:
physpatch -t "TargetVM" -p "488b0000" -- "488b??????????48"
Scan for "488b?????48" in the first virtual machine found, without performing any patching:
physpatch -- "488b?????48"
See physpatch --help
for all the available arguments and their descriptions.
Using Cargo is the easiest way to get started with PhysPatch:
cargo install physpatch
sudo setcap "CAP_SYS_PTRACE=ep" $(which physpatch)
You can now launch the program with the physpatch
command.
git clone https://github.com/sonodima/physpatch && cd physpatch
cargo build --release
sudo setcap "CAP_SYS_PTRACE=ep" target/release/physpatch
The compiled binary is located in target/release/physpatch
CAP_SYS_PTRACE is required to use this program without elevation:
sudo setcap "CAP_SYS_PTRACE=ep" physpatch
For more information, refer to the documentation for memflow_qemu
PhysPatch is an extremely powerful tool, and incorrect usage can (will) lead to unintended consequences, including system crashes and data corruption.
Before using PhysPatch, ensure you fully understand its implications and effects. Proper knowledge of the memory structures and patterns you are searching for is essential.
Those associated with PhysPatch will not be held accountable for any damages, data losses, or system corruptions that arise from the usage of this tool.
This project is heavily inspired by Hygieia, which is a scanning tool to find traces of vulnerable drivers.