Case Library / Quishing (QR Code Phishing) / Abnormal Security "Missed Voicemail" QR Quishing Campaign (2021)

Abnormal Security "Missed Voicemail" QR Quishing Campaign (2021)

Between September 15 and October 13, 2021, attackers sent nearly 200 emails disguised as missed-voicemail notifications with embedded QR codes that routed victims to a Microsoft-credential phishing page hosted on a legitimate enterprise survey service, using compromised Outlook accounts to bypass secure email gateways entirely, one of the earliest vendor-documented "quishing" campaigns.

Share:

Reviewed by the Social Engineering Examples team.

What Happened

Between September 15, 2021 and October 13, 2021, Abnormal Security detected and blocked nearly 200 phishing emails sent to its enterprise customers that disguised QR codes as "missed voicemail" notifications. Scanning the QR code led victims to a Microsoft-credential phishing page hosted on a legitimate enterprise survey service, with backend infrastructure on Amazon/Google IPs. The emails were sent from genuinely compromised Outlook/Office 365 accounts belonging to victim organizations, often from already-approved sender IPs and passing DMARC, and used six distinct sender personas tailored to match each target's industry. Abnormal published the findings on October 26, 2021, describing it as one of the first functional cases of QR-code-based email phishing ("quishing") it had observed, arriving a few months after a July 2021 Better Business Bureau consumer alert had already flagged QR-code scams as an emerging risk.

How the Attack Worked

The actor first tried (Sept 2021) hiding a malicious URL behind an image styled to look like a .WAV voicemail attachment; a security vendor caught that version. The actor then iterated to a QR code embedded directly in the email body: QR codes are images, so secure email gateways' URL-scanning and attachment-scanning features do not decode or check what a QR code actually links to, letting the message through as an ordinary image attachment. The email body impersonated a "missed voicemail" / "encrypted voicemail" notification urging the recipient to scan the code to listen. Because QR codes cannot be clicked on the same device the email is read on, the intended victim flow was: open the email on a computer, then use a phone camera to scan the code, which opened a mobile browser to the phishing page, a device-hop that itself moves the interaction off any corporate-monitored endpoint or network. The phishing pages, designed to harvest Microsoft 365 usernames and passwords, were hosted not on attacker-registered lookalike domains but on a legitimate enterprise survey/form-building service, with backend IPs registered to Amazon or Google, again borrowing trusted, unblockable infrastructure. Oddly, despite all text being in English, the pages served a German-language reCAPTCHA, suggesting the survey platform geolocated the attacker (not the victim) to Germany. Delivery itself used compromised legitimate Outlook/Office 365 accounts at victim organizations, sending from already-approved sender IPs and frequently passing DMARC authentication outright, since the "attacker" was, cryptographically, the real account. Six distinct sender personas were used across the campaign, most tailored to match the target's own industry. Fresh QR images were generated the same day as each send, defeating image-hash/blocklist reputation systems.

The Lure & the Tell

The lure: an email styled as an automated "missed voicemail" / "encrypted voicemail" notification containing a QR code to scan for playback, exploiting the routine, low-suspicion nature of voicemail-to-email notifications that most M365 users already receive legitimately, and using a QR code specifically because it looked benign (just an image) to both the recipient and to security scanners. The tell, per Abnormal's own analysis: QR codes in a business email asking you to scan-to-listen are not a standard voicemail delivery mechanism (real systems attach audio files or provide a direct playback link, not a photo you must scan with a separate device); the forced device hop from computer to phone is itself unusual and should prompt suspicion; the landing page's mismatched German reCAPTCHA on an all-English page was a visible inconsistency; and the underlying domain, once scanned, was a generic third-party survey-tool URL rather than any Microsoft or organizational domain, a direct giveaway that no legitimate voicemail system would route through a survey platform.

Outcome

Abnormal Security identified and blocked the campaign's emails for its own customer base before public disclosure; the company states it detected and stopped almost 200 such emails between Sept 15 and Oct 13, 2021. No breach, fraud, or confirmed successful credential theft tied to this specific campaign was publicly reported; the disclosure is framed as a threat-intelligence "we caught this" writeup rather than a post-breach incident report. The threat actor was never identified or attributed; Abnormal's Director of Threat Intelligence, Crane Hassold, called it the first functional QR-code-in-email phishing case his team had observed and noted the awkward victim flow (needing to open the email on one device and scan with another) likely limited the campaign's real-world success rate. The campaign is widely cited in the security industry as marking the emergence of "quishing" as a distinct, named attack category, arriving shortly after a July 2021 Better Business Bureau consumer scam alert about QR codes more generally.

Why It Matters

This campaign is widely cited as one of the earliest vendor-documented instances of QR-code phishing via email at enterprise scale, and it demonstrated a structural blind spot that persisted for years afterward: secure email gateways and native cloud-email security controls scanned URLs and attachments for known-bad indicators, but treated QR codes as opaque images, never decoding the embedded link to check it. It also showcased two techniques that became staples of later quishing waves: hijacking legitimately compromised accounts/trusted-brand infrastructure to inherit sender reputation and pass authentication checks, and hosting phishing pages on legitimate third-party SaaS platforms (survey tools, form builders, cloud storage) rather than attacker-registered lookalike domains, denying defenders any domain-reputation signal to act on. The campaign also illustrated the "device-hop" property unique to QR phishing: forcing the target to move the interaction from a monitored corporate computer to an unmanaged personal phone, sidestepping corporate EDR, browser isolation, and network-level URL filtering entirely, a property that made the vector both awkward (limiting immediate success) and, in hindsight, a preview of the much larger quishing surge (fake parking tickets, delivery notices, MFA re-enrollment lures) that followed industry-wide from 2022 onward.

Defenses

Abnormal's own writeup frames the core lesson: legacy secure email gateways and native M365/Google controls scan links and attachments for known-bad URLs/hashes: a QR code embedded as an image, sent from a legitimate (compromised) account, with a landing page freshly hosted on a legitimate SaaS domain, matches none of those signatures. Effective defenses that would have caught this class of attack: (1) behavioral/anomaly detection that flags compromised-account sending patterns and unusual sender/content combinations rather than relying on URL/attachment reputation; (2) treating QR codes in email as first-class scannable objects (decode-and-check the underlying URL against threat intel, same as any link) rather than an unscanned image; (3) user training specifically on quishing, since scanning shifts the click from a monitored corporate device/network to an unmanaged personal phone, evading EDR, browser isolation, and DNS filtering entirely; (4) phishing-resistant MFA (FIDO2/passkeys) on M365 accounts so a harvested password alone is insufficient; (5) vendor/SaaS abuse monitoring: flagging survey-tool or form-builder domains suddenly hosting credential-harvesting pages, since attackers piggyback on the target domain's own good reputation; (6) DMARC/DKIM alignment checks alone were insufficient here because the sending account itself was legitimately compromised, so the abuse must be caught by account-behavior signals, not authentication-protocol pass/fail.

Sources
Attack Chain & Defense
The sequence the attacker ran
How it could have been stopped
1
Target-List Assembly: consistent with the campaign's broad, non-targeted "mass" profile as reported, the attacker likely worked from a bulk email address list (harvested from a compromised mailbox's contacts/address book, a purchased B2B contact database, or similar), rather than researching individual employees the way a targeted spear-phishing operation would.
Countering Stage 1: bulk email-address-list assembly for mass campaigns is largely outside defenders' control and hard to detect in advance; the realistic control lands downstream, at delivery and detection, where anomalous sending behavior can be caught regardless of how the recipient list was built.
2
Compromise of Sending Infrastructure: the attacker obtained working credentials to a legitimate victim organization's Outlook/Office 365 mailbox, likely through a prior, separate credential-phishing or credential-stuffing incident not documented in this campaign's own reporting, giving them a sending account with an already-trusted reputation and clean DMARC/SPF/DKIM alignment.
Countering Stage 2: phishing-resistant MFA (FIDO2/passkeys) and continuous sign-in risk detection (impossible travel, new device, anomalous login location) on all M365/Office 365 accounts prevent a stolen or guessed password alone from producing the kind of account takeover that supplied this campaign's trusted sending infrastructure.
3
Lure Development and Iteration: the actor built and tested multiple sender personas (six were documented, most tailored to the target's own industry) and iterated the lure format after an initial failure, moving from a malicious link hidden behind a fake .WAV voicemail-attachment image (caught by a security vendor) to a QR code embedded directly in the email body once that version evaded gateway scanning.
Countering Stage 3: because the lure content itself is engineered to look benign to signature-based scanners, defense at this stage depends on behavioral/anomaly-based email security, flagging an account suddenly sending atypical content, personas, or volume, rather than trying to blocklist the lure format itself.
4
Phishing Infrastructure Setup: rather than registering an attacker-controlled lookalike domain, the actor built a credential-harvesting landing page on a legitimate third-party enterprise survey/form-building service and generated a fresh QR-code image for each send, a combination that denies defenders both a bad domain to blocklist and a repeated image hash to flag.
Countering Stage 4: vendor/SaaS abuse-monitoring on survey and form-building platforms (and on the cloud IP ranges hosting them) to catch when their infrastructure is suddenly serving credential-harvesting forms, combined with decode-and-check tooling that treats embedded QR codes as first-class scannable links against threat intelligence rather than opaque, unscanned images.
5
Delivery: the lure email, styled as an automated "missed voicemail" / "encrypted voicemail" notification, was sent from the compromised Outlook account to the target list with the QR code embedded as an inline image and no clickable link or scannable attachment present for gateway URL/attachment filters to inspect.
Countering Stage 5: behavioral/anomaly-based email security that flags compromised-account sending patterns (unusual recipients, content, or volume from an otherwise-trusted mailbox), since traditional DMARC/DKIM/SPF authentication checks pass cleanly here precisely because the sending account is genuinely compromised, not spoofed.
6
Victim Interaction and Device-Hop: the intended flow required the recipient to open the email on a work computer, then scan the embedded QR code with a personal phone's camera, which opened a mobile browser and navigated to the phishing page, moving the interaction off the monitored corporate device and network onto an unmanaged personal one.
Countering Stage 6: user-awareness training specifically covering quishing and the device-hop pattern, teaching that a business email asking the recipient to scan a code with a separate personal device is inherently unusual, since once the interaction moves to an unmanaged personal phone it becomes invisible to corporate EDR, browser isolation, and network-level URL filtering.
7
Credential Capture (objective completion): the victim was prompted to enter Microsoft 365 credentials on the fake login page (which displayed a mismatched German-language reCAPTCHA on an otherwise English-language page) to "unlock" the voicemail, with any entered credentials relayed to attacker-controlled backend infrastructure on Amazon/Google IP addresses; Abnormal reports it blocked emails in its own customer base before this stage completed, and no source confirms any victim actually reached or completed this step.
Countering Stage 7: phishing-resistant MFA (FIDO2/passkeys) on Microsoft 365 accounts makes a harvested password insufficient on its own to complete an account takeover, serving as the last line of defense if every earlier stage in the chain had already failed.
Quick Facts
Victim
Approximately 200 email recipients across Abnormal Security's enterprise customer base (unnamed organizations), all Microsoft 365 / Office 365 users; no individual victim organizations were named
Location
Global / United States-centric (Abnormal Security's customer base is predominantly US enterprises); backend phishing infrastructure IPs geolocated to the United States and Germany
Date
2021-09-15 to 2021-10-13 (campaign window); reported by Abnormal Security on 2021-10-26
Impact
Not disclosed / not quantified. Abnormal Security and all secondary coverage describe this as a credential-harvesting campaign that was detected and blocked before compromise; no dollar loss, ransom, or downstream fraud figure was ever reported publicly. Abnormal states it blocked "almost 200" emails targeting its own customer base; this is a count of blocked malicious emails/attempts, not 200 confirmed distinct victim organizations, and there is no public confirmation any recipient actually entered credentials.
Status
Confirmed
Case Type
Real-World Incident
Sector
Cross-Sector / Multiple Industries
Related

Related Cases

LevelBlue MTDR SOC "Quishing" Case Study - Fake Microsoft MFA-Setup QR Code Harvests Employee Credentials (2023)

LevelBlue's MDR SOC documented a real client quishing case in which a PDF impersonating a Microsoft MFA-setup notice, hiding a…

Incident 2023Read →

Hornetsecurity QRishing Attack on US-Based MSP (2023)

Hornetsecurity documented a QR-phishing (quishing) email sent to a single employee at a US-based MSP that spoofed an MFA-reactivation notice…

Incident 2023Read →

FTC Consumer Alert: QR Code Scams (Quishing)

The FTC's first major consumer alert on QR-code scams (Dec 6, 2023) warned of fake QR stickers on parking meters…

Incident 2023Read →