Welcome to hackvshack.net Forum!
Download Free HvH CS2/CS:GO Cheats, CFG, LUA/JS Scripts, and More!
Register

Safe Rust Free DMA/External Cheat, Aimbot(MAKCU), Wallhack/ESP for Players, Scientists, Crates and Loot

Plisskien

Administrator
User ID:
1
Messages:
2,692
Reactions:
4,785
Badges:
30
REP:
−4/91+
Level:
779
Hello again!

Today, I'm releasing another DMA/Poor DMA cheat, but this time we're talking about Rust, I've spent the most time working on. It was actually the main game that got me interested in cheating in the first place, because of that there is very rich ESP with everything what you may ask for (This even includes the status of monument doors, showing whether they've been opened!) Thus, when it comes to overall quality, I'd say this is the best cheat in my series!

At first I would like to clarify that this is a DMA cheat, but it can be also used as an External cheat if we were to use my technology that I called Poor DMA on the same computer, but in such case there is risk of getting ban due to overlay on the game. Everything what you need to know regarding this approach is located under this link, a lot of reading but worth it, thus below link is about Poor DMA, for people without DMA cards.

Screenshot from game showing Wallhack/ESP:
free rust dma cheat.webp

Menu showcase:
1793619310473.webp
1793619322043.webp
1793619336299.webp
1793619348027.webp
1793619357667.webp
1793619370683.webp
1793619382563.webp
1793619392677.webp

Features list:

1. Visuals & ESP​

Target categories (36 groups, seven families, every row with its own switch, distance and colour):
  • Players
  • Teammates
  • Sleeping players
  • NPCs (scientists and every other AI kind, routed separately from players)
  • Animals and Corpses
  • Ore, per kind - wood, stone, metal, sulfur, HQM.
  • Loot, per crate - wooden, normal, military, elite, locked, food, medical, supply drop, dropped items, high-tier loot
  • Vehicles, per kind - cars, boats, aircraft, trains, submarines, siege machines, NPC vehicles
  • Pickups - wood, stone, metal, sulfur, hemp, food
  • Traps - landmine, bear trap, shotgun trap, floor spikes, tesla coil
  • Turrets - auto turret, NPC turret, SAM site, flame turret
  • Drones, delivery drones, keycard doors
ESP rendering:
  • Pose-true boxes - the box is drawn around the entity's own projected joints, so a body that is prone, crouched or leaning gets a box that is its pose, not its prefab's standing bounds
  • Prefab-measured sizes - each prefab's bounds are measured once from the game, so a box is the size of the thing and not of a table entry
  • Whole-rig tracking - fourteen named joints resolved through the model's bone table, in two spans per entity per pass
  • Head marker on the rig's actual head joint
  • Health bars and numbers
  • Name, distance, team - and stance, plus speed and heading derived from position deltas (there is no readable velocity field on this build, so it is measured, not guessed)
  • Snap lines (bottom, centre or top of screen)
  • Velocity arrow (real movement heading and horizontal speed)
  • Look line (the direction a body is actually facing)
  • Off-screen direction arrows for anything outside your view
  • Group colours and per-group maximum distance
  • Every text element has its own placement, size and colour
  • Damped between passes, so boxes and text do not twitch when a read is late

2. Threat Alerts​

  • Proximity warning: a line at the top of the screen plus an arrow pointing the way to turn, for the nearest player inside a chosen range, with its own size and colour. It answers a question a box cannot: is anyone within reach right now

3. Hardware Aimbot & Mouse Control (MAKCU)​

  • Hardware mouse emulation: physical USB/serial input through an external MAKCU microcontroller - zero software mouse events on the Game PC
  • Hold button bound by pressing it on the real mouse, because the device is what sees it
  • Target selection: the cone, the range and the strength, then what counts as a target and which one wins
  • Aim joint: any of the rig's named joints, aimed in the same clip space the ESP draws through - so the box and the aim point cannot disagree
  • Humanising: the smoothing that keeps a hold-for-aim assist looking like a hand
  • On-screen block: the numbers that change while you play are drawn on screen, not buried in a panel over the game
  • Test target and Measure so the device can be proven on this PC before a match

4. Display & Fuser​

  • Every attached display listed with its mode, "put the window here", and a mode switch for the fuser sizes it supports
  • Game resolution matched to this display by default, or a preset, or custom - with the aspect ratio measured from the projection matrix, not assumed
  • Alignment with a test pattern and X/Y offset, fullscreen, always-on-top
  • Pixel-sharp drawing and a text outline with its own width and colour

5. Configs & Diagnostics​

  • Saved configs: Load, Save, Create, Delete
  • Three destructive actions ask twice (delete, overwrite on save, reset everything)
  • Link tab: entity and class counts, rigs resolved, pass time, snapshot age, camera age, frame rate, what was drawn
  • Console mode for a log instead of a window

​

Keys:
  • INS - show or hide the settings panel
  • F11 - toggle fullscreen
  • Esc - leave fullscreen (it does not close the window)

Instruction:

Option 1: LAN Mode (Poor DMA - 2 PCs over Network)​

Use this if you do not have a physical DMA card. Both computers must be connected to the same local network / subnet.
Step 1 - On the Game PC:

  1. Launch Rust and join a server, spawned into the world.
  2. Open an Administrator Command Prompt or PowerShell.
  3. Run the server (must be launched after the game):
    Code:
    Expand Collapse Copy
    poor_dma_server.exe
Step 2 - On the Client PC (Secondary PC):
  1. Run the client:
    Code:
    Expand Collapse Copy
    lan_client_rust.exe -lan
  2. (Optional) If automatic network discovery fails to find the Game PC, point it at the address explicitly:
    Code:
    Expand Collapse Copy
    set POOR_DMA_SERVER=192.168.1.xxx:39172
     lan_client_rust.exe -lan

Option 2: Hardware DMA Mode (PCIe FPGA Card)​

Use this if you have a physical FPGA PCIe card (e.g., Captain, Enigma, Lambda, LeechCore).
Hardware Setup:

  • Install the DMA card into a PCIe slot on the Game PC.
  • Connect the USB 3.0 data cable from the DMA card to the Client PC.
  • Place the PCILeech DLLs (vmm.dll, leechcore.dll, FTD3XX.dll, and dbghelp.dll) directly in the same folder as lan_client_rust.exe (or inside a DMA DLLs\ subfolder).
Step 1 - On the Game PC:
  1. Power on the system and launch Rust.
Step 2 - On the Client PC:
  1. Run the client with the -dma flag:
    Code:
    Expand Collapse Copy
    lan_client_rust.exe -dma

Display & Hardware Mouse Setup (Both Modes)​

  • Video Fuser (Overlay): Plug the HDMI output from the Game PC and the HDMI output from the Client PC into an HDMI Video Fuser. The client renders as a transparent borderless fullscreen window keyed over the game.
  • Aimbot Mouse (MAKCU - Optional): Plug the MAKCU device into the Game PC via USB, and connect its COM/serial data cable to the Client PC. Use the MAKCU tab to prove the device and bind the hold button on the real mouse.

OFFSETS UPDATING!!!
Rust patches constantly, and I will not be updating the offsets for you -- the client reads every offset and every decryption program out of offsets.toml, so a patch day is a file edit, never a new build. You can update them yourself with this agentic dumper:
The only thing you need to do is ask AI to check one .md file -- dumper\UPDATE.md -- and it will update everything for you using DMA or Poor DMA. Offsets are in offsets.toml, the only thing you should do is to specify the method of reading memory and where the file with offsets to update is.
IF YOU UPDATE THEM YOURSELF SHARE THEM HERE FOR OTHER PEOPLE AS REPLY BELOW WITH DATE!!!

Troubleshooting

In case of any bugs, or problems while using this cheat, don't forget to paste log in reply and additionally in details explain what is the issue, and if there is such possibility include image, in that case I can HELP, if you are going to write that there is SOME bug and you can't even clarify what it is, you will be ignored.
 

Password for .zip file is hvh.net

Last edited:
Safe file: no malicious activity detected, safe to use
 
GameAssembly.dll not present in the target`s module list - waiting for the first snapshot. dma and fw are ok1793712924392.webp
 
Last edited:
yeah game is running, tried to restart game and cheat, same issue
This .dll must be there in the process if it is running, do you have access to any AI model such as deepseek flash or glm flash? In that case you can debug it with WinDbg, but ofc run rust without EAC thus directly from files, and then maybe it will find the reason, tell AI to debug client not the game, I never had such bug, while I was also testing it on DMA card, but I guess then it must be some bug in the code, but I wonder what is the reason
 
This .dll must be there in the process if it is running, do you have access to any AI model such as deepseek flash or glm flash? In that case you can debug it with WinDbg, but ofc run rust without EAC thus directly from files, and then maybe it will find the reason, tell AI to debug client not the game, I never had such bug, while I was also testing it on DMA card, but I guess then it must be some bug in the code, but I wonder what is the reason
idk maybe ill try to fix with ai, cant do it now unfortunately:(
 
GameAssembly.dll not present in the target`s module list - waiting for the first snapshot. dma and fw are ok1793712924392.webp
I got this too. something in the cheats source for the DMA card mode is wrong im pretty sure. wasnt able to figure it out

edit: are you using AMD CPU? Apparently there is something with intel cpus that prevents eac from hooking properly, so the cheat may work on intel but not amd
 
I got this too. something in the cheats source for the DMA card mode is wrong im pretty sure. wasnt able to figure it out

edit: are you using AMD CPU? Apparently there is something with intel cpus that prevents eac from hooking properly, so the cheat may work on intel but not amd
I was developing it on AMD cpu, this is weird, in that case can u help me debugging the issue?
 

Who has read this thread (Total: 1) in last 1 hours View details