The QR code stuck over the real one
The simplest attack in the whole category: a sticker worth a few cents, over a genuine code. No software, no vulnerability, no hacking. Just paper in the right place.
What makes this fraud work is not technology but the setting. Somebody standing at a parking machine is in a hurry, doesn't want to miss a ticket, and trusts the device. Rightly, too, because the device is genuine. Only the square on it isn't.
Why it works
- The place vouches for the code. Nobody distrusts a municipal machine, and the sticker inherits that trust.
- There is, apparently, nothing to check. A code looks like a code, and the address only shows up once you have scanned it.
- The amounts are small. Nobody queries €2.80 for two hours, and the card details collected along the way are the real target.
- It's cheap and repeatable. A sheet of stickers costs very little and covers a whole street.
How to spot one before you pay
- Feel the edge: if a corner lifts, it is a sticker. Not fraud by itself, but a reason to look closer.
- Compare the surface: the genuine code is usually printed, lacquered or engraved straight onto the machine. Same surface, same black, no cut edge.
- Read the label: is there an address or an app name beside the code? Then the scanned address has to match it.
- Read the address without opening it: the part directly before the ending has to belong to the operator.
- If in doubt, use the operator's app or pay at the machine. That makes the sticker pointless.
For operators: what actually helps
If you run machines, charging points, tables or notices carrying codes, you can make a forger's job much harder. None of this is expensive.
- Don't stick the code on. Print it, lacquer it, engrave it, or put it behind plastic. A sticker on top of that is then obvious.
- Write the address out next to it, large enough to read. It's the simplest check a customer can make, and a forger would have to cover that up as well.
- Use a short domain of your own rather than a shortening service. Using bit.ly yourself trains customers to accept shortened links.
- No payment requests through a code hanging in a public place. Collecting card details via a stuck-on code is indistinguishable from the fraud.
- Use static codes whose destination cannot change, and look at them regularly. Two minutes per site per week is enough.
You can make static codes here, with no account and no expiry: PNG for a notice, SVG for the printer. Create a QR code →
- Is the operator liable for a code somebody stuck over theirs?
- That's a legal question that depends on the case, and it isn't answered here. In practice: checking regularly and printing the address beside the code puts you in a far better position than doing neither.
- Is a warning sign saying “beware of fake codes” enough?
- It helps little while the genuine code is still a sticker. The countermeasure is making the real code look impossible to paste over.
- Are dynamic codes safer?
- Not against this trick, since both can be covered over. Dynamic codes carry a different risk instead: they stop working when the service behind them ends.
Read next
- Quishing
What the word means, why it works, and how to recognise it.
- How to spot a fake QR code
The signs on the paper and the signs in the address, as a checklist.
- QR code scams: the variants
Parking, charging, menus, parcels, donations, invoices: variant by variant.
- How to check a QR code without opening it
Scan but do not open: read the address, and judge it in twenty seconds.