Ultimate Implant Bundle

NExT/xMagic Chip Specifications
The NExT and xMagic chips contain two completely separate transponders in a single device. Each inductor coil antenna and chip in the devices are specifically tuned to accommodate co-operation within the same device.

NExT Basic Specifications

• Encased in 2.1mm by 14mm bioglass with non-toxic epoxy
• Pre-tested and pre-loaded into sterile injection assembly
• No “anti-migration” coating means easy removal/replacement

NExT 13.56MHz NTAG216 NFC Type 2 chip

• 13.56MHz ISO14443A & NFC Type 2 compliant NTAG216 NFC chip
• Full datasheet for the NXP NTAG216 RFID/NFC chip
• 7 byte UID and 886 bytes of user read/write memory
• 10 year data retention. Rated for 100k writes per memory block.

NExT/xMagic 125kHz Atmel T5577 RFID emulator chip

• 125kHz Atmel T5577 RFID emulator chip
• Full datasheet for the Atmel ATA5577 chip
• Can emulate EM41xx, EM4200, HID ProxCards, AWID, Indala, and more!

xMagic Base Specifications

• Encased in 3mm by 15mm bioglass with non-toxic epoxy
• Pre-tested and pre-loaded into sterile injection assembly
• No “anti-migration” coating means easy removal/replacement

xMagic 13.56MHz ISO14443A Mifare “magic” 1k gen2 emulator chip

• Emulates Mifare MF1ICS50 1k chip with “direct write”
• Full sector 0 writability, including 4 byte NUID and MAD

VivoKey Spark 2 Chip Specifications

• 13.56MHz ISO14443A & NFC Type 4 compliant RFID chip
• AES128 encryption function with 2 byte payload salt
• Encased in 2.1mm by 14mm bioglass with non-toxic epoxy
• Pre-tested and pre-loaded in sterile injection assembly

Testing Process
Our x-series chips come pre-loaded inside injector systems with steel needles and cannot typically be read while inside the needle. Because of this, we perform a full test on every x-series tag before it is loaded into the injector assembly and sterilized. We have also conducted several tests on our x-series chips and cataloged those tests here.

Return Policy
We offer a 30-day money back guarantee! Read all about it on our return policy page.

Lifetime Warranty
If you do purchase one of our products and experience a failure, we offer a full lifetime warranty on all of our products. You will need to return the product for testing and analysis, and if it is malfunctioning, we will ship you a replacement free of charge. Read all about it on our warranty policy page.

Passive RFID and NFC chips are magnetically coupled devices that power themselves and communicate data over a shared magnetic field the reader generates. This means their effective read range and performance depends entirely on how well the antenna coils of both the chip and reader couple with each other. This typically means the shape, size, and orientation of both antennas must be complimentary.

Because our x-series chips have a cylindrical coil antenna and most readers have a flat spiral plane antenna, correctly positioning your x-series chip is critical. This is why we include our RFID Diagnostic Card and X Field Detector! Watch this video;

Our x-series transponders are typically installed into the webbing between the metacarpal bones of the index finger and thumb, resting parallel to the index metacarpal. The reason they are installed in the hand has to do with the extremely short read range of x-series chips and the typical use case being some form of access control where the tag must be presented to a fixed reader of some kind. The suggested placement within the hand was chosen due to the lack of major nerve bundles or blood vessels running through that area.

Achieving a safe installation definitely requires a steady hand and experience performing aseptic procedures. Dangerous Things prefers our customers locate one of our professional body piercing or body modification partners to complete the installation of this product. If no partners are available in your area, you should be able to follow this guide to finding a professional in your area who is willing to assist you. For aftercare information and what to expect, please read our X-Series FAQ page.

You have questions! That’s understandable. The short answer is; it’s all good. If you’re looking for more specific answers, we have an extensive FAQ page that deals with many of the most commonly asked questions regarding installation of our x-series transponders.

The NTAG216 chip inside the NExT was designed for use in more typical NFC applications such as smart posters, labels, and other disposable use cases where the memory contents would typically be written and then locked so it could not be changed. This is done using built-in “lock bytes” which are OTP (one time programmable). That means that once the lock bytes are turned on to protect memory blocks, they can never be unlocked. Once any memory block is locked, it will forever be read-only, which is not ideal for the NExT. Many NFC applications offer ways to “lock” or “protect” your tag, which will end up locking the tag read-only. Because of this, we have disabled the ability to change or set the lock bits in the NExT’s NTAG216 chip.

Before disabling the lock bytes however, there is one page of user memory we do lock down as read-only. That is the CC or Capability Container, located in memory page 03. This page of 4 bytes is required to have a specific format of data so the tag can be recognized and used as an NFC Type 2 tag. This memory page is also special in that the data stored there uses OTP bits, or “One Time Programmable” bits, meaning once a bit is flipped from 0 to 1, it cannot be flipped back to 0. It is critical that this memory page be locked as read-only so a malicious attacker can’t mess up your Capability Container, thus ruining the chip for use as an NFC compliant transponder. We set lock bytes to mark the Capability Container as read-only, then we disable the lock bytes so no other memory pages can be permanently set as read-only.

In addition to lock bytes, the NTAG216 offers a 32bit password protection function. It can be used to password-protect just writing to or both reading from and writing to the user memory space of the NTAG216 chip. Regardless of what some NFC smartphone apps indicate, it is not possible to remove or disable the password. It is only possible to set the password to the default hexadecimal value of 0xFF 0xFF 0xFF 0xFF. If the password is set to the default value, then anyone could easily authenticate, change the password, then write data or change protection options for your tag, and change the password to some unknown value. Because it is also possible to protect memory blocks from unauthenticated reads using a password, this could make the tag completely useless by not allowing any memory blocks to even be read. We set a default password value of 0x44 0x4E 0x47 0x52 or DNGR, but strongly suggest you change it after installation.

Finally, many of the critical configuration bytes used by the NTAG216 chip are stored in the last few memory pages of the tag. This means that it may be possible for an NFC application that does not properly detect or honor the NExT’s NTAG216 chip memory schema to accidentally attempt to write binary or NDEF record data (the data you’re trying to store on the tag) overtop of the configuration bytes. For example, if the data you are attempting to write is longer than the user memory blocks available, the remainder of the data might be written overtop of configuration bytes, which contain settings that are potentially dangerous to modify such as the config lock byte. It is not possible to disable the configuration lock byte, so accidentally writing to that byte could result in your configuration being irreversibly locked. We password-protect the configuration bytes from being able to be written to or updated using the password feature of the NTAG216 chip. Overall, the NExT leaves the factory with the entire user memory space accessible and writable, while at the same time the configuration bytes and password values at the bottom end of the NTAG216 chip’s memory space are protected.

Once your NExT is installed, you’ll be able to use any NFC smartphone app to write data to the tag and not need to be afraid of accidentally locking the tag, or changing the configuration bytes, or someone maliciously locking your tag or changing your password. We suggest using NXP’s TagWriter app.