How to get base address of process?

[Leastrio]

I have a game that doesnt have any dll modules so i cannot use those, instead i need to take the base address of the game and add my offsets to it. How may i do this?

[vxcall]

Hi!
Which way are you trying to do, external or internal? It depends, but i think it'll work if u pass executable name like "foo.exe" instead of dll name.
if it doesnt work, let me know!

[Leastrio]

I am currently using external, and I just tried passing the executable name instead of a dll name and it errors with a PartialCopy error.

[vxcall]

May I take a look at a minimal reproducible example of the bug?
If it appears because of your code or target memory, i can point it out, or if it looks my code's fault, I'll fix it so:)

[Leastrio]

    let lol: Process = match Process::from_process_name("League of Legends.exe") {
        Ok(p) => p,
        Err(why) => {
            panic!("{}", why)
        }
    };

    let module_info = lol.get_module_base("League of Legends.exe");

    println!("{:#?}", module_info);

Will print

Err(
    ReadMemoryFailed(
        ErrorPartialCopy,
    ),
)

[vxcall]

Does it print at the line of panic!("{}", why) ??

[Leastrio]

Nope, it prints at the last println

[vxcall]

Thanks, Since it's my codes bug, I'll take a look at my code and stuff 🙂

[Leastrio]

thank you !!

[vxcall]

plz be informed that it may take a while cuz im swamped this week.

[Leastrio]

Thats completely fine! im in no rush just experimenting with gamehacking.

[vxcall]

Thanks.
This is off topic but cpp is way easier than rust when u manipulate memory. Rust complain about types every time u compile...
I just leaving this code as a reference for later and backed to cpp haha.

[Leastrio]

yeah ive realized that, i wanted to see how far i could go with rust as its my main language i use. C++ has a lot more resources for gamehacking so i might learn a bit of C++ because itll make this field easier to learn

[vxcall]

So I tested it with random 64bit process I own now and it just worked.

use toy_arms::external::process::Process;

fn main() {
    let process = Process::from_process_name("WAIUA.exe").unwrap();
    println!("process handle: {:?}", process.handle);
    let module_info = process.get_module_info("WAIUA.exe").unwrap();
    println!("{}", module_info);
    while true {}
}

# output
process handle: 0xac
module_name: WAIUA.exe
module_size: 290816
module_base_address: 140698121076736  <-- 0x7ff6d5870000 in hex which is correct as shown below image
module_handle: 0x7ff6d5870000
module_path: C:\Users\pseuxide\AppData\Local\Programs\WAIUA\WAIUA.exe

probably League of Legends has a sort of memory protection technique. or maybe hooking VirtualProtect or something. I'll debug with League of Legends tomorrow.
Are you not getting baned? Careful if u use this kind of library on Anti cheat-equipped game, it might get u baned unless u reverse engineer the integrity checker and hack it beforehands.

[vxcall]

I just examined it and indeed, error get caused in the memory reading part. It's been long time since i peeked at this code, but rust's code is horribly hard to read. omg

[Leastrio]

So I tested it with random 64bit process I own now and it just worked.

use toy_arms::external::process::Process;

fn main() {
    let process = Process::from_process_name("WAIUA.exe").unwrap();
    println!("process handle: {:?}", process.handle);
    let module_info = process.get_module_info("WAIUA.exe").unwrap();
    println!("{}", module_info);
    while true {}
}

# output
process handle: 0xac
module_name: WAIUA.exe
module_size: 290816
module_base_address: 140698121076736  <-- 0x7ff6d5870000 in hex which is correct as shown below image
module_handle: 0x7ff6d5870000
module_path: C:\Users\pseuxide\AppData\Local\Programs\WAIUA\WAIUA.exe

probably League of Legends has a sort of memory protection technique. or maybe hooking VirtualProtect or something. I'll debug with League of Legends tomorrow. Are you not getting baned? Careful if u use this kind of library on Anti cheat-equipped game, it might get u baned unless u reverse engineer the integrity checker and hack it beforehands.

They dont care if I do passive memory reading, which is all im doing for now.

[Leastrio]

I just examined it and indeed, error get caused in the memory reading part. It's been long time since i peeked at this code, but rust's code is horribly hard to read. omg

i find rust to be easier to read than C++, but thats because ive used it more. It is probably the same thing with you just opposite

[vxcall]

So, i found the possible problem that might be causing this issue, and confirmed it by testing things in C++ haha. Anyway now I have an idea to fix it. I'll fix it in this few days ~~