Email Obfuscation Edit
HitokageTaka opened this issue · comments
Identify and 'refang' emails formatted as follows:
identifier[@]domain[.com]
Thanks for the issue! This should be doable.
If you don't mind me asking, where are you seeing emails in this format?
Thank you for the quick reply! In an information sharing group my
organization is a part of. I could probably provide you with 100 different
“defanging” techniques these analysts try.
Another for your consideration could be another common defang technique of
“google DOT com”. They will literally type “dot” or “at” rather than a [.]
or [@].
Again thanks for the prompt reply!
…On Fri, Sep 14, 2018 at 1:14 PM Ryan Shipp ***@***.***> wrote:
Thanks for the issue! This should be doable.
If you don't mind me asking, where are you seeing emails in this format?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#22 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ApRe4wYNM4PgtN03_Ij9I3xA8pfCX_-1ks5ua_H8gaJpZM4Wpps3>
.
Interesting, thanks. If you have more defangs we're not catching, definitely feel free to share them.
I'll try to up the robustness of our email support in general. It's a bit weaker than our URL support just because I don't often see emails shared, and didn't realize it was something people needed.
Just published v1.10.0 to PyPI, that should catch everything you mentioned and more.
Let me know if there are any that still don't get picked up, or any false positives/other issues!