The GPL Problem
WordPress is GPL. Plugins that depend on WordPress core are derivative works and must be GPL-compatible. Obfuscating GPL code is incompatible with the license. WordPress.org explicitly requires "code must be mostly human-readable."
The Security Scanner Problem
Security tools like Wordfence and Sucuri flag eval(base64_decode(...)) as malware. If you obfuscate a plugin with eval-wrapping, it will be flagged as malicious even if it's benign.
What This Tool Actually Does
It uses regex to find $variable and function name patterns and replaces them with $a, $b, fn1, etc. It does not parse PHP. It will break on:
- WordPress hooks —
add_action('init', 'my_function')references the function name as a string - Namespaced code
- String interpolation with variables
- Class methods and properties
For real PHP obfuscation, use a proper tool:
globus-studio/php-obfuscator (token-based, Composer package) or Component Batch Encryptor (Python CLI). This browser tool is for learning only.