pool_party_rs
is a cutting-edge remote process injection tool designed for cybersecurity research and penetration testing.
It leverages advanced techniques described in SafeBreach’s blog on Windows thread pool abuse and is inspired by the PoolParty project on GitHub.
This tool currently implements the first two variants of the PoolParty process injection techniques, with plans to expand its capabilities in the future.
How pool_party_rs
Works
The tool utilizes Windows Thread Pool mechanisms to inject malicious code into target processes. Here’s a breakdown of its operation:
Variant 1: Worker Factory Start Routine Overwrite
- Obtain Target Process Handle: The tool uses
OpenProcess
to gain access to the target process. - Identify Worker Factory Handle: It enumerates all handles in the target process using
NtQueryInformationProcess
and checks each handle type withNtQueryObject
to locate a “TpWorkerFactory” handle. - Retrieve Start Routine Address: Using
NtQueryInformationWorkerFactory
, it extracts the start routine address of the worker factory. - Inject Shellcode: The start routine address is overwritten with malicious shellcode using
WriteProcessMemory
. - Trigger Execution: The tool forces thread creation by calling
NtSetInformationWorkerFactory
, which executes the shellcode.
Variant 2: Task Queue Manipulation
This variant modifies the thread pool task queue by injecting a malicious task into it. When executed, this task runs the injected shellcode, effectively compromising the target process.
- OpenProcess: Accesses the target process.
- NtQueryInformationProcess: Enumerates handles in the process.
- DuplicateHandle: Duplicates handles for inspection.
- NtQueryObject: Identifies handle types.
- WriteProcessMemory: Writes shellcode to memory.
- NtSetInformationWorkerFactory: Triggers execution of injected code.
To integrate pool_party_rs
into your Rust project, add this dependency to your Cargo.toml
:
[dependencies]
pool_party_rs = { git = "https://github.com/Teach2Breach/pool_party_rs" }
use pool_party_rs::wrapper;
let info_string = wrapper(&SHELL_CODE, pid, variant);
println!("{}", info_string);
Run the proof-of-concept (PoC) with:
cargo run <pid> <variant>
The current version does not prioritize operational security (OPSEC) considerations like dynamic API resolution. However, an OPSEC-safe version will be released on a dedicated branch approximately one month after the initial release.
pool_party_rs
demonstrates innovative abuse of Windows thread pools for process injection, making it a valuable resource for cybersecurity professionals studying evasion techniques.
By exploiting legitimate system functionalities, it highlights gaps in modern detection systems and underscores the importance of continuous advancements in endpoint security solutions.