#x86-64 #injection #reverse-engineering #process #windows

ntprocesses

Rust library that makes it easy to manipulate Windows' processes

5 releases

new 0.1.4 Apr 9, 2025
0.1.3 Apr 9, 2025
0.1.2 Apr 5, 2025
0.1.1 Apr 5, 2025
0.1.0 Apr 4, 2025

#97 in Windows APIs

Download history 240/week @ 2025-03-30 365/week @ 2025-04-06

605 downloads per month

MIT license

57KB
1K SLoC

ntprocesses

About

Rust library that makes it easy to manipulate Windows' processes. The name comes from the ability to specifically target processes found with the undocumented NtAPI, and use of NtAPI functions. You can use officially supported APIs just as well, too.

Usage

[dependencies]
ntprocesses = "*"

- or -

$ git clone https://github.com/item-self/ntprocesses.git
$ cd ntprocesses
$ cargo test

Examples

Getting a process using a snapshot:

let process = ProcessBuilder::<Attach>::default()
    .permissions(PROCESS_ALL_ACCESS)
    .process_id(process_id)
    .build_from_snapshot()?;

Getting a process using the NtAPI:

let process = ProcessBuilder::<Attach>::default()
    .permissions(PROCESS_ALL_ACCESS)
    .process_id(process_id)
    .build_from_nt()?;

Basic memory operations on a process:

// this will actually allocate an entire page, read only.
let addr = process.virtual_alloc(None, 1, PAGE_READONLY)?;

// this will set the page to be able to be read and written to.
process.set_protection(addr, 1, PAGE_READWRITE)?;

process.write(addr, 1337 as usize)?;

assert_eq!(process.read::<usize>(addr)?, 1337 as usize);

Iterate through process threads with undocumented flags:

let process = Process::<NT>::from_pid(process_id, PROCESS_ALL_ACCESS)?;

for thread process.get_threads() {
    thread.suspend()?;
    println!("{:?}", thread.thread_state);
}

Thread hijacking made easy with these methods!

let thread = process.get_threads().next().unwrap();

thread.suspend()
thread.get_context()
thread.set_context()
thread.resume()
// etc ...

And, many more examples in the test modules.

Dependencies

~116MB
~2M SLoC