Skip to main content

Information regarding provided dumps

You might find that certain dumps and linked IDA databases specialize in documenting different concepts. Therefore I decided to explicitly label which purpose a dump fits the best. For example, If your main goal is to learn more about the general game engine, then you might require a different context than if you were interested in anti-cheat capability.

Type Purpose
Generic

For general-purpose analysis and quick scouting for changes, 

Game/Engine

For analysis of game-specific mechanisms and deeper exploration of the game engine.

AntiCheat

For analysis and further research about integration with both third-party, and in-house cheat detection solutions. 

How to achieve an usable dump?

I think there is currently three popular ways of how people capture a dump of Apex. I will list them from most common to least.

1. Classic one-time memory dump

This is probably the easiest way to have something to look at quickly, without spending much time and effort on your dumper. It might suffice if all you care about is finding offsets for use In cheat software. It won't be enough if you care about not having to dump at multiple points of in-game time, like pre-lobby, post-lobby, or post local player spawn, and end up with multiple dumps. Sure, you could write something up that could easily fuse them if you somehow mark uncaptured pages in both, but there are much better ways to accomplish it without having to attack their packer or introducing packer-specific logic.

 2. Passive dumping over a set period of time

If you're looking for a middle ground inbetween just classic dumping and the more invasive, "Attack the Packer" approach, then you might find yourself in this situation. You will have real caveats with this one, for example you will never be able to capture any cold pages. With that I just mean pages that the game never executes during the time you dump. This can and does happen if you use this approach. However, you can achieve close to ~80% coverage of the code section if you're patient and play the game to let it gradually unpack much of its code pages.  

3. Attacking of Apex's Packer

If you're here, you probably don't need me to explain it. But I'll do it either way for those who might not know. You can technically find flaws within Theia, which is just the name of Apex's third party packer/anti-tamper stuff, to then abuse it for fabricating a near fully complete memory dump. This is nothing new and people have been doing and flexing it on cheater social spaces all the time. It certainly is arguably harder than Methods 1-2 because you would actually have to spend effort to understand the internals of their packer/AT. Obviously there is endless ways to achieve it if you're skilled enough or posess advanced tooling.

For drof's labs, I rely solely on Method 2. Why? Because simply put, I'm not interested in an arms race with their outer security layers when I can get most of the things done with passive dumping. I'll acknowledge Its caveats again in order to avoid confusion: Yes, It will lead to me missing any pages that are cold. But the key is: most stuff you care about is actually accessed by Apex at some point. It might take lots of manual action and deliberately forcing unlikely events, but It can pay out if your primary goal is code that is actually running during your dump.