An interesting attempt, Claude. However, your promot is missing an important step to measure effectiveness against humans: wait 40-60 years for your vision to degrade naturally, and check the confusables again, preferably on a small phone screen. Bonus points if you can find someone with visual disabilities from birth. Obviously most attacks aren't pixel-perfect, but that's not the point, all you need to confuse are…
I rendered 1,418 confusables over 230 fonts. Most aren't confusable to the eye
41–50 of 60 posts
Re: I rendered 1,418 confusables over 230 fonts. Most aren't confusable to the eye
#42Was that the intention?
Re: I rendered 1,418 confusables over 230 fonts. Most aren't confusable to the eye
#43Re: I rendered 1,418 confusables over 230 fonts. Most aren't confusable to the eye
#44> a string like “аpple.com” with Cyrillic а (U+0430) is pixel-identical to “apple.com” in 40+ fonts. The user, the browser’s address bar, and any visual review process all see the same pixels. This is not theoretical. It is a measured property of the font files shipping on every Mac.
Current implementations of "Computer Use" Agentic AI tools mostly use visuals -- screenshotting of a computer screen and interpreting it.
These pixel-dentical character pairs will be a straight failure mode for those automations and could possibly be a threat vector if crafted well.
Re: I rendered 1,418 confusables over 230 fonts. Most aren't confusable to the eye
#45> 82 pairs are pixel-identical > a string like “аpple.com” with Cyrillic а (U+0430) is pixel-identical to “apple.com” in 40+ fonts. The user, the browser’s address bar, and any visual review process all see the same pixels. This is not theoretical. It is a measured property of the font files shipping on every Mac. Current implementations of "Computer Use" Agentic AI tools mostly use visuals -- screenshotting of a com…
Re: I rendered 1,418 confusables over 230 fonts. Most aren't confusable to the eye
#46I did run into some issues in early versions on when characters in Linux commands or visible web addresses were replaced. Fortunately the source docs were HTML, and it was easy to exclude code or pre nodes when rendering.
I thought this was so clever, but the leaker was never caught using it, to the best of my knowledge.
Re: I rendered 1,418 confusables over 230 fonts. Most aren't confusable to the eye
#47Re: I rendered 1,418 confusables over 230 fonts. Most aren't confusable to the eye
#48Maybe not at super large font sizes. But even lowercase i and l are easy enough to confuse at a glance mid-word in most sans-serif fonts, not to mention uppercase I and lowercase l. You don’t even need “confusable” glyphs to create a domain name that will stand up to a casual visual confirmation from a busy user in a phishing context.
This was like 1998-2003, and non technical people were doing it too. I think I am the only one from that friend group who would even consider that as something to watch out for.