Back to guides

Wi-Fi NFC Tags Hold the Password in Plain Text: Where to Put One

A Wi-Fi NFC tag stores the network key unencrypted, so anyone who can tap it can read the password. Write a guest network, keep the tag indoors, and lock it after you test it.

Published

Short answer

A Wi-Fi NFC tag stores your network key as plain text, so anyone who can tap it can read the password. Write only a guest network to it, stick it where only visitors can reach it, and lock it once it works.

What the tag actually stores

When you write a Wi-Fi tag, the phone saves a Wi-Fi Simple Configuration record with the media type application/vnd.wfa.wsc. We cover its fields in the WSC record, but the part that matters here is the Network Key. The ndeflib documentation describes a Configuration Token as carrying unencrypted credentials, with a key of up to 64 octets next to the SSID and the authentication and encryption types.

You can see this in a real example. SparkFun's ST25DV64KC Wi-Fi example writes a network called guestNetwork with the password guestPassword123. In its hex dump, the password sits in the text column as ordinary ASCII. No key is needed to read it. Any NFC reader app will show it.

The WPA2 and AES settings protect the radio link after you join. They do not protect the password on the tag.

Put the tag on a guest network

Because the key is readable, treat the tag as a way to hand out a password, not to hide one. Write a network you are happy for visitors to use, never your main one.

A guest network is a separate network with its own name and password. Google's guest Wi-Fi help page describes it as a separate network just for your guests, where visitors can use only the devices you choose to share. The password must differ from your main network's, and you can change it later from the same screen.

That last point is the useful one. If someone copies the password off the tag, you change the guest password and rewrite one tag. Your laptops, cameras and phones stay untouched. Our guest Wi-Fi tag guide walks through the write itself.

Where the tag goes

An NFC read happens within a few centimetres, so the risk is not someone sniffing the password from across the street. The risk is who can walk up and tap it. Placement is your access control.

  • Good: inside the home or rental, on the fridge, a shelf by the sofa, the inside of the entry hall cabinet. Guests are already past your front door.
  • Weaker: the outside of a door, a window, a gate or a porch wall. Anyone passing can tap it.
  • Shared spaces: a staff-only area is fine. A waiting room wall is a public tag, so assume the password is public.

If a tag has to live somewhere open, ask whether a printed code is better. We compare NFC or a QR code for exactly this choice. A QR code on a wall is just as readable, so neither option hides the password. The difference is that a tag can be locked against tampering.

Lock it after you write it

A new tag doesn't protect itself. NCC Group's overview of NFC chip security notes that on the NTAG213 read and write protection are available but not enabled by default. An unprotected tag can be overwritten with something else, such as a phishing link, and nobody would know until they tapped.

On an NTAG213 you have two options, as the WakDev chip notes summarise:

  • Permanent lock: the lock bytes make the memory read-only. This is irreversible.
  • 32-bit password: a password and a 16-bit acknowledgement restrict writes, or optionally reads, from a page you choose.

For a guest tag, write protection is what you want. Do not turn on read protection: a phone that cannot read the tag cannot join the network either. Our comparison of password protection or a permanent lock explains when each fits.

Write the record, tap it on an iPhone and an Android phone, and only then lock it. NCC's conclusion is modest: default-level protections stop opportunistic tampering, not a determined attacker. That is another reason to keep the network a guest one.

When the password changes

A permanently locked tag cannot be rewritten. If you rotate the guest password, write a new tag and replace the old one. An NTAG213 offers 144 bytes of user memory, plenty for one Wi-Fi record. If you rotate often, use the password option instead of the permanent lock, and remember the password.

Conclusion

The tag won't keep your password secret, so build around that. Write a guest network, place the tag past your front door, lock it after testing, and replace it when you change the password. Before you hand a tag to anyone, read it back with an NFC reader such as NFCore to see exactly what it holds.

Frequently Asked Questions

Is the Wi-Fi password on an NFC tag encrypted?

No. The Wi-Fi Simple Configuration record stores the network key unencrypted, so any NFC reader that can read the tag can recover it.

Can I stop people reading the password off the tag?

You can switch on NTAG213 read protection with a 32-bit password, but phones then usually cannot read the tag either, which defeats the point. Treat the password as visible and limit the damage with a guest network.

Should I lock the tag after writing it?

Yes, if the guest password will not change. A permanent lock stops anyone rewriting the tag with another link, but it is irreversible, so write and test first.