QR Code Security: Risks, Quishing and Safe Habits
6 min read Last updated 2026-11-17
A QR code is a container, not a threat: it carries text, and the danger lies entirely in what that text does when opened. The same property that makes QR codes convenient - you cannot read the payload by eye - also makes them a vector for phishing, because a printed code can hide any URL behind an innocent-looking sticker.
This guide covers how QR-based attacks actually work, what publishers of codes can do to be trustworthy, and the small set of habits that protects people who scan codes they did not create.
Why QR codes are attractive to attackers
A camera shows no payload preview before opening a scanned link, and even when the phone does display a URL, people frequently skip reading it. Attackers exploit a trust transfer: the code sits on a physical surface you already trust - a parking meter, a poster in an office lobby, a table in a restaurant - so the scan feels safe even though the payload could point anywhere. Law-enforcement agencies, including the FBI, have published advisories about exactly this pattern on tampered parking stickers.
Unlike a link in an email, a printed code passes through no spam filter, no link scanner and no mailbox security. It is an offline attack channel with the credibility of physical space. That combination - invisible payload, borrowed trust and no intermediary checking the destination - is the whole threat model, and every defense follows from breaking one of those three.
The main attack patterns
The patterns repeat because they work. The most reported is the sticker overlay: a fake code pasted over a genuine one on parking meters, EV chargers or restaurant tables, so payments or logins flow to the attacker. The others arrive by mail or message: urgent letters and emails carrying codes that claim fines, failed deliveries or account problems, and codes that open lookalike login pages built to capture credentials.
None of these patterns require technical sophistication, which is precisely why they scale. Printing a sticker costs almost nothing, and the victim completes the attack by scanning in good faith. The defense, for both scanners and publishers, is to treat every code as an unverified claim until the preview and the context agree.
- Sticker overlays: a fake code pasted over a genuine one on meters, chargers or tables
- Impersonation letters and emails: urgent codes claiming fines, deliveries or account problems
- Credential pages: the scan opens a lookalike login page that captures passwords
- Payment redirection: a swapped payment QR sends money to the attacker
- App sideloading: the scan prompts installation of unknown apps outside official stores
Safe habits for people who scan
Read the preview. Modern phone cameras display the decoded URL before opening it, and that pause is the cheapest security control in the ecosystem. Check the domain - not just that there is one: look for lookalike spellings, unfamiliar extensions and opaque shortened links. A page that immediately asks for a password after an unexpected scan should be treated as hostile until verified.
Never enter credentials or payment details after scanning a code you did not expect, and be skeptical of urgency: fines, penalties and account lockouts are the classic pressure devices, and every one of them can be verified through an official channel instead. Install apps only through official app stores, no matter what a scanned page instructs. If a code on a public device looks like a sticker layered over another sticker, do not scan it at all.
Publishing codes you can defend
Publishers control half of the risk. Point printed codes at short, readable URLs on your own domain, so the scan preview shows a name people recognize; avoid third-party link shorteners that hide the destination behind a generic domain. Serve everything over HTTPS, and keep the physical code protected: lamination, tamper-evident sticker material or engraved plates, plus a periodic walk-through audit that scans every public code.
In payment contexts, prefer provider-issued dynamic codes where possible, and train staff to check that the payee name displayed on their own counter code still matches the business. Make that check part of the opening routine, the same way counters check their card terminals each morning. A code that a customer cannot verify is a code you should not print.
What QR codes cannot do
A QR code cannot execute anything on a phone by being scanned. Scanning merely decodes text and typically opens it; malware requires the user to take a further action, such as installing an app, opening a downloaded file or submitting credentials. Framing it this way keeps the defenses focused on the right step: the moment after the scan, when the human decides.
A static QR code also cannot track anyone: it contains no callback, and the scan touches no server. The privacy concern lives with dynamic codes, where the redirect provider observes every scan - time, IP address and device - and with the destination site's own analytics. Businesses choosing a dynamic service should treat that scan data as customer data and pick providers accordingly.
Key takeaways
- The risk is never the code itself but the destination it opens and what you do there
- Quishing works by borrowing trust from a physical surface; urgency plus an unexpected code is the classic pattern
- Read the URL preview after scanning and check the domain before entering anything
- Publishers build trust with short HTTPS URLs on their own domain and tamper-protected prints
- A payment QR cannot charge you without authentication - but a swapped one can point your money at the wrong payee
Put it into practice
Frequently asked questions
Continue reading
QR Code Basics: What They Are and How They Work
A plain-English introduction to QR codes: what they are, how scanners read them, error correction, capacity and the difference between static and dynamic codes.
Read guideQR Code Payments: How They Work and How to Accept Them
How payment QR codes work: UPI QR standards, merchant codes, wallet interoperability, settlement basics and how to accept QR payments safely.
Read guideQR Code Troubleshooting: Why Codes Fail and How to Fix Them
Fix QR codes that fail to scan: contrast, quiet zone, glare, size and damage checks, plus fixes for WiFi, UPI and logo-related scanning problems.
Read guide