For Autohotkey Dynamic Object Name Obfuscation, Use the DUMP Commands
DUMP Commands Are Mandatory When Dynamic Obfuscation is Used
Because Dynamic Obfuscation builds object names out of fragments represented by
The assignment statements themselves will have object name fragments inserted into them which will be represented by the presence of
The fragments used in the assignment statements can be common security fragments or they can be fragments associated with a secure classe. Since common security fragments are used frequently even by secure classes for some things, they must be DUMPed before most other types of DUMPS are done.
If you choose to randomize the order of functions and label sections on the obfuscation run screen, then the order of individual statements within the DUMPS will also be scrambled, making it more difficult to identify individual assignments.
The DUMPS commands will put comment headers into the code to identify individual object initializations which is useful for debugging. To have them show, uncheck the 'strip out all comments' box on the obfuscation run screen.
"%"s, these fragments must be initialized somewhere in your program.
The DUMP command comments allow you to do that at places of your choosing in your source code.
When using Dynamic Obfuscation you must always DUMP common object fragments and DUMP fragments for object types. If you create secure classes, you must use the DUMP commands for those and you can also use the DUMP Poisoned command for those. If you want to change where your function calls go to, use the DUMP Rewire Function.
The DUMP command comments will drop a bunch of assignment statements into your code. These statements will initialize the values of object name fragments that will be used to create and secure object names.
The assignment statements themselves will have object name fragments inserted into them which will be represented by the presence of
"%"s. Both sides of the assignment statement will have these so that it will be difficult for the hacker to find the place where an object fragment used in the program is initialized.
The fragments used in the assignment statements can be common security fragments or they can be fragments associated with a secure classe. Since common security fragments are used frequently even by secure classes for some things, they must be DUMPed before most other types of DUMPS are done.
If you choose to randomize the order of functions and label sections on the obfuscation run screen, then the order of individual statements within the DUMPS will also be scrambled, making it more difficult to identify individual assignments.
The DUMPS commands will put comment headers into the code to identify individual object initializations which is useful for debugging. To have them show, uncheck the 'strip out all comments' box on the obfuscation run screen.
Insert mandatory DUMP Commands for Dynamic Obfuscation
See Mandatory DUMPS COMMANDS for Dynamic Obfuscation for a sample of code to insert so that mandatory dumps will be made.
DUMP Commands for Secure Classes
If you've created secure classes, you will need to use DUMPS for Secure Classes as well!