Email security

QR-code phishing (quishing): how it works and how to spot it

QR codes in emails and letters let phishing skip your filters and land on unprotected phones. How quishing works and what to change in your business.

Your bookkeeper gets an email from "Microsoft 365": the multi-factor authentication on their account expires today, and they need to scan the QR code to keep access. There's no link to hover over and no attachment to worry about, just a square of black and white dots. They pick up their phone, scan it, and sign in on a page that looks exactly like Microsoft's.

That's QR-code phishing, often called quishing. It isn't new: Safeonweb first reported phishing with a QR code instead of a link in 2022. But it has become a standard tool in phishing campaigns against businesses, and it lands in a year when Belgians reported more than 3.6 million phishing messages to Safeonweb in the first three months alone.

This article explains why the trick works so well, what it's usually after, and the changes that make your team much harder to catch.

Why a QR code works better than a link

A phishing link in an email can be checked. Your mail filter can scan it, your browser can block it, and a careful user can hover over it to see the real address. A QR code is an image. Until someone decodes it, it's just pixels.

The bigger reason is where the click happens. Microsoft's own threat hunters describe the typical pattern: the user scans the code on their personal, unmanaged phone, which sits outside the protection the company has on its laptops and its mailbox. The email arrived in a protected environment. The sign-in happens on a device nobody manages.

And phones make checking hard. Safeonweb warned early on that when you scan a QR code, you can't immediately see where it leads, and a long web address on a small screen is easy to skim past.

What the attackers are after

In business email, the goal is usually your Microsoft 365 account. According to Microsoft, most QR-code campaigns it investigated send the user to an adversary-in-the-middle (AiTM) phishing page: a fake sign-in page that passes everything to the real Microsoft page and keeps the signed-in session. The attacker then uses that session for business email compromise and data theft.

That means a text code or an approved push notification doesn't save you. Our article on phishing-resistant MFA explains why, and why passkeys do.

The lures are familiar business admin:

  • "Your MFA is expiring, scan to re-register"
  • a document to sign, a voicemail or a shared file
  • a payslip or HR notice that seems to come from a social secretariat
  • a tax refund: one Belgian warning concerned a fake FOD Financiën message asking people to scan a QR code to confirm their bank details

QR codes also turn up outside email. The FBI has warned about criminals placing stickers with their own codes over legitimate ones, for example on payment terminals, so the victim lands on a fake page asking for login or card details.

How to spot a quishing attempt

Most quishing emails fail the same checks as any phishing email. The QR code is just the delivery method.

What to do:

  • Ask why it's a QR code. Legitimate services rarely ask you to scan a code in an email to keep your account working. A QR code in a message you read on your computer, asking you to sign in, is a red flag on its own.
  • Check the sender and the pressure. An unfamiliar sender, a deadline of "today" and a threat of losing access are the classic signs.
  • Read the address before you open it. Most phone cameras show the web address before opening it. Safeonweb's advice is to check where a QR code comes from before you scan it, and some scanner apps can check a link's safety first.
  • Never sign in or pay from a scanned code. For anything involving a password or a payment, the FBI advises typing a known, trusted web address yourself instead of following the code. It also warns against installing apps through a QR code.
  • Look at the physical code. On a parking meter, poster or terminal, check whether a sticker has been placed over the original.

What to change on the IT side

Training helps, but the bigger gains come from settings that don't depend on someone spotting the trick.

Let your email filter read the codes

Microsoft Defender for Office 365 and Exchange Online Protection extract QR codes from images during mail flow and check where they lead. That's a real improvement, but attackers keep adjusting how they draw and hide codes, and a message with a code that links to a newly registered page can still get through. As of November 2026, Microsoft is also rolling out detection of malicious QR codes in Teams messages, switched on by default through the existing malicious URL protection setting.

Protect the phone, not just the laptop

If staff read work email on their phones, those phones are part of your defence. Microsoft Defender for Endpoint on iOS and Android includes web protection that blocks phishing sites. How much of the phone it covers depends on how the device is enrolled: on an Android work profile, for example, only the work profile is protected.

Make a stolen password worthless

The account is the prize, so take it off the table. Phishing-resistant sign-in with passkeys means a fake page has nothing to relay. Conditional Access rules that only allow access to company data from compliant devices mean a session stolen on someone else's machine is much less useful.

Make reporting easy

Give your team one obvious way to report a suspicious email, such as the Report button in Outlook, and say clearly that reporting a scan is welcome, not embarrassing. Suspicious messages can also be forwarded to suspicious@safeonweb.be, which helps the CCB warn others.

If someone scanned a code and entered their password, treat the account as compromised: reset the password, revoke all sessions and check for new MFA methods and inbox rules the same day.

Our guide to a hacked email account walks through those steps in order.

Where to start

  1. Tell your team this week that your IT team and Microsoft will never ask them to scan a QR code in an email to sign in, and that scanning one is a reason to report, not to hide.
  2. Check your email protection and confirm that QR-code scanning is active for your licence and that user-reported messages are reviewed by someone.
  3. List who reads work email on a phone, and decide how those phones are protected: device enrolment, app protection or mobile threat defence.
  4. Start a passkey rollout for the accounts that would hurt most if stolen: directors, finance and administrators.
  5. Write down the response steps for "I scanned it and signed in", so the first person who reports it gets a quick, calm answer.

The takeaway

Quishing works because it moves the click away from your protected laptop to a phone nobody manages, and because a square of dots looks harmless. You don't need new rules for it: treat a QR code like any other link, never sign in or pay from one, and make sure your email filter, your phones and your sign-in method are ready for the cases where someone scans anyway. A short team briefing and a passkey rollout for your key accounts cover most of the risk.

← All articles

Not sure where you stand?

Find your gaps before an attacker does

A free, no-obligation assessment maps your risks and gives you a prioritised plan, whether or not you work with us.