by DavidJacobson

DavidJacobson / SafeText

Script to remove homoglyphs and zero-width characters to allow for safe distribution of documents fr...

130 Stars 11 Forks Last release: Not found MIT License 24 Commits 0 Releases

Available items

No Items, yet!

The developer of this repository has not created any items for sale yet. Need a bug fixed? Help with integration? A different license? Create a request here:


Tool to sanitize text to allow for safe distribution of documents from anonymous sources by removing zero-width characters and homoglpyhs.

Individuals attempting to leak an email or other text file face the risk of identification through fingerprinting. Fingerprinting often occurs when the original distributor of the document has embedded some form of a canary. For example, Elon Musk's email in 2008 in response to leaks featured slightly different wording for each employee. This tactic was realized by the employees, and failed. An easier tactic that is also employed, is the presence of nearly invisible changes to the text. SafeText is designed to identify and remove these changes. Specifically this tool will remove homoglyphs, zero-width characters, and other subtle characters. This tool will also attempt to identify unique spelling of words that could give away an individual's location.


To use SafeText, call:

python inputfile
Example output is: ```shell λ python TestFile.txt [] Cleaning TestFile.txt to ... [!] FOUND HOMOGLYPHIC CHARACTER CYRILLIClargeH ON LINE 1 The message said: "(Н)ey, let's hang out!" [!] FOUND a SPACE ON LINE # 2 LoremIpsumDolorSit [!] WARNING - Use of spelling (colour) that identifies country on line 3 [!] FOUND HOMOGLYPHIC CHARACTER GREEKB ON LINE 5 [!] FOUND HOMOGLYPHIC CHARACTER GREEKC ON LINE 5 Subject: (Β)udget (Ϲ)uts [*] Output file closed
Note: The relevant characters will be underlined - not enclosed by parentheses. 
SafeText will output to 

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.