Microsoft has uncovered a large-scale phishing campaign that repurposed an evasion technique from AI prompt injection research, known as "ASCII smuggling," to bypass email security filters. Threat actors sent millions of finance-themed phishing emails by inserting invisible Unicode characters into keywords. This technique, which uses characters from the deprecated Unicode Tags block (U+E0000–U+E007F), splits words like funding into fun[invisible]ding at the code level, defeating simple keyword-based detection while remaining visually unchanged to the recipient. The campaign, linked to a U.S. Small Business Administration (SBA) themed operation, peaked at 2.37 million messages per day and demonstrates the ongoing adaptation of novel evasion methods by cybercriminals.
The campaign was discovered by Microsoft researchers using a hunting signature originally designed to detect hidden AI prompts. They observed a massive spike in activity starting February 9, 2026, with daily email volumes soaring from ~21,000 to over 1.3 million. The attackers' goal was to lure victims with SBA-themed financial offers to a landing page designed to harvest detailed business and financial information. The operation leveraged the ActiveCampaign marketing platform for distribution, a tactic previously documented by security firm Fortra. While Microsoft Defender for Office 365 successfully blocked over 99% of the messages through its layered defenses, the sheer volume and novelty of the technique highlight a significant threat.
The core of the attack is the abuse of the Unicode Tags block. These characters are designed to be language tags and are not meant to be rendered, making them invisible in most email clients and web browsers.
loan, and inserts one or more tag characters, e.g., l<U+E006F>oan. To a filter looking for the exact string loan, this modified version is not a match. To the human user, the word loan appears perfectly normal.T1027 - Obfuscated Files or Information. The ultimate goal is to deliver a malicious link, which falls under T1566.002 - Spearphishing Link.This incident shows a crossover of techniques between different domains of cybersecurity. A method developed to hide malicious instructions in AI prompts has been effectively repurposed for a classic, high-volume phishing campaign. This demonstrates that threat actors are constantly innovating and borrowing ideas from other fields.
No specific file hashes, IP addresses, or domains were mentioned in the source articles.
To detect this specific evasion technique, security teams should focus on the content of emails:
[\uE0000-\uE007F]Email Gateway LogsSBA Loan ThemesD3-FA: File Analysis).U+E0000–U+E007F range within email bodies and headers.rule Detect_ASCII_Smuggling_Unicode_Tags {
strings:
$tag_char = /[\uE0000-\uE007F]/ wide
condition:
$tag_char
}
D3-NTA: Network Traffic Analysis).M1021 - Restrict Web-Based Content.M1017 - User Training).This mitigation includes advanced content filtering techniques, such as normalizing text to remove obfuscation characters before analysis.
Training users to be skeptical of unsolicited emails, especially those with financial offers, remains a critical layer of defense.
Layered defenses, including sender reputation and behavioral analysis, can help catch campaigns that evade simple content filters.
The core of the ASCII smuggling technique is to hide keywords from content filters. The direct countermeasure is to enhance file analysis capabilities at the email gateway. Specifically, the email security solution must be configured to normalize email body content before applying detection rules. This normalization process involves identifying and stripping or replacing non-rendering characters, such as those from the Unicode Tags block (U+E0000–U+E007F). Once the text is normalized, the word 'fun<U+E0064>ing' becomes 'funding', and standard keyword-based detection rules will trigger successfully. Security teams should verify with their email security vendor that this type of Unicode normalization is performed by default or configure a custom pre-processing script to do so. This proactive analysis neutralizes the entire evasion technique.
Even if an ASCII-smuggled email bypasses content filters, the attack can be stopped by analyzing the destination of the phishing link. Modern email security gateways should be configured with URL rewriting and time-of-click protection. This technology replaces all links in an incoming email with a unique, redirected link that goes through the security vendor's proxy. When a user clicks the link, the destination is analyzed in real-time for phishing kits, malicious scripts, or poor reputation. If the site is deemed malicious, the user is blocked from accessing it. This provides a critical safety net, protecting users who might be tricked by the lure text of the email. It shifts the detection from the obfuscated email body to the unobfuscated, malicious infrastructure.
This campaign was noted to be high-volume and distributed via the ActiveCampaign marketing platform. While the content itself was obfuscated, the sending infrastructure provides another opportunity for detection. Email security systems should analyze sender reputation based on factors beyond the IP address, including the sending domain's age, its history (has it been associated with spam or phishing before?), and whether it is a legitimate marketing platform being abused. A sudden spike in emails from a specific marketing service with financial themes should raise the reputation risk score. Implementing DMARC, DKIM, and SPF and enforcing a 'reject' policy on failures helps validate sender identity and block spoofed emails that are often part of such campaigns.
Microsoft observes a massive spike in ASCII smuggling phishing activity, with daily message volume jumping to over 1.3 million.
The high-volume phishing campaign drops off sharply.

Cybersecurity professional with over 10 years of specialized experience in security operations, threat intelligence, incident response, and security automation. Expertise spans SOAR/XSOAR orchestration, threat intelligence platforms, SIEM/UEBA analytics, and building cyber fusion centers. Background includes technical enablement, solution architecture for enterprise and government clients, and implementing security automation workflows across IR, TIP, and SOC use cases.
CyberNetSec.io uses automation to assist source monitoring, deduplication, observable extraction, and structured intelligence generation. Published analysis follows human-defined editorial standards and adds defensive context including MITRE ATT&CK, D3FEND, STIX, and Sigma where applicable. Read our editorial policy.
Help others stay informed about cybersecurity threats
Every tactic, technique, and sub-technique used in this threat has been identified and mapped to the MITRE ATT&CK framework for consistent, actionable threat language.
Observables and indicators of compromise (IOCs) have been extracted and cataloged. Risk has been assessed and correlated with known threat actors and historical campaigns.
Detection rules, incident response steps, and D3FEND-aligned mitigation strategies are included so your team can act on this intelligence immediately.
Structured threat data is packaged as a STIX 2.1 bundle and can be visualized as an interactive graph — relationships between actors, malware, techniques, and indicators.
Sigma detection rules are derived from the threat techniques in this article and can be converted for deployment across any major SIEM or EDR platform.