Quote:
Originally Posted by !JoelR
No, they are just using the DMA to map/inject their internal. It's the same thing Hyper did.
|
I don’t quite understand why people feel the need to slander our products. It seems other providers really like to slander us. Almost as if they don’t like the guys that are trying to lower the price of DMA products.
So let me put it to you like this, What hyper did was spam shellcode into RWX, LOTS of shellcode, Something that hasn’t been safe on rust for about a year and something that isn’t safe on apex anymore. I wont go into the details because it isn’t my job to teach the competition about their detections.
At MOE our team is used to making internals and actually dealing with anti cheats. That being said why would we want to be internal with DMA? Lets say we aren’t doing what hyperhax was doing but are fully internal. Why would we put that on DMA? Why would we waste a good injector that we could turn into 30k/m on a DMA cheat? It doesn’t exactly add up does it? That isn’t even assuming the challenges that come with making internals, it is a whole other ballpark when it comes to anything none native to the game resulting in you having to do a lot of patches to windows or to the anti cheat. So making an entire internal just to use something like websockets to communicate it out to another pc instead of just drawing internally, That has to be the daftest thing you can do.
Our Rust cheat only writes to Heaped memory. It is completely safe and will never write to any immutable memory pages.
Want to test if we use shellcode? It is quite simple, So just use our open source library:

Take that codecave finder and search through the game for all the RWX sections, read to each one and them for the entire size of the RWX page. Then print it out. Store it. Run the cheat. Then run the shellcode finder again. If we utilized shellcode you would see many of the page contents change. Do this with atomic and their custom chams, it is weird how you will find them changing a RWX page to a static bytearray that takes 4 minutes for any anti cheat to sig.
55 48 8B EC 48 81 EC C0 01 00 00 49 BF 00 43 80 D5 BB 00 00 00 49 89 4F 20 49 89 57 28 4D 89 47 30 4D 89 4F 38 48 B8 50 3E 73 7C F8 7F 00 00 48 B9 20 2D A3 A4 1E 02 00 00 48 BA B8 74 D9 82 1E 02 00 00 49 B8 1B 16 00 00 00 00 00 00 FF D0 49 BF 00 43 80 D5 BB 00 00 00 49 89 07 48 33 D2 48 8B C8 FF C2 4D 33 C0 48 B8 E0 39 73 7C F8 7F 00 00 FF D0 49 BF 00 43 80 D5 BB 00 00 00 49 89 47 08 48 33 D2 90 90 90 90 90 48 B8 10 4E 29 54 F8 7F 00 00 49 BF 00 43 80 D5 BB 00 00 00 49 8B 0F 48 33 D2 FF D0 49 BF 00 43 80 D5 BB 00 00 00 49 89 47 10 48 B9 20 2D A3 A4 1E 02
^ It might have changed since this dump. But the principle stays the same.
That is a small little segment that can easily be scanned for that detected with ease. Now think, these are the guys making this up about us, the ones that use shellcode that can be detected within 5 minutes.

Now last time I checked, aimbot and no recoil doesn’t cause bans for other providers. So is it more likely that a few people using an obscure feature like their RWX custom chams was causing these bans.
If anyone is curious as to why we are talking about AtomicDMA in this post, its because these false allegations come from them. Which we find completely ironic due to their usage of shellcode. Trying to then get us removed from the legit providers list is just petty. It is funny how instead of coming up with proof of these acquisitions they made stuff up. If they were competent cheat devs, really fighting for their users to have a better experience and avoid bans from a nasty RWX spamming internal, you would expect them to at least post proof, maybe even a cheat dump.
It is just odd to make up nonsense. There are genuine parts of our cheat that are easy to critique such as a crashing bug and kmbox net issues. Yet going to the extent of making nonsense up to try get people removed off seller lists is a whole other degree of absurd.
Here is their sexy shaders
