Option to dump rename mappings to json, load the mapping and keep identifiers that contain ASCII - #1033
Open
Treeed wants to merge 5 commits into
Open
Option to dump rename mappings to json, load the mapping and keep identifiers that contain ASCII#1033Treeed wants to merge 5 commits into
Treeed wants to merge 5 commits into
Conversation
added 5 commits
September 10, 2026 01:48
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When trying different transformers and their effects it can become quite annoying that the normalizers are not stable in between deobfuscations, such that comparing to another version is impossible. On the other hand, it is almost impossible to work on some deobfuscated sources, that use only short Unicode symbols, without normalizing (try telling apart twenty identical looking chinese characters).
The option to dump the mapping and load it for another deobfuscation run solves that problem and makes it possible to trace back identifiers in the original source after working on the normalized source for a bit.
A related issue is that normalizing may remove meaningful identifiers that the obfuscator left untouched intentionally (e.g. identifiers used by reflection or overriding native classes). In the case of unicode identifiers these are easy to tell apart since most people and the standard libraries use ASCII for their identifiers. For that reason, an option to retain identifiers containing ASCII is introduced.
In the process, a related bug in the duplicate renamer was fixed, where a class could be silently dropped if the renamer picked a new name that already existed in the original source. See the tests for exactly what cases are covered