Troubleshooting — VM Obfuscation | Obfuscator.io Documentation

Section

Troubleshooting VM Obfuscation

VM obfuscation is a complex technology. While it has been tested extensively, some edge cases may still cause issues.

VM obfuscation completely transforms your code into custom bytecode. Ideally, this transformation should handle all possible code patterns and edge cases seamlessly. However, due to the complexity of VM obfuscation, there are still edge cases that may not be fully supported. This means that VM-obfuscated code must be carefully tested in at least all happy-path scenarios before deployment.

If your code doesn't work after VM obfuscation:

1. Narrow down the problematic code
Use vmTargetFunctionsMode: 'comment' to selectively VM-obfuscate specific functions. Add the /* javascript-obfuscator:vm */ comment only to individual functions and test incrementally to identify which function causes the issue.
2. Contact support with details
Email support@obfuscator.io with as much information as possible:
- Error message and stack trace
- Environment (browser/Node.js version)
- Obfuscator options/preset used
- Obfuscator version (shown in the bottom-right corner of the editor)
- Minimal code sample that reproduces the issue (ideally the narrowed-down problematic function)

To significantly simplify debugging on our side, ideally share your source code with us. If your code is proprietary and you cannot share it directly, we can sign an NDA. Understanding the original code pattern that causes an error is essential for diagnosing and fixing the issue.

Using the NPM Package

Basic Obfuscation