Microsoft’s 2026 Digital Defense Report puts QR code phishing at more than 145 million attacks detected by Defender for Office 365 between July 2025 and June 2026 1. The number is large. The part I plan around is smaller and harder to file: the payload rides in an attachment, and the click happens on a phone that has none of my controls on it.

The number moved, then the format moved again

Microsoft’s Q2 2026 numbers show the shape. QR attacks peaked at 18.7 million in March, fell 7 percent in April to 17.4 million, then dropped 38 percent in May and 22 percent in June to 8.3 million 2. Microsoft ties much of that decline to its disruption of the Tycoon2FA platform, with phishing volume linked to it down 92 percent from pre-disruption averages 2.

Volume is the easy half. The delivery format rotated while the volume fell. PDF attachments carried 79 percent of QR attacks in April, 59 percent in May, and 58 percent in June. DOC and DOCX files moved the other way, reaching 40 percent by June 2. Codes embedded in the message body, which had jumped 336 percent in March, dropped to near zero across the quarter 2.

That rotation matters more to me than the monthly total. A rule I write as “PDF with a QR code inside” covered 79 percent of what arrived in April and 59 percent a month later 2. The durable unit is an attachment whose content is a picture of a link, whatever the container claims to be.

Link protection works on URLs the message carries. In Microsoft’s implementation, Safe Links scans inbound mail during mail flow, rewrites or wraps the URL with the safelinks prefix, and re-checks it when someone clicks 3. Wrapping needs a string to wrap. A QR code is a bitmap, so until something decodes the image there is no URL in the message to touch.

Microsoft’s answer to that arrived in 2024, when the company described image processing at the initial stage of mail flow that extracts and logs URLs hidden within QR codes 4. That work matters, and I want it running on every message, but it happens at delivery, inside my mail path, and the phone is not part of that path.

The scan happens on a device with no agent, no proxy, and no policy from me, and the page opens in a browser my controls never see. Microsoft’s research on the pattern notes that warning signs a person might catch on a large screen can go unnoticed on a phone 4. My tooling inspects the message, and the click lands on a device I never see, so the rest of my work starts where the mail evidence ends.

The attachment is the payload

The same report records that 89 to 95 percent of email phishing attachments led to a credential theft effort 1. That matches what reaches my queue. The attachment is a step in a sign-in chain, and the document is the wrapper around it.

Microsoft’s writeup of an April campaign describes the pattern: the attacker proxies the authentication session and captures tokens that can give immediate account access, which bypasses MFA that is not phishing-resistant 5. A scanned code that lands on one of those pages puts a working session in someone else’s hands, and the password reset I reach for first leaves it running.

What I ask when one lands

The first number is delivery and reach. A quarantined message is a policy result. A message delivered to forty people is a list of people who might scan.

Extraction comes next. If the mail platform decoded the code, that URL sits in telemetry, and I can search for other recipients and push the URL to a block list. If the person scanned with a personal phone, no click telemetry exists on my side, and the user’s report is the only sensor that fired.

The identity trace comes after that. A scan leaves its mark at the identity layer rather than the mail layer: a session from a mobile network at an hour that matches when the person says they were reading mail. That check finds the scan nobody reported.

The recipient list closes it out. A shared subject line, a hand-built recipient list, and the sender’s delivery history tell me whether I hold a ticket or a purge.

On a confirmed scan, I ask for session revocation first, then a password reset, then a look at what the account touched in the gap. Tokens outlive passwords, so the revocation request goes in the same line as the reset, and the review of what the account reached follows once the session is dead.

What I would change, in order

My first ask goes to the mail side: treat an attachment that carries a code as a link when it arrives, not only when someone clicks. Microsoft lists minimal to no text as a QR pattern, because it removes signal from the message 4. A near-empty body with one PDF from a first-contact sender is a shape I would rather detonate than deliver.

The second ask is identity. Phishing-resistant authentication on the accounts that matter is the control that survives a phone camera, because AiTM flows bypass MFA that is not phishing-resistant 5. Session lifetime is the other half of that request, because a stolen token is worth its remaining validity.

The third is reporting speed. If the person who scanned the code is the only sensor, the report has to work from a phone in two taps. Post-delivery purge helps a message still sitting unread in a mailbox, and Microsoft’s guidance on zero-hour auto purge covers that case 2. It does nothing for a code already scanned, which is why I put reporting ahead of cleanup in the list I hand over.

The number will move again next quarter. I cannot put an agent on a personal phone, so the work lands where I do have a say: what reaches an inbox as an attachment, and how fast a session dies once someone says they scanned something.


  1. Microsoft. (2026). Microsoft Digital Defense Report 2026. https://www.microsoft.com/en-us/corporate-responsibility/topics/cybersecurity/reports/microsoft-digital-defense-report/ ↩︎ ↩︎

  2. Microsoft Threat Intelligence. (2026, July 23). Email threat landscape: Q2 2026 trends and insights. Microsoft Security Blog. https://www.microsoft.com/en-us/security/blog/2026/07/23/email-threat-landscape-q2-2026-trends-and-insights/ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎

  3. Microsoft. (2026, October 14). Safe Links in Microsoft Defender for Office 365. Microsoft Learn. https://learn.microsoft.com/en-us/defender-office-365/safe-links-about ↩︎

  4. Chitrakar, R. (2024, November 4). How Microsoft Defender for Office 365 innovated to address QR code phishing attacks. Microsoft Security Blog. https://www.microsoft.com/en-us/security/blog/2024/11/04/how-microsoft-defender-for-office-365-innovated-to-address-qr-code-phishing-attacks/ ↩︎ ↩︎ ↩︎

  5. Microsoft Threat Intelligence. (2026, May 4). Breaking the code: Multi-stage ‘code of conduct’ phishing campaign leads to AiTM token compromise. Microsoft Security Blog. https://www.microsoft.com/en-us/security/blog/2026/05/04/breaking-the-code-multi-stage-code-of-conduct-phishing-campaign-leads-to-aitm-token-compromise/ ↩︎ ↩︎