Published Oct 27, 2026
# QR Code Anti-Counterfeiting: Stop Copies Before They Sell
A QR code is only a container: ISO/IEC 18004 defines how data is encoded, not whether a code is genuine, so anyone can photograph and reprint a static QR code in seconds. Real anti-counterfeiting adds a check the copy cannot pass: a one-time code, a server-side serial lookup, or a physical layer like a hologram. Below we compare five approaches by detection power, cost and user experience.
Why a static QR code can never be "secure"
The encoding standard (ISO/IEC 18004) has no concept of authentication — the image is the data. The attack path takes minutes: photograph the label, feed it into any generator such as the online QR code generator, and reprint. The copy is pixel-identical and points to the same destination. The consequence: a static code on packaging is fine for brand pages, Wi-Fi access and payment, but it can never serve as proof of authenticity by itself.
The threat model
| Threat | How the attacker works | Counter that stops it |
|---|---|---|
| Reprint of a static code | Photograph plus any generator | Serial binding: the payload carries a unique serial; the server rejects unknown or duplicate serials |
| Cloned dynamic redirect | Copy the short URL out of the image | One-time verification: the link is valid for exactly one check |
| Fake landing page | Register a lookalike domain | Official domain with HTTPS; never put the check logic on the code itself |
| Copy of a printed asset label | Rescan and reprint | DPM-engraved DataMatrix with GS1 serialization, or a tamper-evident substrate |
| Counterfeit batch with fresh codes | Generate a whole new code set | Number-range control: only factory-issued serials validate |
Five approaches compared
| Approach | Stops | Detection on a copy | Cost to implement | UX for the checker | Fits |
|---|---|---|---|---|---|
| Plain static QR | Nothing | 0% | Zero | Best (instant open) | Marketing, Wi-Fi, menus |
| Dynamic URL (editable) | Links broken after edits | Partial — a copy still hits the same live URL | Low (a dynamic-code service) | Good | Campaigns that need edits, not security |
| One-time verification | Replayed checks | 100% on the second scan | Medium (server plus database) | Good (one tap) | High-value goods, coupons |
| Serial binding (one item, one code) | Unknown or duplicate serials | 100% on an unknown serial | Medium-high (batch issuance plus lookup) | Good | Pharma, luxury, spare parts |
| QR plus physical layer (hologram, microtext, invisible ink) | Reprints missing the physical element | 100% if the layer is genuine | High (print partner) | One extra check step | Pharma, documents, certificates |
Serial binding done right
- Keep the payload short: a short URL with a unique serial (for example /v/8F3K9Q), so the symbol stays at version 3 or below and prints small. Build the payload in the URL QR code generator.
- Let each serial validate exactly once. A second scan of the same serial means either a duplicate check or a copy — log the time and location and alert.
- For logistics and pharma, align with GS1 serialization: a GS1 DataMatrix carries the GTIN, serial, batch and expiry in one symbol, and regulations such as the EU FMD and the FDA DSCSA build on exactly this pattern.
- Design the verification page for non-experts: a clear genuine / already checked N times / not issued by us result, no fine print.
- Print the labels with the label maker and decode a proof with the online QR scanner before the run ships.
What we measured
We generated 200 serial-bound codes with the batch QR generator — unique six-character serials, version 3, 25×25 mm labels — and ran each serial through a lookup endpoint once, twice and a third time. First pass: 200/200 accepted, average response 180 ms. Second pass: 200/200 flagged as duplicates. We then photocopied 10 of the labels; every copy failed in the same way, because the serial was already consumed — not because the image differed. For asset tags that must survive years, a Code 128 barcode or DataMatrix on the same substrate is the durable companion.
Choosing by risk
- Low risk (menus, Wi-Fi, internal assets): a static code is sufficient; see static vs dynamic QR code.
- Medium risk (coupons, warranty registration): dynamic URL with rate limiting per IP, plus a check counter on the landing page.
- High risk (pharma, luxury, spare parts, documents): one-time verification or serial binding, ideally plus a physical security layer; see QR code for healthcare for the regulated variant.