#pid #ram #process #inspector #pointers #firefox #length #race #proc-maps #memory-region


A library for the arbitrary inspection and manipulation of the memory and code of a process on a Linux system

19 releases (6 breaking)

new 0.7.3 Sep 27, 2023
0.7.2 Sep 26, 2023
0.6.3 Sep 25, 2023
0.5.2 Sep 20, 2023
0.1.0 Aug 21, 2023
Download history 46/week @ 2023-08-16 55/week @ 2023-08-23 8/week @ 2023-08-30 35/week @ 2023-09-06 39/week @ 2023-09-13 221/week @ 2023-09-20

303 downloads per month

GPL-3.0 license

523 lines


raminspect is a crate that allows for the inspection and manipulation of the memory and code of a running process on a Linux system. It provides functions for finding and replacing search terms in a processes' memory, functions for allocating new memory belonging to the process, and an interface that allows for the injection of arbitrary shellcode running in the processes' context. All of this requires root privileges, for obvious reasons.

Demonstration of Functionality


Running an Example

You should be able to run the firefox_search example if you have Firefox installed. To do so, start by opening an instance of Firefox and typing "Old search text" in the search bar. If all goes well, when you run the example as root using the command sudo cargo run --example firefox_search --release, it should be replaced with "New search text", although you will probably have to click on the search bar again in order for it to render the new text.

A Note about Memory Allocation and Shellcode Injection

The find and replace functionality is available with or without the kernel module, but if you want to inject shellcode or allocate new buffers you must build and load the prerequisite kernel module first. You can do this by installing your distros' kernel headers package, performing a git clone and then running the following commands in the kern_module subfolder of the repository (if the build fails for some reason please file an issue):

make all
sudo insmod raminspect.ko

Also note that the shellcode injection part is currently designed to work on any architecture (even though the actual shellcode itself has to be platform-specific), but the arbitrary memory allocation part is currently limited to x86-64. PRs to add support for arbitrary allocation on more CPU architectures are welcome.