In late 2014, Nintendo launched a tiny plastic fortress: the amiibo.
Nintendo spent millions securing the protocol between the console and the toy. But they relied on a third-party manufacturing ecosystem that had lax security on its programming tools. The hackers didn't kick down the front door; they walked in through the construction site left open next door.
The "Key"—or more accurately, the method to generate valid signatures—was effectively in the wild. Within months, apps like TagMo emerged, allowing anyone with a smartphone and a $0.30 NFC sticker to create their own amiibo.
For enthusiasts creating backups or custom amiibo cards, these keys act as the "bridge" between raw data and a functional figure. amiibo encryption key
Nintendo’s amiibo figures contain an NFC chip. Data on the chip is split into:
The final piece of the puzzle came down to observation. The encryption used by the amiibo (a mathematical standard) was strong, but the implementation had a flaw. The hackers realized that during the handshake between the amiibo and the Wii U, the console had to send a specific "unlock" command to the chip to wake it up.
In modern computing, if a user possesses the hardware, they will eventually possess the keys. Once the amiibo key was exposed, it allowed for the preservation of digital rights. Players could back up their $50 rare figures onto cheap stickers, ensuring that even if the plastic toy broke, the digital content remained theirs. It shifted the power from the manufacturer back to the owner. In late 2014, Nintendo launched a tiny plastic
By reverse-engineering the firmware of this industrial writer, the hackers found something incredible. The manufacturer of the writer had left a "backdoor" command—a debug mode that wasn't supposed to be active in the final product. Using this backdoor, the hackers could override the protection on a blank NFC chip and write any key they wanted to the lock page.
By listening to the communication between a legitimate amiibo and a Wii U—sniffing the radio waves—they could capture the handshake. Combined with the ability to write to blank chips via the industrial writer, they could now clone an amiibo perfectly.
| Key | Length | Purpose | |------|--------|---------| | | 128 bits | Encrypts the “dynamic” part of the tag (save data, counters) | | HMAC Key | 128 bits | Ensures integrity & authenticity of the encrypted data | The hackers didn't kick down the front door;
The security relied on the fact that the NTAG213's lock page was hard to read. But "hard to read" is not "impossible to duplicate." Once the industrial writers were compromised, the obscurity of the chip's layout became irrelevant.
In the world of hardware hacking, there is generally one way to get a key: you either find a flaw in the software implementation (a bug) or you physically pry the chip apart (a side-channel attack).
Amiibo encryption relies on HMAC-SHA256 signatures, specifically requiring unfixed-info.bin and locked-secret.bin files (often bundled as key_retail.bin ) to read and edit .bin data on NTAG215 chips. Reverse-engineered in 2015, these keys allow for the emulation and modification of Amiibo data via apps like TagMo or hardware like Flipper Zero. For a detailed breakdown of the reverse-engineering process, see the analysis at Kevin Brewster's Blog . Reverse Engineering Nintendo Amiibo (NFC Toy)