Business team meeting around laptops in an office

How to Clean Agile.NET Protected Files With de4dot

Agile.NET is a protector that can make a .NET program difficult to read, even for experienced analysts. This guide shows how to clean Agile.NET protected files with de4dot, what to check before you run it, and how to handle a result that is only partly readable.

As with other protectors, the goal is not to force a perfect result on the first try. The goal is a safe, repeatable process that tells you clearly what worked, what did not, and what to try next.

What Agile.NET Protection Usually Changes

Agile.NET can rename code, encrypt strings, change control flow, and add checks that make a program harder to analyse. The exact mix depends on the settings chosen when the program was protected, so two files with the same protector can behave quite differently in de4dot.

That is why detection matters. If you skip detection and go straight to cleaning, you may miss a second protector, a packed file, or a feature that de4dot handles only partly. A few minutes of checking at the start can save a long, confusing analysis later.

Before You Clean an Agile.NET File

Work only with files you own or have permission to analyse, and work on a copy. Keep the original protected file safe, note its size and dependencies, and use an isolated system if the sample is untrusted.

  • Copy the EXE or DLL into a separate working folder.
  • Put de4dot in the same folder for a simple first run.
  • Record the detection result before you clean.
  • Keep dependencies with the file, so a load error is easy to spot.
  • Do not run an untrusted cleaned file on your main system.

Step 1: Detect the Protection

Run detection first and read the output carefully.

de4dot -d yourfile.exe

If the output names Agile.NET, you have a match to work with. If it names something else, or nothing clear, pause and reconsider, because cleaning with the wrong assumption can produce a file that looks clean but still hides important protection.

Step 2: Run a Basic Clean

Start with a plain run, without extra options. A simple run is easier to compare with later runs, and it gives you a baseline cleaned file.

de4dot yourfile.exe

Check the output for warnings about unsupported features. Those warnings are not failures on their own, but they point to the parts of the file that may still need manual work after cleaning.

Step 3: Inspect the Cleaned File

Open the cleaned file in a decompiler and check whether class names, method logic, and strings are easier to follow. Look for methods that are still scrambled, strings that are still hidden, and resources that are missing. A partial clean is still useful, as long as you know which parts are reliable.

To understand what de4dot produced, read the guide to the de4dot cleaned output file. It explains how the cleaned file is named, where it appears, and what to check next.

Step 4: Try a Conservative Run If Needed

If the cleaned file crashes or will not open, try keeping names unchanged. This can help when renaming causes a problem, although the result will be harder to read.

de4dot --dont-rename yourfile.exe

Compare that result with your first clean. If the conservative run is more stable, use it as your analysis copy and note the trade-off. Stability matters more than perfect readability when you need a file you can actually inspect.

When a Clean Is Only Partial

Some Agile.NET settings, especially stronger string encryption or custom protection layers, may leave parts of the code unclear. In that case, focus on what was recovered. Document the methods that are clear, the data that is readable, and the sections that still need manual analysis. A clear partial result is far more useful than a forced result that looks complete but is wrong.

For a broader view of what de4dot supports, check the de4dot supported obfuscators list before you promise a full clean to yourself or to a team.

Frequently Asked Questions

Can de4dot clean all Agile.NET files?

No. Many common Agile.NET patterns can be cleaned, but results depend on the version and settings used. Detection first gives the most realistic expectation.

Does cleaning change the original file?

No, de4dot normally writes a new cleaned file. Still, work on a copy so you can return to the original protected file at any time.

Why do some names stay generic after cleaning?

Original names may have been removed during protection, so de4dot keeps safe generic names to keep the code valid. The logic may still be readable even when names are not.

What if the cleaned file will not run?

Check dependencies, test in isolation, and try a conservative run without renaming. If it still fails, use the cleaned file for reading only and keep the original for reference.

Should I analyse an unknown Agile.NET file on my main computer?

No. Use a virtual machine or another isolated system, and only analyse files you have permission to examine.

Cleaned carefully, an Agile.NET file becomes much easier to work with: detect first, back up, clean simply, inspect honestly, and record what remains.

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top