[IC] - ๐—›๐˜‚๐—ป๐˜๐—ถ๐—ป๐—ด ๐—œ๐—ป๐˜ƒ๐—ถ๐˜€๐—ถ๐—ฏ๐—น๐—ฒ ๐—จ๐—ป๐—ถ๐—ฐ๐—ผ๐—ฑ๐—ฒ ๐—ถ๐—ป ๐—˜๐—บ๐—ฎ๐—ถ๐—น๐˜€

For years, when hunting phishing emails, I have mainly focused on what the user sees inside of it. But I think AI agents are going to change this. An email may soon have two audiences: Human + AI Agent. And they may not always see exactly the same thing. In this new KQL, I explore a simple example: invisible Unicode characters. Microsoft and Micro<U+200B>soft may look the same to us, but not necessarily to a detection, filter, parser or AI agent. For attackers, this difference can be interesting as a way to obfuscate content and potentially evade keyword-based detections or other systems processing the text. I hunt these patterns in email and add context around them. Because attackers will not only write emails for us. They will(are) start writing emails for our agents too.