This library is meant to be created to test rust's capability for game hacking. u know it's kinda far from normal programming, right? However, cuz I was too lazy and beginner this library is relatively high level, meaning it doesnt use either Nt or Zw API, and it's only capable of things that a user-mode application does. Dont get it something fancy, rather consider this as my training of rust, can't guarantee the quality of the code. Oh, and never ever mention about the bizzar project structure, even if it looks bloody cringy. My bad.
But before actually test the example, I'll show you some preparation steps you're supposed to know.
Firstly, include toy-arms in your dependencies' table in Cargo.toml.
As of now toy-arms has 2 features which are internal and external.
internal feature flag is on by default so you have to specify external when you wanna use it.
for internal use:
[dependencies]
toy-arms = {git = "version = "https://github.com/vxcall/toy-arms"}
# This annotation below is to tell the compiler to compile this into dll. MUST.
[lib]
crate-type = ["cdylib"]for external use:
[dependencies]
toy-arms = {git = "https://github.com/vxcall/toy-arms", features = ["external"]}Secondly, sicne most of those tests are targeting the game "csgo.exe(x86)", you may have to build the code in x86 architecture depending on the example.
You can either specify in .cargo/config.toml as following:
[build]
target = "i686-pc-windows-msvc"Or put --target i686-pc-windows-msvc flag everytime when you build the code.
If you don't have toolchain for 32bit msvc, do following
rustup target add i686-pc-windows-msvc In this section I'll showcase you various examples for different situations with internal and external features. Find one fits your purpose.
Be informed that all these examples are happened to target CSGO:counter strike global offencive , so be sure to get it and test with it.
Welcome to the examples of internal hack. A dll file will be generated by build these examples, inject it with whatever dll injector you possess.
With this crate, making the injectable dll which is the smallest possible is simple as this:
cargo b --example in_simplest_dll --target i686-pc-windows-msvc
/*
This is the demonstration of how to make the simplest hack with toy-arms.
*/
// A neat macro which defines entry point instead of you.
// Also, you dont have to alloc/free console by yourself, console will show up when u compile into debug build.
internal::create_entrypoint!(hack_main_thread);
// Main thread
fn hack_main_thread() {
// YOUR STUNNING CODE'S SUPPOSED TO BE HERE;
for i in 0..30000 {
println!("using toy-arms {}", i);
}
}This is the code that overwrites the value at DW_FORCE_ATTACK to 0x5 every loop in csgo.exe.
Note that you have to check if the address of DW_FORCE_ATTACK is up-to-date.
cargo b --example in_auto_shoot --target i686-pc-windows-msvc
/*
This is the demonstration of how to use internal analysis feature in toy-arms.
This code gets module handle and function address of the func called MessageBoxA as an example.
Then read the value called dwForceAttack and overwrite it to make player shoot.
The offset DW_FORCE_ATTACK works as of the day i wrote this but it might not be up to date in your case.
*/
use toy_arms::internal::cast;
use toy_arms::utils::detect_keydown;
use toy_arms::utils::keyboard::{detect_keypress, VirtualKeyCode};
use internal::common::get_module_handle;
use winapi::shared::minwindef::HMODULE;
internal::create_entrypoint!(hack_main_thread);
// This offset has to be up to date.
const DW_FORCE_ATTACK: usize = 0x320BDE8;
fn hack_main_thread() {
let mut once = false;
// Gets module handle
let module_handle: HMODULE = get_module_handle("client.dll").unwrap();
println!("module handle = {:?}", module_handle as usize);
let shoot_flag = cast!(mut module_handle as usize + DW_FORCE_ATTACK, u8);
loop {
if !once {
println!("Press INSERT to exit...");
once = !once;
}
unsafe {
// Auto shoot
*shoot_flag = 5u8;
}
// To exit this hack loop when you input INSEERT KEY
if detect_keypress(VirtualKeyCode::VK_INSERT) {
break;
}
// just flexing this neat function xd.
if detect_keydown!(VirtualKeyCode::VK_HOME) {
println!("HOME is both pressed");
}
}
}While this code below will retrieve health value of LocalPlayer object in csgo.exe.
Note that you have to update the offset of DW_LOCAL_PLAYER.
cargo b --example in_get_localplayer_health --target i686-pc-windows-msvc
/*
This example is the demonstration of getting player health with toy-arms internal memory analysis feature.
Make sure that you inject this image to csgo.exe.
also, the offset of DW_LOCAL_PLAYER works as of the day i wrote this but it might not be up to date in your case.
*/
use internal::cast;
use internal::module::Module;
use internal::GameObject;
use toy_arms::derive::GameObject;
use utils::keyboard::VirtualKeyCode;
internal::create_entrypoint!(hack_main_thread);
// This macro provides from_raw() func that ensures the base address is not null.
#[derive(GameObject)]
struct LocalPlayer {
pointer: *const usize, // Denote the base address of LocalPlayer to use it later in get_health() function.
}
impl LocalPlayer {
unsafe fn get_health(&self) -> u16 {
*cast!(self.pointer as usize + 0x100, u16)
}
}
// This offset has to be up to date.
const DW_LOCAL_PLAYER: u32 = 0xDBF4BC;
fn hack_main_thread() {
let module = Module::from_name("client.dll").unwrap();
unsafe {
//let dw_local_player = memory.read_mut::<LocalPlayer>(0xDA244C);
loop {
if let Some(i) = LocalPlayer::from_raw(module.read(DW_LOCAL_PLAYER as usize)) {
println!("health = {:?}", (*i).get_health());
};
if toy_arms::utils::keyboard::detect_keypress(VirtualKeyCode::VK_INSERT) {
break;
}
}
}
}This is the pattern scanning example where the pattern is for dwForceAttack in csgo.
cargo b --example in_pattern_scan --target i686-pc-windows-msvc
/*
This is an example to demonstrate how to use powerful pattern scan feature in toy-arms.
Make sure you inject this image to csgo.exe.
The model pattern is for dwForceAttack.
*/
use internal::module::Module;
use toy_arms::utils::keyboard::{detect_keypress, VirtualKeyCode};
internal::create_entrypoint!(hack_main_thread);
const DW_FORCE_ATTACK_PATTERN: &str = "89 0D ? ? ? ? 8B 0D ? ? ? ? 8B F2 8B C1 83 CE 04";
fn hack_main_thread() {
let mut once = false;
let mut client = Module::from_name("client.dll").unwrap();
match client.find_pattern(DW_FORCE_ATTACK_PATTERN) {
Some(i) => println!("[+] *dwForceAttack address: 0x{:x}", i),
None => println!("[-] Pattern not found"),
}
match client.pattern_scan(DW_FORCE_ATTACK_PATTERN, 2, 0) {
Some(i) => println!("[+] dwForceAttack address: 0x{:x}", i),
None => println!("[-] Offset not found"),
}
loop {
if !once {
println!("[+] Press INSERT to exit...");
once = !once;
}
// To exit this hack loop when you input INSEERT KEY
if detect_keypress(VirtualKeyCode::VK_INSERT) {
break;
}
}
}On the other hand, following code is how tamper with memory externally is like.
This is the code that overwrites the value at DW_FORCE_ATTACK to 0x5 every loop in csgo.exe.
Note that you have to check if the address of DW_FORCE_ATTACK is up-to-date.
cargo r --example ex_auto_shoot --features external --no-default-features
/*
This is the demonstration of how to use external feature of toy-arms.
Following code is trying to get process id and process handle first, then getting a value called dwClientState_state.
Then showing the way to overwrite value at dwForceAttack to make player shoot.
The offset DW_CLIENT_STATE, DW_CLIENT_STATE_STATE and DW_FORCE_ATTACK work as of the day i wrote this but it might not be up to date in your case.
*/
use toy_arms::external::process::Process;
use toy_arms::external::{read, write};
use toy_arms::utils::keyboard::VirtualKeyCode;
fn main() {
// This const has to be up to date.
const DW_FORCE_ATTACK: u32 = 0x320BDE8;
// Getting process information
let process = Process::from_process_name("csgo.exe").unwrap();
println!(
"[+] process id: {}, \n[+] process handle: {:?}",
process.id, process.handle
);
// You can get module information by using get_module_info
let module_info = process.get_module_info("client.dll").unwrap();
println!("[+] module name: {}", module_info.name);
loop {
// write helps you tamper with the value.
write::<u32>(
&process.handle,
process.get_module_base("client.dll").unwrap() + DW_FORCE_ATTACK as usize,
&mut 0x5,
)
.unwrap();
// Exit this loop by pressing INSERT
if toy_arms::utils::keyboard::detect_keypress(VirtualKeyCode::VK_INSERT) {
break;
}
}
}Retrieving local player health demo is present as below. Quick tip: You don't wanna use usize as the pointer type cuz external program itself is going to be 64bit, therefore the buffer size will be 8bytes whereas the actual pointer is 4bytes. Use u32 or DWORD instead.
cargo r --example ex_get_localplayer_health --features external --no-default-features
use external::error::{ReadWriteMemoryFailedDetail, TAExternalError};
use std::mem::size_of;
use toy_arms::external::error::TAExternalError::ReadMemoryFailed;
use toy_arms::external::module::Module;
use toy_arms::external::process::Process;
use toy_arms::external::read;
const DW_LOCAL_PLAYER: u32 = 0xDBF4BC;
fn main() {
let csgo: Process;
match Process::from_process_name("csgo.exe") {
Ok(p) => csgo = p,
Err(e) => {
println!("{}", e);
return;
}
}
let client: Module;
match csgo.get_module_info("client.dll") {
Ok(m) => client = m,
Err(e) => {
println!("{}", e);
return;
}
}
println!("[+] module_base: {:x}", client.base_address);
println!(
"[+] localplayer pointer pointer: 0x{:x}",
client.base_address + DW_LOCAL_PLAYER as usize
);
let mut localplayer: u32 = 0;
let ok = read::<u32>(
&csgo.handle,
client.base_address + DW_LOCAL_PLAYER as usize,
size_of::<u32>(),
&mut localplayer as *mut u32,
);
match ok {
Ok(_ok) => {
println!("[+] localplayer pointer: 0x{:x}", localplayer);
let mut health: u16 = 0;
// 0x100 is the offset of the health in player entity class.
let ok2 = read::<u16>(
&csgo.handle,
localplayer as usize + 0x100,
size_of::<u16>(),
&mut health as *mut u16,
);
match ok2 {
// This is what we wanted.
Ok(h) => println!("[+] localplayer's health: {}", health),
Err(ReadMemoryFailed(e)) => println!("{}", e),
Err(_) => println!("[-] some error"),
}
}
Err(e) => match e {
TAExternalError::ReadMemoryFailed(ReadWriteMemoryFailedDetail::ErrorPartialCopy) => {
println!("Partial Copy. Probably the address is protected")
}
TAExternalError::ReadMemoryFailed(ReadWriteMemoryFailedDetail::ErrorInvalidAddress) => {
println!("Invalid Address")
}
TAExternalError::ReadMemoryFailed(ReadWriteMemoryFailedDetail::ErrorInvalidHandle) => {
println!("Invalid Handle")
}
TAExternalError::ReadMemoryFailed(ReadWriteMemoryFailedDetail::UnknownError {
error_code,
}) => println!("Unknown Error: {}", error_code),
_ => println!(
"[-] error: {}\n[-] Maybe non-updated offset are the reason. update it yourself.",
e
),
},
}
}This is the pattern scanning example where the pattern is for dwForceAttack in csgo.
cargo r --example ex_pattern_scan --features external --no-default-features
use toy_arms::external::process::Process;
use toy_arms::utils::keyboard::VirtualKeyCode;
const DW_FORCE_ATTACK_PATTERN: &str = "89 0D ? ? ? ? 8B 0D ? ? ? ? 8B F2 8B C1 83 CE 04";
fn main() {
let mut once = false;
// Getting process information
let process = Process::from_process_name("csgo.exe").unwrap();
// You can get module information by using get_client
let mut client = process.get_module_info("client.dll").unwrap();
let address = client.find_pattern(DW_FORCE_ATTACK_PATTERN);
match address {
Some(i) => println!("[+] found *dwForceAttack pattern at 0x{:x}", i),
None => println!("[-] NOTHING FOUND"),
}
let offset = client.pattern_scan::<u32>(DW_FORCE_ATTACK_PATTERN, 2, 0);
match offset {
Some(i) => println!("[+] found dwForceAttack offset at 0x{:x}", i),
None => println!("NOTHING FOUND"),
}
loop {
if !once {
println!("[+] Press INSERT to exit...");
once = !once;
}
// Exit this loop by pressing INSERT
if toy_arms::utils::detect_keydown!(VirtualKeyCode::VK_INSERT) {
break;
}
}
}Yes you have! Take a look at examples directory, you'll see more examples!
However, you may need to update offsets which some examples contain with your own hands.
Refer to hazedumper as always for latest offsets of CSGO.
To build examples in x86 arch:
cargo build --example EXAMPLE_NAME --target i686-pc-windows-msvcfn read<T>(
process_handle: &HANDLE,
base_address: usize,
size: usize,
buffer: *mut T,
)make sure to pass buffer like following:
let mut buffer: u32 = 0; // Declare with mut keyword
read::<u32>(
&handle,
base_address,
size_of::<u32>(),
&mut buffer as *mut u32, // Must be the form of &mut buffer as *mut T
// These are equivalent to &buffer in C++.
);in the example, both of them are used conditionally. They are present for different use.
cast!() is the basic dereference and u can always use this of course.
read() is the member method of Module struct. It allows u to just pass the offset of what u want from module base, and it adds them for you. cast!() is used under the hood.
hazedumper-rs - referenced as role model of pattern scan
