Before you run de4dot on a protected file, it helps to know what the de4dot supported obfuscators list actually covers. de4dot is built to recognise a range of well known .NET protectors and undo the tricks they use. That support is not unlimited, though, and it changes with the version of de4dot and the version of the obfuscator used on the file. This guide gives you a realistic picture of what de4dot can clean, where results may vary, and what to do when a file is not recognised.
How de4dot Support Works
de4dot does not use one generic cleaning routine for every file. It contains separate detectors and cleaners for individual obfuscators. When you run it, it first looks for signs of a known protector, then applies the matching routines. If it cannot match the file to a protector it knows, it reports that the obfuscator was not detected rather than guessing and damaging the file.
That design is why support is best described as a list of protectors with varying depth, not a simple yes or no. Some protectors are cleaned thoroughly, including renaming and control flow changes. Others may be only partly reversed, especially when the protected file uses a newer build or an unusual combination of features.
The Supported Obfuscators List
The following protectors are the ones de4dot is commonly known to handle. Think of this as a working list rather than a guarantee for every file.
- ConfuserEx: one of the most commonly cleaned protectors, including its renaming and control flow features
- Confuser: the earlier protector that ConfuserEx grew out of, still recognised in many builds
- Dotfuscator: widely used in commercial .NET projects, with varying results depending on the edition and options chosen
- .NET Reactor: a popular commercial protector with several layers of protection, cleaned to different degrees depending on settings
- SmartAssembly: another commercial protector, where results depend heavily on the features turned on
- Eazfuscator.NET: commonly seen in desktop applications, with support for many of its standard features
- Agile.NET: an older protector that de4dot still recognises in many cases
- Crypto Obfuscator: supported for many of its common configurations
- Babel Obfuscator: recognised and cleaned in many builds, though newer options may reduce the result
- CodeWall: a less common protector that appears in de4dot’s supported set
- DeepSea Obfuscator: supported in many builds, with the usual limits on newer or layered settings
- Goliath.NET: another protector in the supported range, again with results that vary by version
If your file was protected with one of these and the result looks poor, the version matters. A protector from 2024 or later may include changes that an older de4dot build does not yet understand. Checking which build you are running is a sensible first step.
What Support Does Not Mean
Being on the supported list does not mean every protected file will come back perfectly readable. Obfuscation can be layered: a file might be protected twice, or the author may have used custom settings, string encryption and virtualisation together. In those cases de4dot may clean the outer layer well and leave parts of the code still hard to read.
It also does not mean the cleaned file will be identical to the original source. Names that were removed during obfuscation cannot be invented back, and comments are gone for good. What you get is a working, readable assembly, not a perfect reconstruction of the developer’s source code.
How to Check Whether Your File Is Supported
- Run de4dot on a copy of the file and read its output: it will name the obfuscator it detected, if any
- Compare the cleaned output with the original: check that classes, methods and strings are more readable than before
- Try a simple test file protected with the same tool, so you can separate tool limits from file-specific problems
- If detection fails, confirm the file is a .NET assembly and has not been packed with a native packer first
For a plain introduction to what the tool does, what de4dot is and how it works explains the detection and cleaning steps in simple terms.
When de4dot Cannot Clean a File
When de4dot reports an unknown obfuscator or produces a file that is still hard to read, do not force the issue by editing the cleaned output blindly. First check whether you are using the latest build, since support improves over time. Then check whether the file uses a protector that is not on the list, or a customised version of a known protector.
Some files also combine .NET obfuscation with native packing or virtualisation. Those layers need different tools and skills, and they are outside what de4dot is designed to do. If you run into repeated failures, how to fix de4dot not working walks through the common errors and their fixes.
Conclusion
The de4dot supported obfuscators list is broad, covering the protectors most .NET developers and analysts will meet in everyday work. Support is strongest for well known tools such as ConfuserEx, Dotfuscator, .NET Reactor and SmartAssembly, and it varies with version and settings. Test on a copy, read de4dot’s detection output, and treat a partial result as normal rather than a failure. That way you get the most out of the tool without expecting it to do more than it can.
Frequently Asked Questions
Does de4dot support ConfuserEx?
Yes. ConfuserEx is one of the protectors de4dot handles most often, including renaming and control flow protection, though results vary with the version and settings used.
Does de4dot support Dotfuscator?
Dotfuscator is in de4dot’s supported range, but the result depends on the edition and the options chosen when the file was protected.
Can de4dot clean .NET Reactor files?
.NET Reactor is supported, but because it offers several layers of protection, some files clean better than others depending on which features were enabled.
What happens if my obfuscator is not on the list?
de4dot will usually report that it could not detect the obfuscator. That means it has no matching cleaner for that protector, and you should not expect a useful cleaned file from that run.
Does a newer de4dot version support more obfuscators?
Often, yes. Support improves as new builds add detectors and cleaners, so checking you have the latest version is a good step when a file is not recognised.


