Security

ASCII Smuggling Phishing Evasion Hits Microsoft 365

3 min read

Summary

Microsoft researchers observed a high-volume phishing campaign using invisible Unicode tag characters, known as ASCII smuggling, to evade email filters in finance-themed lures. The technique, previously associated with AI prompt injection, shows how AI-era evasion methods are now crossing into traditional phishing, making layered email security and hunting more important for defenders.

Need help with Security?Talk to an Expert

Introduction

Microsoft has uncovered a notable shift in attacker behavior: a technique made popular in AI prompt injection research is now being used in mainstream phishing campaigns. For Microsoft 365 and security teams, this matters because it shows how evasions developed for AI systems can quickly become practical tools for email-based attacks.

What is new

Microsoft Security Research observed a large phishing campaign using invisible Unicode tag characters from the U+E0000 to U+E007F range. This method, called ASCII smuggling, lets attackers split or hide lure words such as “funding” so that the text appears normal to users but may be parsed differently by detection systems.

Key findings include:

  • The activity was first surfaced through Microsoft Defender for Office 365 prompt injection protection research.
  • Signature hits spiked sharply on February 9, 2026.
  • Volume jumped from about 21,000 messages on February 8 to more than 1.3 million the next day.
  • Peak volume exceeded 2.3 million messages on February 11.
  • The campaign largely followed a weekday-only sending pattern for roughly three months.
  • Microsoft linked the activity to a broader finance-themed phishing campaign using around 150 sender domains.

Why this matters for defenders

This finding highlights an important security trend: techniques first discussed in AI red-teaming and prompt injection are now being repurposed for classic phishing evasion. In this case, the same invisible Unicode characters that can hide instructions from humans while exposing them to AI models were used to obscure phishing keywords from email filters.

Microsoft also noted that detection did not rely on a single Unicode-specific rule alone. Instead, layered protections in Defender for Office 365 flagged most messages, which reinforces the value of defense in depth rather than depending on one signature.

Impact on IT administrators

For administrators, this means email hunting and detection logic should account for unusual Unicode usage, especially the Unicode Tags block. However, tuning is essential because legitimate content can also trigger detections, such as subdivision flag emojis for England, Scotland, and Wales.

Security teams should expect more crossover between AI-related attack research and traditional threat activity. Techniques that once seemed niche may quickly appear in large-scale commodity phishing.

Next steps

  • Review Defender for Office 365 detections and hunting queries for suspicious Unicode tag usage.
  • Validate that layered phishing protections are enabled and monitored.
  • Train analysts to recognize invisible-character obfuscation as a phishing signal.
  • Watch for finance-themed lure campaigns and unusual weekday-volume patterns.
  • Revisit email security controls to ensure they normalize or inspect hidden Unicode content where possible.

As attackers adapt AI-era evasion methods for email, defenders should update hunting strategies now rather than wait for these techniques to become standard practice.

Need help with Security?

Our experts can help you implement and optimize your Microsoft solutions.

Talk to an Expert

Stay updated on Microsoft technologies

ASCII smugglingphishingMicrosoft Defender for Office 365Unicodeemail security

Related Posts

Security

Microsoft Digital Defense Report 2026: Key Security Insights

Microsoft's 2026 Digital Defense Report highlights how AI and growing system interconnectedness are reshaping both cyberattacks and defense strategies. The report emphasizes that organizations must secure AI, identities, data, and cloud environments together while improving signal correlation across tools to detect modern threats faster.

Security

Government Cyber Risk in 2026: Microsoft’s 5 Priorities

Microsoft says government agencies were the most targeted sector in 2026, accounting for 27% of observed cyber threat activity. The company urges public-sector leaders to focus on five resilience priorities, including faster response, AI security, bidirectional information sharing, and planning for incidents that spread across suppliers and essential services.

Security

Microsoft Ignite 2026 Security Guide: Key Sessions

Microsoft has published its security guide for Microsoft Ignite 2026, highlighting AI-first security themes, a dedicated Security Pre-Day, and technical sessions focused on securing identities, data, devices, clouds, and AI agents. For IT and security teams, the event offers an early look at Microsoft’s roadmap and practical guidance for building an AI-ready security strategy.

Security

CVE-2026-73570: Zimbra Mail Server Exploitation

Microsoft is tracking active exploitation of CVE-2026-73570, an unauthenticated command injection flaw affecting internet-facing Zimbra mail servers with the optional zimbra-snmp package installed and SNMP notifications enabled. The issue can lead to web shell deployment, privilege escalation, mailbox data theft, and persistent remote access, making immediate patching and configuration review critical for administrators.

Security

Phishing Abuses RMM Tools for Persistent Access

Microsoft security researchers observed phishing campaigns in July 2026 that used a legitimate MSP360 RMM installer disguised as meeting invites, PDF updates, and other lures to gain remote access. Attackers then deployed ConnectWise ScreenConnect for redundant persistence, highlighting the need for tighter controls on remote management tools and better detection of unapproved RMM activity.

Security

Azure DevOps Attack Path Exposed in New DART Report

Microsoft’s latest DART cyberattack report shows how a single compromised identity was used to access Azure DevOps, alter pipelines, and harvest Kubernetes credentials. The case highlights how tightly connected identity, DevOps, and cloud environments can let attackers move far beyond source code, making stronger identity and pipeline controls essential.