excel word vba programm software code macro obfuscator obfuscating obfuscation schutz schützen sicherung passwort entfernen knacken verschlüsselung verschlüsseln analyse codierung tarnung tarnen excel word vba program software code macro obfuscator obfuscating protection safeguard password removing crack scramble scrambling codify encrypt encoding encoder camouflage analyzing encryption microsoft office

Why obfuscate?


Four good reasons to use CrunchCode

A number of ways are available to protect VBA source code from unauthorized access, as described below. All have serious limitations.

1. VBA project password

This option which is available in the VBA editor prevents access to the source code providing the password is not known.

2. Conversion to a DLL

This would be the most elegant way because because it converts the source text into machine code and thus protects against direct intervention.

3. Conversion to an EXE file

Some so–called compilers are available which convert the VBA code into an executable file.

4. Hacking

There are a numbers of tools which try to prevent the VBA code being displayed by direct manipulation of the file (the best known example is the so–called DPB patch for Excel files).

Bottom line:

These methods can be very effective depending on the application, but they all have limitations such as limited security or difficulties that limit their application.


If you obfuscate the source code text (without affecting its functionality) so that it becomes "unreadable" and cannot be decrypted or understood except with excessive effort, then 99,9% of attackers can be expected to give up in frustration.

With obfuscation, the full functionality of the VBA project is retained, with all connections to the application program completely untouched.

This is the aim of obfuscating!


Look at this example of obfuscated code:

Quelltexte in dieser Form sind entmutigend und verhindern meist schon einen Debugging–Versuch