A sophisticated phishing campaign exploiting Microsoft 365's Direct Send feature has compromised over 70 organizations across multiple sectors in the U.S. since May 2025. This attack vector bypasses traditional email security measures by leveraging a legitimate Microsoft protocol, making it particularly dangerous for businesses relying on Office 365 for communication.

Understanding the Direct Send Vulnerability

Microsoft's Direct Send protocol allows applications and devices to send emails directly to Office 365 mailboxes without authentication through SMTP. While designed for legitimate purposes like multifunction printers sending scans, attackers have weaponized this feature to:

  • Bypass spam filters by appearing as internal mail
  • Evade SPF/DKIM/DMARC checks
  • Deliver malicious payloads with high success rates

Recent attacks have combined this technique with QR code phishing (quishing), where victims are redirected to credential-harvesting pages mimicking Microsoft login portals.

How the Attack Works (Technical Breakdown)

  1. Infrastructure Setup: Attackers register domains similar to target organizations
  2. Direct Send Abuse: They configure these domains to send through Microsoft's SMTP relay servers
  3. Payload Delivery: Phishing emails appear to come from internal addresses (@company.onmicrosoft.com)
  4. Social Engineering: Messages typically reference urgent matters requiring immediate action

Current Impact and At-Risk Organizations

According to Microsoft Threat Intelligence:

Sector % of Attacks Common Lures Used
Healthcare 32% Patient records access
Financial Services 28% Wire transfer approvals
Education 19% Password expiration notices
Government 12% Security clearance updates
Other 9% Various internal comms

7 Critical Mitigation Steps

1. Restrict Direct Send Permissions

Set-TransportConfig -SmtpClientAuthenticationDisabled $true

2. Implement Mail Flow Rules

Create Exchange Online rules to:
- Flag external emails pretending to be internal
- Block messages with suspicious headers
- Quarantine emails containing QR codes

3. Enforce Conditional Access Policies

Configure Azure AD to:
- Require MFA for all email access
- Block legacy authentication protocols
- Implement device compliance checks

4. Enhance Email Authentication

  • Configure strict SPF records ("-all")
  • Enable DKIM signing for all domains
  • Implement DMARC with p=reject policy

5. User Awareness Training

Focus on:
- Identifying spoofed internal addresses
- QR code phishing dangers
- Proper reporting procedures

6. Advanced Threat Protection

Enable:
- Safe Links for URL scanning
- Safe Attachments for content inspection
- Anti-phishing policies with impersonation protection

7. Continuous Monitoring

  • Review Message Trace logs daily
  • Set alerts for suspicious send patterns
  • Monitor for new domain registrations mimicking yours

Microsoft's Response and Updates

As of July 2025, Microsoft has:

  • Released new Exchange Online protections
  • Updated Threat Explorer with Direct Send detection
  • Added educational materials to the Security Center

However, organizations must still implement additional controls as these measures don't fully prevent exploitation.

Long-Term Security Recommendations

Adopt a Zero Trust approach for email security:

  1. Verify Explicitly: Treat all messages as potentially malicious
  2. Least Privilege: Restrict mailbox permissions
  3. Assume Breach: Deploy continuous verification
  4. Unified Security: Integrate email protection with endpoint/cloud security

Case Study: Successful Attack Prevention

A Midwest hospital system avoided compromise by:

  • Implementing mail flow rules blocking external senders using onmicrosoft.com
  • Running simulated phishing tests monthly
  • Deploying AI-based anomaly detection

Their security team detected and stopped 14 attempted Direct Send attacks in June alone.

Future Outlook

Security experts predict:

  • More sophisticated Direct Send variants emerging
  • Increased targeting of supply chain partners
  • Potential regulatory action regarding SMTP relay security

Organizations using Microsoft 365 should treat this as an ongoing threat requiring layered defenses rather than a one-time fix.