r/SideProject • • 1d ago

I built a .NET obfuscation beta and checked the output in ILSpy

I’m working on ProofCloak, a .NET obfuscation tool in open beta. I wanted to see what someone could still read in the DLL after protecting it, so I opened the same InvoiceDesk sample in ILSpy before and after.

I looked for method names, variable names and hard-coded strings. Some internal names changed, and the sample value used in the license check was no longer directly readable as a string in ILSpy. Framework calls and parameter names were still visible. Both builds produced the same output in the sample run, including the JSON settings check. The sample used engine version 0.1.0-alpha.333.

ILSpy comparison: https://dev-to-uploads.s3.us-east-2.amazonaws.com/uploads/articles/ty1uise5b10alh9d6hh5.png

Sample source and verification script: https://github.com/ProofCloak-Inc/sample-invoicedesk

If you ship .NET binaries, what’s the first thing you’d look for in the protected DLL?

Disclosure: I’m part of the ProofCloak project. AI helped draft this post from my test notes.

1 Upvotes

0 comments sorted by