Sem descrição

AloneLiberty a50dab5d71 Migrate FAQ to wiki, add guide links há 2 anos atrás
assets 0c13737038 1.0.0 - Public release há 2 anos atrás
lib c9654abd57 1.1.1 - Improve calibration cycle (hope nothing breaks) há 2 anos atrás
scenes 0c13737038 1.0.0 - Public release há 2 anos atrás
LICENSE.md 0c13737038 1.0.0 - Public release há 2 anos atrás
README.md a50dab5d71 Migrate FAQ to wiki, add guide links há 2 anos atrás
TODO.md f7f453f883 1.1.0 - Text changes, nothing new há 2 anos atrás
application.fam f7f453f883 1.1.0 - Text changes, nothing new há 2 anos atrás
mifare_nested.c 0c13737038 1.0.0 - Public release há 2 anos atrás
mifare_nested.h 0c13737038 1.0.0 - Public release há 2 anos atrás
mifare_nested_i.h c9654abd57 1.1.1 - Improve calibration cycle (hope nothing breaks) há 2 anos atrás
mifare_nested_worker.c e3651bde62 1.1.0 - Change nested folder name to .nested, remove .keys file after search, bug fixes há 2 anos atrás
mifare_nested_worker.h e3651bde62 1.1.0 - Change nested folder name to .nested, remove .keys file after search, bug fixes há 2 anos atrás
mifare_nested_worker_i.h 0c13737038 1.0.0 - Public release há 2 anos atrás

README.md

Mifare Nested Attacks for Flipper Zero

Ported nested attacks from proxmark3 (Iceman fork)

Download

FlipC.org

Currently supported attacks

  • nested attack
  • static nested attack

Warning

App is still in early development, so there may be bugs. Your Flipper Zero may randomly crash/froze. Please create issue if you find any bugs (one bug = one issue).

Disclaimer

The app provided for personal use only. Developer does not take responsibility for any loss or damage caused by the misuse of this app. In addition, the app developer does not guarantee the performance or compatibility of the app with all tags, and cannot be held liable for any damage caused to your tags/Flipper Zero as a result of using the app. By using this app you confirm that the tag belongs to you, you have permission to preform the attack and you agree to hold the app developer harmless from any and all claims, damages, or losses that may arise from its use.

I need your help!

To successfuly recover keys from nested attack we need to correctly predict PRNG value. But we have a problem with that. Due to lack of my knowlege of Flipper Zero NFC HAL, PRNG can jump by quite large values (not like Proxmark3). So app is trying to find a delay where PRNG can be predicted accurately enough. This is not the best option, because we have to try to recover a bunch of unnecessary keys, which takes a lot of time and RAM and also spend a lot of time on timings. I don't know how to fix it.

UPD: Chameleon Ultra devs faced same issue. They seems to use same method: nested.c (better know from the beginning of development...)

How to use it?

Detailed guide: EN RU.

FAQ

For frequently asked questions, please refer to the FAQ: EN RU.

Contacts

Telegram: @libertydev