<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>Unicode Tags - PhishFort | AI-Powered Brand Protection</title><link>https://phishfort.com/resources/blog/tag/unicode-tags/</link><description>PhishFort delivers agentic brand protection: detecting and eliminating phishing sites, fake apps, and impersonations across every digital channel.</description><generator>Hugo -- gohugo.io</generator><language>en-US</language><lastBuildDate>Tue, 13 Oct 2026 12:00:00 +0000</lastBuildDate><atom:link href="https://phishfort.com/resources/blog/tag/unicode-tags/index.xml" rel="self" type="application/rss+xml"/><item><title>ASCII Smuggling: How Invisible Unicode Bypasses Email Filters</title><link>https://phishfort.com/ascii-smuggling-unicode-phishing-email-evasion/</link><pubDate>Tue, 13 Oct 2026 12:00:00 +0000</pubDate><dc:creator>PhishFort Team</dc:creator><guid>https://phishfort.com/ascii-smuggling-unicode-phishing-email-evasion/</guid><description><![CDATA[<p>ASCII smuggling is a technique that hides invisible Unicode tag characters inside normal words. It was first used to slip hidden instructions past large language models (LLMs) in prompt-injection attacks. In 2026, Microsoft reported attackers using it for mass phishing. One campaign, which peaked at more than 2.37 million emails per day, used invisible characters to break up words often used in phishing emails, such as &ldquo;funding&rdquo;. As a result, email filters let them through and the recipients saw perfectly normal text.</p>]]></description><content:encoded><![CDATA[<p>ASCII smuggling is a technique that hides invisible Unicode tag characters inside normal words. It was first used to slip hidden instructions past large language models (LLMs) in prompt-injection attacks. In 2026, Microsoft reported attackers using it for mass phishing. One campaign, which peaked at more than 2.37 million emails per day, used invisible characters to break up words often used in phishing emails, such as &ldquo;funding&rdquo;. As a result, email filters let them through and the recipients saw perfectly normal text.</p>
<p><strong>Summary</strong></p>
<ul>
<li>The campaign targeted finance and corporate accounts with business loan and credit lures, peaking at over 2.37 million emails per day.</li>
<li>Attackers inserted the invisible Unicode Tag Space character (<code>U+E0020</code>) between the letters of high-signal words such as &ldquo;funding&rdquo;.</li>
<li>Machine learning models and regex filters read the broken word and did not flag it. People saw clean text because the characters do not render.</li>
<li>The trick came from AI red teaming, where it hides prompt injection payloads. It is now a phishing filter bypass.</li>
<li>The fix is Unicode normalization: strip tag characters (<code>U+E0000</code> to <code>U+E007F</code>) before any filter or AI classifier analyzes the text.</li>
</ul>
<p>
















  
  
  
    
    
    

    
    

    
      
      
      
      
      
        
          
          
          
          
        
      
        
          
          
          
          
        
      
        
          
          
          
          
        
      
        
          
          
          
          
        
      
        
          
          
          
          
        
      
      
      

      <picture>
        <source srcset="/img/1791482034712-pasted-image_hu_7ddbc4ce1625fb45.webp 480w, /img/1791482034712-pasted-image_hu_28329e8d7b129b2c.webp 768w, /img/1791482034712-pasted-image_hu_3603ba106db1ad91.webp 1200w, /img/1791482034712-pasted-image_hu_9fd9368c0d8cf9e0.webp 1600w, /img/1791482034712-pasted-image_hu_c1c558670496da26.webp 2000w, /img/1791482034712-pasted-image_hu_cc7bc9db222f1f47.webp 2048w"
                sizes="(max-width: 768px) 100vw, 700px" type="image/webp">
        <img src="/img/1791482034712-pasted-image.png"
          srcset="/img/1791482034712-pasted-image_hu_7ea9affe650f1143.png 480w, /img/1791482034712-pasted-image_hu_78b7b294057dc36.png 768w, /img/1791482034712-pasted-image_hu_7cfcd99935582073.png 1200w, /img/1791482034712-pasted-image_hu_2c3b6fbd6b103389.png 1600w, /img/1791482034712-pasted-image_hu_1f85b713b0983d32.png 2000w, /img/1791482034712-pasted-image.png 2048w"
          sizes="(max-width: 768px) 100vw, 700px"
          alt=""
          
          width="2048" height="1117"
          
          
          loading="lazy"
          >
      </picture>
    
  



</p>
<h2 id="what-is-ascii-smuggling">What is ASCII smuggling?</h2>
<p>ASCII smuggling is the practice of embedding invisible Unicode tag characters alongside visible text, so machines read something different from what people see. Most applications do not display tag characters at all, which makes the hidden content invisible to the reader.</p>
<p>Security researchers first described it as a way to hide instructions inside text sent to AI models. If a model processes the hidden characters, it can follow instructions the user never saw. That is a form of prompt injection.</p>
<h2 id="how-does-ascii-smuggling-bypass-email-filters">How does ASCII smuggling bypass email filters?</h2>
<p>ASCII smuggling bypasses filters by breaking the words they look for, without changing what the reader sees. In the campaign Microsoft documented, it worked in three steps:</p>
<ol>
<li><strong>The ghost character:</strong> attackers placed the Unicode Tag Space (<code>U+E0020</code>) between the letters of a financial keyword, so &ldquo;funding&rdquo; became <code>f[U+E0020]u[U+E0020]n[U+E0020]d[U+E0020]i[U+E0020]n[U+E0020]g</code> in the raw text.</li>
<li><strong>The evasion:</strong> machine learning models and regex rules that analyzed the raw string did not recognize the broken word, so the email passed.</li>
<li><strong>The victim&rsquo;s view:</strong> text rendering engines ignore tag characters, so the recipient saw the normal word &ldquo;funding&rdquo; in a clean, professional email.</li>
</ol>
<p>Older tricks such as zero-width spaces or Cyrillic lookalike letters (homoglyphs) are now widely detected. Unicode tags are a less watched corner of the standard.</p>
<p>
















  
  
  
    
    
    

    
    

    
      
      
      
      
      
        
          
          
          
          
        
      
        
      
        
      
        
      
        
      
      
      

      <picture>
        <source srcset="/img/1791482037858-pasted-image_hu_cebc6b73e20b943c.webp 480w, /img/1791482037858-pasted-image_hu_2a9ba9ba036e3fcc.webp 668w"
                sizes="(max-width: 768px) 100vw, 700px" type="image/webp">
        <img src="/img/1791482037858-pasted-image.png"
          srcset="/img/1791482037858-pasted-image_hu_8ce6ee9b8b356470.png 480w, /img/1791482037858-pasted-image.png 668w"
          sizes="(max-width: 768px) 100vw, 700px"
          alt=""
          
          width="668" height="1024"
          
          
          loading="lazy"
          >
      </picture>
    
  



</p>
<p style="text-align: center;"><em>Mock example of an ASCII-smuggled phishing email, created for illustration. Not a real attack.</em></p>
<h2 id="what-are-unicode-tag-characters">What are Unicode tag characters?</h2>
<p>Unicode tags are a block of non-rendering characters, from <code>U+E0000</code> to <code>U+E007F</code>, created to tag text with language information. Today they are mostly used inside some flag emoji sequences. When used on their own, most apps show nothing, which is exactly what makes them useful for hiding content.</p>
<h2 id="why-does-ascii-smuggling-matter-for-security-teams">Why does ASCII smuggling matter for security teams?</h2>
<p>ASCII smuggling matters because it shows techniques moving from AI attacks to traditional phishing. A method built to manipulate LLMs now defeats perimeter email security. As more organizations use AI to classify email, read documents and run agents, any text pipeline that does not clean its input is exposed to both filter evasion and prompt injection.</p>
<h2 id="how-can-organizations-defend-against-ascii-smuggling">How can organizations defend against ASCII smuggling?</h2>
<p>The core defense is Unicode normalization before inspection. Practical steps:</p>
<ul>
<li><strong>Normalize at the gateway:</strong> configure secure email gateways (SEGs) and AI pipelines to strip non-rendering tag characters (U+E0000 to U+E007F) before any spam, phishing or AI classification runs.</li>
<li><strong>Check the raw source:</strong> if a financial email feels wrong but shows no warnings, open &ldquo;View original&rdquo; or the raw message. Smuggled words appear as escape codes such as <code>\u{E0020}</code>.</li>
<li><strong>Do not trust clean formatting:</strong> an email that passed filters and looks perfect can still be malicious. Verify high-risk financial requests through a bookmark or a known phone number.</li>
<li><strong>Apply the same rule to AI tools:</strong> clean text before it reaches LLMs, copilots or agents, so hidden instructions cannot steer them.</li>
</ul>
<h2 id="how-phishfort-helps">How PhishFort helps</h2>
<p>Filter evasion is one way phishing reaches inboxes. <a href="https://phishfort.com/product/abuse-mailbox/" target="_blank" rel="noopener"><u>PhishFort Abuse Mailbox</u></a> turns phishing that employees and customers report into investigation and takedown, so the sites and accounts behind a campaign come down even when a message slipped past the filters.</p>
<h2 id="jargon-buster">Jargon buster</h2>
<ul>
<li><strong>ASCII smuggling:</strong> embedding hidden Unicode tag characters alongside visible text to trick machine readers without changing what people see.</li>
<li><strong>Unicode tags block (<code>U+E0000</code> to <code>U+E007F</code>):</strong> a set of non-rendering characters created for language tagging and now used in some flag emojis. Most apps display them as nothing.</li>
<li><strong>Unicode normalization:</strong> cleaning and stripping invisible control and tag characters from text before it reaches security filters, regex rules or AI classifiers.</li>
<li><strong>Prompt injection:</strong> hiding instructions in content an AI model processes, so the model does something its user did not ask for.</li>
</ul>
<h2 id="frequently-asked-questions">Frequently asked questions</h2>







<div class="faq-plain">
  













<p class="faq-plain__q"><strong>What is ASCII smuggling?</strong></p>
<div class="faq-plain__a pf-prose">
  ASCII smuggling hides invisible Unicode tag characters inside text, so computers and AI models read different content from what people see. It started as a prompt injection technique and is now used to evade email filters.
</div>















<p class="faq-plain__q"><strong>How does ASCII smuggling evade phishing filters?</strong></p>
<div class="faq-plain__a pf-prose">
  Attackers insert invisible characters such as <code>U+E0020</code> between the letters of keywords like &ldquo;funding&rdquo;. Filters that read the raw text do not recognize the word, while the recipient sees it normally.
</div>















<p class="faq-plain__q"><strong>How do you detect ASCII smuggling in an email?</strong></p>
<div class="faq-plain__a pf-prose">
  View the raw message or original source. Hidden tag characters appear as escape codes such as <code>\u{E0020}</code> between letters. Security teams should normalize Unicode at the email gateway before inspection.
</div>















<p class="faq-plain__q"><strong>Is ASCII smuggling the same as prompt injection?</strong></p>
<div class="faq-plain__a pf-prose">
  No, but they are related. Prompt injection is the goal of hiding instructions for an AI model. ASCII smuggling is one way to hide them. In phishing, the same hiding trick is used to fool email filters instead of AI models.
</div>



</div>


<h2 id="sources">Sources</h2>
<ul>
<li><a href="https://www.microsoft.com/en-us/security/blog/2026/09/03/ascii-smuggling-crosses-over-from-ai-prompt-injection-to-phishing-evasion/" target="_blank" rel="noopener noreferrer nofollow">Microsoft Security Blog: ASCII smuggling crosses over from AI prompt injection to phishing evasion (September 3, 2026)</a></li>
</ul>
]]></content:encoded><category>Cybersecurity</category><category>phishing</category><category>security</category><category>ASCII smuggling</category><category>Unicode tags</category><category>prompt injection</category><category>phishing evasion</category><category>email security</category><category>secure email gateway</category><category>Unicode normalization</category><category>AI security</category></item></channel></rss>