search

MisterY52 / apex_dma_kvm_pub

Apex Legends QEMU/KVM hack
427 stars 183 forks source link

Does this bypass the anti-cheat? #23

Open Glaiveisdad opened 2 years ago

Glaiveisdad commented 2 years ago

title

Xenia0 commented 2 years ago

write your own.

KZDKM commented 2 years ago

Correct me if I'm wrong, but seeing how kvm dma works, You could kinda make it undetectable if you remove the guest part of this hack, so there would not be anything related to cheat running on the guest OS (where the anti-cheat has their eyes on).

You could use looking glass to display the graphical output on your host OS and write a overlay over the looking glass viewport to display ESP with the memory you are reading from the guest os.

But I dont know how you would retain the aimbot feature if you do it this way because it would be hard for you to detect input to activate the aimbot. One possible way of doing it is to do evdev passthrough so therefore the host could still read the input going to the guest operating system and find a way to monitor the input stream on host.

Do note that hypervisor is still a detection vector, despite that EAC is pretty forgiving on VMs.

Kamineko1978 commented 2 years ago

We are looking for someone to set up. We will also prepare a reward.

PaulDotSH commented 2 years ago

Correct me if I'm wrong, but seeing how kvm dma works, You could kinda make it undetectable if you remove the guest part of this hack, so there would not be anything related to cheat running on the guest OS (where the anti-cheat has their eyes on).

You could use looking glass to display the graphical output on your host OS and write a overlay over the looking glass viewport to display ESP with the memory you are reading from the guest os.

But I dont know how you would retain the aimbot feature if you do it this way because it would be hard for you to detect input to activate the aimbot. One possible way of doing it is to do evdev passthrough so therefore the host could still read the input going to the guest operating system and find a way to monitor the input stream on host.

Do note that hypervisor is still a detection vector, despite that EAC is pretty forgiving on VMs.

Writing code that interacts with the X11 lib works too, I have a simple example of an overlay for X11 systems, it also does a passthrough of the clicks so this should mean that besides hypervisor (pretty small chance), and memory writing (even smaller chance) there are no detection vectors.

I didn't think about the host not being able to capture input, but there definitely should be a fix for this, in the "worst case", you could just capture input from the overlay and pass it to kvm/qemu manually.

Quicals commented 2 years ago

If anyone makes apex thingys dm me 6ix#4431