A couple of newbie questions

Projects
2

  1. Yes, you will need to mod your car if you want to start it via implant. AFAIK the tech used in car keyfobs is pretty proprietary, the only car that is implant-compatible out of the box is the Tesla Model 3, and that’s only with a TeslaFlex implant, or the upcoming VivoKey Apex. They also don’t run at the frequency used by any implant. Regardless, they don’t work like traditional implants, and can’t be replaced by them. I’m working on a project writeup right now for replacing an ignition switch with a custom implant-based RFID system, should be posted in the next week or so. This will apply to older style ignitions, however.

  2. Yes, I would still look at a NExT. The xEM alone can be a bit limited without a Proxmark, which is a tool for RFID hacking/experimentation. It’s not very beginner-friendly. For a beginner, the Spark 2 won’t have many useful features. At the current moment, it can do basic UID-based high-frequency authentication, website login on a handful of sites via the VivoKey app, and it can open a profile or webpage of your choice when tapped with someone’s phone. It’s a neat piece-of-kit, and nice to have, but I definitely wouldn’t advise it as your only implant. The NExT will give you a high frequency implant that you can read/write with your phone, as well as a low-frequency side that you can use with an xAC (access controller sold by DT, can be used for your own projects). You will occasionally see something called the “blue cloner” mentioned. This can be used for cloning low frequency credentials onto a NExT or an xEM, but there’s a fairly large risk of potentially bricking your implant. I would definitely advise buying a proxmark 3 easy if you go this route, especially since DT sells them now. If you don’t want to spring for the NExT, I would then recommend the Cyborg Transformation bundle, with an xEM and the xNT. It’s cheaper, but it’s 2 implants instead of one. Same functions at the NExT though. Regardless, if you want to do anything with your phone or a PC, you’re gonna want an xNT or a NExT most likely.

  3. xSIIDs don’t really have any issues for the end-user. There’s issues with writing to the last kilobyte or so of memory, but if you’re just writing websites, contact info, etc., it works identically to an xNT or a NExT. Depending on how deep you wanted to go, you can also write your own programs to take advantage of the last bit of the storage. Idk what your experience is there.

Both the xSIID and the xLED do need to be quite close, as well. I’d say with almost any reader (disregarding super long range readers) you could expect a centimeter or two max. Mine lights ~1.5cm away I’d say with most readers. As mentioned before, car fobs use a different frequency (315MHz I believe), so neither a low-frequency or high-frequency xLED could be lit by your car.

I would say there’s no way to do what you want here regarding lighting up an implant. There’s projects ongoing to build a bracelet that would light up implants, but that’s still a ways away it seems.

  1. The flexMT is indeed implantable, but it’s more involved than traditional x-series implants, being a flex device, and a decent sized one at that. You can find an excellent thread here by @vampire_blue covering his experience with the flexMT:
    MagicFlex Install and Notes

Feel free to let me know if you have any more questions.

4 Likes