catalyst

Protect your binary.
Keep your logic yours.

Binary-rewriting obfuscation that only touches what it can prove safe.

Do the obfuscation in the obfuscator,
not the code.

Before· VMProtect markers by hand
// you mark every region & string
int check(const char* key) {
  VMProtectBeginUltra("check");
  const char* salt = VMProtectDecryptStringA("S3cr3t");
  int acc = 0;
  for (int i = 0; i < len; i++)
    acc ^= key[i] ^ salt[i % 6];
  if (!strcmp(user, VMProtectDecryptStringA("admin")))
    grant(VMProtectDecryptStringA("ROOT"));
  VMProtectEnd();
  return acc == TARGET;
}
After· clean source, protected by catalyst
// what you actually write
int check(const char* key) {
  const char* salt = "S3cr3t";
  int acc = 0;
  for (int i = 0; i < len; i++)
    acc ^= key[i] ^ salt[i % 6];
  if (!strcmp(user, "admin"))
    grant("ROOT");
  return acc == TARGET;
}

Why

Strip the flags and string encryption out of your code and you kill two birds with one stone.

No chance of user error from a bad or missed implementation — there's nothing to get wrong.

Easier to code knowing the obfuscation is handled, so you can focus on what you should be focusing on.

Find inner peace,
knowing your binaries are safe.

Cherry blossoms on a tree trunk — woodblock print by Utagawa Hiroshige