You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When layering obfuscation methods, it can be fairly simple to modify a layer to print out the next layer. Then you can keep doing this until the unobfuscated command is printed. To combat this, I am proposing a layer dependability feature. It will work like this:
Generate obfuscated layer 1.
Save a random amount of variable instantiation statements for later, do not include them in the first layer.
Generate obfuscated layer 2.
Put the saved variable instantiation statements needed by layer 1 somewhere random in layer 2.
During runtime of the obfuscated payload, the variables needed by layer 1 are first instantiated in layer 2.
Layer 2 then runs layer 1, who knows the values of the variables instantiated in the previous layer.
Successful execution of layer 1 by itself without modification is impossible, since it depends on commands being executed prior to itself being executed.
The text was updated successfully, but these errors were encountered:
When layering obfuscation methods, it can be fairly simple to modify a layer to print out the next layer. Then you can keep doing this until the unobfuscated command is printed. To combat this, I am proposing a layer dependability feature. It will work like this:
The text was updated successfully, but these errors were encountered: