What the Obfuscator does
Upload a compiled Windows program and get back a protected one that is hard to read, hard to attach to and hard to change. No source code and no change to your build.
Open it now:Obfuscator, Overview
What goes in and what comes out
You give it a finished .exe or .dll, 32-bit or 64-bit, from any compiler that produces a normal Windows program. It returns the same program with protections applied: its code rewritten, its strings and imports hidden, checks woven in that detect debuggers, injection, memory dumps and patching, and a chosen response when one trips. Every build is different, so a technique that works on one protected file does not carry over to the next.
The Obfuscator is a separate product from Atlas Auth and needs no SDK. The two work well together, and Use it with Atlas Auth explains how.
What it defends against
The protections fall into six suites, each answering one thing an attacker does:
| Suite | The attacker | Result |
|---|---|---|
| Reverse-engineering defense | Opens the file in a decompiler. | It yields nothing usable. |
| Debugger resistance | Attaches a debugger. | The process is already gone. |
| Injection resistance | Injects a library or manual-maps code. | Foreign code cannot live inside it. |
| Memory acquisition resistance | Dumps the process memory. | The dump is unusable. |
| Code virtualization | Looks for the function worth stealing. | It no longer exists as native code. |
| Integrity binding | Patches bytes to skip a check. | The math breaks, silently. |
Defense suites lists what each defeats. No protection makes a program impossible to analyze. They raise the time, skill and tooling an attacker needs, which is what stops almost all of them.
Where to find it
In the dashboard, switch the product from Authenticator to Obfuscator at the top of the sidebar. Its pages are Overview, Protect, Jobs, History, Templates, Analytics and Plan, described under Protect a file and Builds, downloads and history.