Control Flow
Control flow obfuscation aims to hide the flow of your program by mangling it. To achieve this, our engine will transform your code into a new one that behaves as the original one did with the difference that is hardly understood by humans.
The performance of the new application is barely affected, revealing the perfect feature for those that want to achieve good security without sacrificing performance.
public static void Main(string[] args) {
int i, sum = 0, n;
Console.Write("Enter the Nth Number : ");
n = int.Parse(Console.ReadLine());
for (i = 0; i <= n; i++) {
sum = sum + i;
}
Console.WriteLine("\nSum of N Numbers : " + sum);
Console.ReadLine();
}
public void InterfaceMethod(float b)
{
int num = -1961952481;
int num2 = -1574439195;
int num3 = 553806077;
int num4 = 1668559803;
for (;;)
{
if (~(((-87 / num4 & (int)-3.0786116f) ^ (int)5.293522f) < ((num4 + -95 | num4) & (int)8.033648f)) & (~(8.9628105f + (float)num4 + (float)num4 - (float)num4 < (float)(16 % num4 & num4 & (int)6.241485f)) & ~((num4 - num4 ^ num4) - (int)9.832379f < (64 * num4 + 61 ^ 86))))
{
Console.WriteLine("\nSum of N Numbers : " + sum);
num4 = (int)((-11.802868f - (float)num4) % (float)num / (float)37 + (float)767841124);
}
else
{
if (-1460763283 == num4)
{
break;
}
if (~((num4 / (int)-8.1555f ^ num4 ^ -83) > (num4 - -11 & -10) - 28) | (~((num4 - 36 | (int)-4.076834f) * 29 > (num4 / (int)-4.492111f * 73 ^ num4)) | ((12.411447f ^ (float)num4) | (float)num4) - 11.7112875f > (float)((96 + num4 ^ (int)-7.2460685f) * 16)))
{
num4 = ((50 % num3 ^ -24) >> num4) + 1792755332;
}
else if (~((-97 | num4 | num4) + -15 < ((58 / num4 ^ num4) | num4)) | (~((-26 << num4) - num4 + (int)7.8907924f < (int)((-12.561203f % (float)num4 | (float)32) * (float)45)) & (num4 - (int)-8.214035f + num4 & -84) == (num4 % num4 + num4 | num4)))
{
num4 = (int)((5.822695f % (float)num ^ (float)92) - (float)num2 + (float)113675818);
}
}
if (1474886602 == num4)
{
return;
}
}
}
By default, the Control Flow Obfuscation that we provide has little to no impact on performance, the reason is, the challenges and arithmetics added on the default settings are easily solved by the JIT Compiler. These settings, however, also reduce the complexity of obfuscation.
If you want to trade performance for security, you can do so by using the parameters present in the protection.
Mangling complexity measures how many times, the pathing of your application is obscured. This means that the control flow of your application is obfuscated multiple times, ensuring the most resilience against automatic tools (deobfuscators).
Using a number higher than 3 can worsen the performance exponentially. If you want to safeguard your code to the maximum, check Virtualization.
Expression density sets how complex the generated arithmetic expressions are. You can change this setting if you want to enhance the potency of the method and generate an uglier code when your application is decompiled.
Expression density sets how complex the logical expressions are. You can change this setting if you want to enhance the potency and resilience of the method and generate an uglier code when your application is decompiled.
The enhanced mode enables a set of techniques that obscure the pathing of the obfuscated app. This is done by adding a new layer of encryption that protects the opaques and expressions present in the application.
Last modified 1yr ago