| Term | Meaning |
|---|---|
| WUP-SAK | SAK Value found during the Wake up & Anti-collision process, what you would see reported from a basic search. |
| Vanity SAK | SAK Value represented in Block 0 of a Mifare Classic, on legitimate cards this does not inform the value of the WUP-SAK. |
| Magic Card | An illegitimate card capable of changing it's UID; some magic cards are also able to change other values such as ATQA/SAK. |
equipter
/ SAK Swapping.md
Last active
April 11, 2025 19:29
Explaination of Mifare Classic SAK Swapping anti cloning defense
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| BEGIN:VCARD | |
| VERSION:3.0 | |
| FN;CHARSET=UTF-8:Samwise whiskey Gamgee | |
| N;CHARSET=UTF-8:Gamgee;Samwise;whiskey;NFC;jr | |
| NICKNAME;CHARSET=UTF-8:Sam | |
| GENDER:M | |
| UID;CHARSET=UTF-8:54838c80 | |
| BDAY:20030103 | |
| EMAIL;CHARSET=UTF-8;type=HOME,INTERNET:[email protected] | |
| PHOTO;ENCODING=b;TYPE=JPEG:/9j/4AAQSkZJRgABAQAAAQABAAD/2wCEAAkGBxMTEhUSEhMVFRUVFRUVFRUVEhUVFRUVFRUWFhUVFRUYHSggGBolGxUVITEhJSkrLi4uFx8zODMtNygtLisBCgoKDg0OGhAQGy0lHR8tLS0tLS0rLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLf/AABEIAOEA4QMBIgACEQEDEQH/xAAbAAACAwEBAQAAAAAAAAAAAAADBAACBQEGB//EADgQAAIBAgQEBAUDAgUFAAAAAAABAgMRBCExQQUSUWETcYGRFCKhsfAGMsEV8TNCUnLRI2JzwuH/xAAaAQADAQEBAQAAAAAAAAAAAAABAgMABAUG/8QAJhEAAgICAgICAgIDAAAAAAAAAAECEQMhBBIxQRMiFFEyQgUVcf/aAAwDAQACEQMRAD8A+cYt55CkhmvHMUa1PRxw0Gb2DR2m7EIkW6kuwxUV/mXqcouzX56EoTtqElT3RPr6KL9hqtFWU4vLp0fRl6Ks+z+gtCbV++qC4Sqv2y0enZiPG6GUlYzVoatWa7CjgNSp7ry1JyXNFUMIyp6B6egz4F1lqifD6dx20zdRS2aYenR3LuhqEw8c7AktaMkHw9OLTUjOxFH5uUekmtBbDq8u9svM0INWwyfhBcJB7f7fRlFJ3jHV6I0/AcKav+5zDYbhjivF32VjlnKKtsqosB8C+R31eojCleF+ |
NDEF (NFC Data exchange format) is a method of transferring (relatively small amounts of) information from a passive or actively emulated tag by way of "records" which specify the type of information is being received and the function it is meant to have.
iPhones do not have a full suite of NDEF compatibility, the reason for this is unknown (to me at least), what this means is the background polling on iPhones will not interpret some specific record types, with compatible NDEF records, a notification will pop up directing the user to follow the received data into its respective app to complete whatever action was intended by the record.
Below are the options offered by NFC Tools on IOS for NDEF Encoding, some of the options below are other record types but with a specific function IE social links are just URLs.