How safe is NFC, and what can it expose?
A tag is read across two centimetres, holds no power and makes no decisions, which rules out most of what people picture. The risks that remain sit elsewhere: at the address the tag points to, in systems that treat a public number as a secret, and in what a copy of a tag lets somebody do.
What the physics rules out
A tag has no battery. It is powered by the field of the reader, and that field is useful across roughly two centimetres.
So every scenario that begins with somebody at the far side of a room, or walking past in a crowd, is asking the field to do something it cannot. The attacker has to be close enough that you would notice, and stay there while the exchange completes.
A tag also has no logic. It answers what it is asked and does nothing else, which means it cannot decide, cannot initiate, and cannot reach out to anything.
These two facts remove most of what gets written about NFC risk. What they do not remove is worth taking seriously.
What actually remains
The destination. A tag holds an address, and the page at that address behaves like any other page: it can log the visit, set identifiers, and record far more than the tag ever held. This is where the privacy question really lives.
Systems that trust a number. A tag announces an identifier to any reader that asks. Installations that authorise on that identifier are authorising on a value anybody standing next to the holder can obtain.
Content that should not be public. Anything written on a tag is readable by anybody who holds a phone to it, with no permission asked and no trace left.
And rewriting rather than copying. An unlocked tag on a wall can be overwritten by a passer by, which is a more practical attack than duplication and gets less attention.
The confusion that does the damage
Locking a tag and protecting a tag are not the same thing, and treating them as one causes more real losses than any attack.
Locking prevents alteration. It does nothing whatever about copying, because a copy is made by reading, and reading is exactly what a tag is for.
Similarly, an identifier feels like a secret and is not one. It is long, it looks random, and nobody publishes it, none of which makes it confidential.
Most disappointed deployments come from one of these two confusions rather than from a sophisticated adversary.
Judging a risk by what it is worth
Copying a tag requires proximity, a blank, and a reason. The first two are cheap; the third is where most fears fall apart.
A copy of a tag that opens a public page gains the attacker a public page. A copy of a badge that opens a door gains them the door. The same operation, wildly different consequences, and the difference is entirely in what sits behind the tag.
So the useful question is not whether your tag can be copied. It can. The question is what somebody would hold if they did.
Answer that first, and the protection that follows is proportionate rather than reflexive.
All guides in this section
- What can be cloned
- Authentication and signatures
- Payment security
- Privacy and tracking
- Myths and common beliefs
What can be cloned
- What can actually be cloned from an NFC tag?
- Can someone copy your NFC business card?
- Can an access badge be cloned?
- Can a tag be cloned without touching it?
- Can a phone clone a tag on its own?
- Can a bank card be cloned by tapping it?
- Can a passport or an ID be read without consent?
- Is your tag worth cloning to anyone?
- How do you tell if a tag is a clone?
- How do you protect a deployment against copying?
Authentication and signatures
- What is a signed NDEF record, and what does it prove?
- Can a tag prove it is genuine?
- What is tag authentication, and which chips offer it?
- Does password protection authenticate anything?
- What is a rolling code on a tag?
- Who verifies that a tag is genuine?
- How do brands authenticate products with NFC?
- Can a tag be tied to a single phone?
- When is cryptographic authentication worth its cost?
Payment security
- How safe is contactless payment, really?
- What happens if you tap a terminal you do not trust?
- What does a payment terminal actually receive?
- Do RFID blocking wallets do anything?
- Why is a phone payment safer than a card tap?
- What happens if your phone is stolen?
- Who pays when a contactless payment is fraudulent?
- What data is on a contactless card?
- Why do contactless payment limits exist?
Privacy and tracking
- Can an NFC tag track you?
- What does a tag learn about the phone that reads it?
- Can a tag read data from your phone?
- What does the site behind a tag see?
- Is leaving NFC on a privacy risk?
- Could somebody track you with a tag hidden in your things?
- What are the privacy duties of a public tag?
- What should a tag driven landing page disclose?
- Do NFC tags fall under data protection rules?
Myths and common beliefs
- Can an NFC tag be disabled permanently?
- Can an NFC tag carry a virus?
- Can someone hack your phone through a tag?
- Is NFC dangerous for health?
- Does NFC work when your phone is switched off?
- Can a tag be changed remotely?
- Can you tell what a tag holds by looking at it?
- Do NFC tags need to be registered or activated?
- Is a QR code safer than an NFC tag?
- Is it safe to tap a tag in a public place?
- What should you do after tapping an unknown tag?
Frequently asked questions
Can somebody read my tag from across a room?
No. A tag is powered by the reader's field, which is useful across roughly two centimetres. Distance is the one thing NFC genuinely rules out.
Does locking a tag stop it being copied?
No. Locking prevents alteration and has no effect on duplication, because copying is done by reading.
Where is the real privacy question?
At the address the tag points to. The page behind a tag can record far more than the tag ever held.
Is a tag identifier a secret?
No. It is announced to any reader that asks, before anything else is exchanged. It is a name, not a password.