A QR code can hide the same kind of malicious link used in email and text scams. This checklist explains how to check the destination, recognize suspicious payment requests, verify the organization independently, and decide what to do before scanning, signing in, or paying.
Overview
QR phishing, sometimes called quishing, uses a QR code to move you from a physical sign, message, screen, or social post to a website or app. The code itself does not prove that the destination is legitimate. It is simply a shortcut to information supplied by whoever created or placed it.
A safe decision does not require advanced technical knowledge. Treat the QR code like an unfamiliar link: pause, reveal the destination, inspect it, and confirm the request through a separate trusted channel. Be especially cautious when the page asks for a password, card number, bank details, identity information, a payment, or permission to install an app.
Do not assume that a QR code is safe because it appears in a familiar location. A sticker can be placed over a legitimate parking meter code, a printed notice can be copied, and an account can be compromised before a post reaches you. Visual branding is useful context, but it is not proof of authenticity.
Before acting, use this short rule: scan only when necessary, inspect before opening, verify independently, and stop if the request creates pressure.
Checklist by scenario
The right level of scrutiny depends on what the QR code is asking you to do. Use the following comparison as a starting point.
| Where you see the QR code | What to check first | Warning signs | Safer next step |
|---|---|---|---|
| Parking notice or meter | Reveal the URL and compare the domain with the parking operator's official website or app. | A pasted sticker, an unfamiliar domain, a demand for immediate payment, or a request for unnecessary personal details. | Open the operator's official site or app manually, or use the payment method printed on a verified sign. |
| Package message or delivery notice | Check whether the message was expected and inspect the complete destination URL. | Urgent claims about a missed delivery, address correction, small redelivery fee, or card verification. | Track the package through the retailer or carrier's official app or website, not through the QR link. |
| Restaurant menu | Look for a normal web address and confirm that the page only needs menu-related access. | A forced app download, requests for contacts or location without a clear reason, or an unexpected payment page. | Ask staff for the menu or type the restaurant's known website into your browser. |
| Event ticket | Confirm that the ticket came from the organizer or authorized seller and that the destination matches its domain. | A request to sign in through an unfamiliar site, transfer money outside the ticket platform, or install an unrecognized app. | Use the ticket seller's official app or account page and contact the organizer using independently found details. |
| Invoice or business document | Compare payment details with a previous invoice and verify any changed bank or payment information. | New payment instructions, unusual urgency, mismatched company details, or a QR code added over the original document. | Call a known contact at the organization using a number already on file. |
| Social post or advertisement | Inspect the destination and question why the offer requires a QR scan. | Prize claims, investment promises, emergency appeals, limited-time pressure, or a request for credentials or crypto payment. | Find the organization or offer through a separate search and navigate from its official presence. |
How to check a QR code link before opening it
- Pause before scanning. Ask what the code is supposed to do and whether you need it at all. If the same service has an official app, known website, or physical payment option, that may be safer than using an unexpected code.
- Use the camera's preview rather than tapping immediately. Many phones show the destination as a notification or preview. Read it before opening. If your camera opens the page automatically, close it and repeat the process with a QR scanner or device setting that lets you preview the link first.
- Read the full domain. Look past the brand name in the page title. Watch for misspellings, extra words, unexpected subdomains, hyphens used to imitate a brand, or a domain ending that does not fit the organization. A padlock or HTTPS connection only indicates that the connection is encrypted; it does not prove that the site is honest.
- Expect redirects and shortened links. A preview may show one address while the browser eventually reaches another. Stop if the link passes through several unfamiliar domains, uses a shortened address you cannot verify, or redirects to a login or payment page that was not expected.
- Check the page before entering anything. Look for a clear organization name, consistent contact information, sensible spelling, and a purpose that matches the original context. Do not enter a password simply because the page resembles a familiar sign-in screen.
- Review app permissions. If the destination asks you to install an app, check its name, publisher, requested permissions, and source. A menu or ticket should not normally require access to contacts, messages, accessibility controls, or unrelated device functions.
- Verify payment independently. Never rely on the QR code itself to confirm where money is going. Check the recipient name, amount, invoice reference, and payment destination. For an invoice or account change, contact the organization through a trusted number or website you found separately.
- Stop when urgency replaces evidence. Warnings such as “pay within minutes,” “account suspended,” or “delivery will be cancelled” are pressure cues, not proof. Take time to verify even if the message claims there is a penalty for waiting.
What to double-check
The revealed URL: Check the registrable domain, not only the words displayed before it. For example, a long address may contain a familiar brand name while ending at an unrelated domain. If you cannot identify who controls the destination, do not sign in or pay.
The requested information: Match the request to the context. A restaurant menu should not need your government identifier. A delivery update should not require a bank password. A ticket check should not ask for broad device permissions.
The payment recipient: A QR payment can make a fraudulent request feel official because it appears on a printed invoice or meter. Confirm the recipient using a separate record. If payment details differ from earlier instructions, treat the change as suspicious until verified.
The source and placement: Examine stickers, overlays, and unexpected additions. On a screen, question QR codes embedded in unsolicited messages or advertisements. On social media, remember that an account or post may not represent the organization it appears to represent.
The device behavior: Keep your phone's operating system, browser, and security tools updated. A QR code can lead to a phishing page even when the camera and browser work normally. Updates reduce avoidable weaknesses, but they cannot determine whether a payment request is legitimate.
Common mistakes
- Trusting the location. A code on a parking meter, poster, or invoice can be replaced or altered.
- Checking only the logo. Images and brand colors are easy to copy. The domain and request matter more than appearance.
- Assuming HTTPS means safe. Encryption protects the connection; it does not validate the person or business operating the site.
- Ignoring the final destination. Redirects may lead somewhere different from the first preview. Recheck the address before entering information.
- Approving a payment from the QR screen. Confirm the recipient and amount in the payment app. If anything differs from the expected transaction, cancel.
- Installing an app from an unexpected prompt. Use the official app store and search for the organization yourself instead of following a forced download path.
- Reusing a password on the linked page. If you entered credentials on a suspicious site, change that password from the real service and review account security. Our phishing-link recovery checklist covers the immediate steps.
When to revisit this checklist
Use this workflow each time you encounter an unfamiliar QR code, especially before making a payment or installing an app. Revisit it before seasonal travel, tax or invoice cycles, major events, and periods when deliveries or parking payments increase. Those are useful moments to remind family members, staff, and customers that a familiar-looking code still needs verification.
Website owners and organizations should also review printed materials, public signs, invoices, event tickets, and social profiles whenever payment providers, domains, apps, or customer workflows change. Remove obsolete codes and make the official domain or app easy to identify. If a QR campaign sends visitors to a third-party service, document the expected destination and permissions so unusual changes can be spotted.
If you already scanned a suspicious code, do not panic or continue experimenting. Close the page, avoid entering further information, and contact the organization through a trusted channel. If you submitted credentials, change them from the genuine site and enable a stronger sign-in method where available. If you supplied payment details, contact the payment provider promptly and monitor the account. For broader website and link checks, see our guide to checking whether a website is safe.
Save the practical rule: preview the link, inspect the domain, question redirects and permissions, verify payment details independently, and walk away from pressure. A QR code is convenient, but convenience should never replace confirmation.