Skip to content

Bambu-Research-Group/RFID-Tag-Guide

BranchesTags

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

56 Commits
.github/workflows
.github/workflows
 
 
examples
examples
 
 
images
images
 
 
OpenSourceRfid.md
OpenSourceRfid.md
 
 
README.md
README.md
 
 
parse.py
parse.py
 
 
traceKeyExtractor.py
traceKeyExtractor.py
 
 

Repository files navigation

Bambulab RFID Tag Guide

This guide gives you a basic overview how you can decrypt and read your tags. Since we don't know how Bambulab will react on this guide and the general reverse engineering of the tags: Please don't share you tag's UID and the related keys for now.

We are currently working on a way to submit the tag data in a secure way so analysis on the data could be done.

Table of contents

Project Summary

This is a research group dedicated to documenting the data structures used by Bambulab 3D printers to identify filament data.

FAQs

  • Can I clone tags?
    • Yes, you can read and clone tags using a tool such as a Proxmark3
  • Can I create custom tags?
    • No, tags are digitally signed. Even if you modify the contents, the printer will reject any tags without a valid RSA signature
    • An Open Source RFID Tag has been proposed to allow anyone to create / modify their own tags. This must be adopted by printer manufacturers, or you can mod your own printer for support
  • What are the next steps for this project?
    • Decyphering the rest of the unknwn tag content
    • Custom AMS firmware that allows custom tags to be read while ignoring the signature
    • See Todos/Timeline/Next steps for more info

How do RFID tags work?

Here's a high-level summary of how everything works:

  • BambuLab printers use MiFare 13.56MHZ RFID tags
    • These tags contain a unique ID that is not encrypted (called the UID)
    • In most cases UID is fixed (not-changable). Some "hackable" rfid tags allow you to set the UID to anything you want
  • Blocks (Encrypted)
    • MiFare tags also contain "Blocks" of data. Each block contains info about the spool, such as Material, Color, Manufacturing Date, etc. See Tag stucture section for details
    • The blocks are encrypted, meaning that you need to have a KEY to decipher them
    • Each block is encrypted with a different key
  • Encryption Keys
    • Keys are unique to each RFID tag. Even if you discover the key for one tag, that doesn't mean you can use that same key to unlock a different tag.
    • Keys are likely derived from the UID. The UID goes through an algorithm (known only by Bambu) to reveal a set of keys for each block
    • Keys can be sniffed by using a device (such as a ProxMark 3) to listen in on the communication between the AMS and the rfid tag.
    • Once the keys have been sniffed, they can be saved and used to read the contents of the tag directly (without an AMS). (Reminder, the saved keys will ONLY work for the tag they were sniffed from)
  • RSA Signature
    • One of the blocks contains a 2048-bit RSA Signature
    • RSA signatures are a way to digitally sign / certify authenticity of content, and they are effectively un-breakable (this is how things like cryptocurrency remain secure)
    • RSA signatures encompass all of the data of the RFID tag. Changing a single byte somewhere else in the tag would require a completely different signature to be considered genuine
    • Bambu printers check the content of the tag and then check if the signature is valid. If the signature is invalid, it rejects the tag
  • Cloning Tags
    • Even though there is a signature, a tag can be cloned
    • To clone a tag, it must have the same UID, identical content from the data blocks, and the identical RSA signature
    • Changing even one byte will cause the signature to be invalid, and the tag will be rejected
  • Custom Tags
    • This is very unlikely to happen, mostly due to the RSA signature. Only Bambu has their "Private Key" which is used to digitally sign these tags.
    • To create a custom key, you need to know the following info:
      • UUID -> Encryption Key algorithm (or just use known UID + Key pairs)
      • RSA Signature Private Key. You'd have to get this from bambu, good luck
    • Since Bambulab will likely not remove the signature requirement, you would need custom AMS firmware to read tags and ignore the signature

How to contribute

If you have a Proxmark3 (or other RFID debugging tool), you can sniff and decrypt the contents of your tags and submit them for review. The more data we have, the easier it is to compare differences to learn what each byte represents. A lot of the contents have been deciphered (see Tag stucture), but there is still more unknown data still left.

Todos/Timeline/Next steps

  • Tool for automatic trace analysis
  • Web service for tag submisson with automatic anonymized data publishing to github
  • Tag content analysis
  • Generate keys based on an arbitrary UID

Required Equipment

  • Bambulab 3D Printer with AMS or AMS Lite
  • Bambulab Filament spool or the related tags
  • A Proxmark3-compatible RFID reader
  • The proxmark3 software

Proxmark3 compatible readers

Proxmark3 Easy

A Proxmark3 Easy is sufficient for all the tasks that need to be done. You can buy a clone from Alixepress, Amazon or Dangerous Things.

Hacking a Bambulab Tag and readout of its data

The easiest way to obtain the We document here the most simple approach to get all required A-Keys and the data of the tag. The easiest way is to sniff the data.

Bambulab AMS RFID reader location

The Bambulab AMS RFID readers are located between slots 1&2 and slots 3&4.

Bambulab AMS Lite RFID reader location

The Bambulab AMS Lite RFID readers are located at the base of each spool holder.

For sniffing, you will need to place the Proxmark in between the RFID tag and the reader on the AMS. As there is not much clearance, it is recommended to temporarily remove the low frequency radio (the topmost piece) if you can, as it will not be used in this process.

Proxmark3 placement for sniffing

For sniffing, you will need to place the Proxmark3 against the reader. On the AMS, you may place it on the other side (for example, load the spool into slot one and place the Proxmark3 against the reader in slot 2). On the AMS lite, you will need to place it in between the reader and the spool.

As there is not much clearance, it is recommended to temporarily remove the low frequency radio (the topmost piece) if you can, as it will not be used in this process.

If you place the Proxmark in between the AMS reader and the spool, make sure that spool rotates so that the RFID tag moves away from the reader, otherwise the AMS will assume that it is reading the tag from its neighboring slot and attempt to rewind it until it cannot see the RFID tag.

Dump RFID Contents (.bin)

  1. Run ProxMark3 Software

    In a terminal, run pm3 to start the Proxmark3 Software

  2. Sniff Communication

    • Start sniffing with: hf 14a sniff -c -r
      (hf=High Frequency, 14a=Tag Type, Sniff=command, -c and -r mean "capture on triggers instead of continuously)

    • Place your Proxmark3 between the tag and the AMS. Recommended: Use tape to hold it in place.

    • Load a strand of filament into the AMS. This is what triggers the AMS to attempt to read the RFID tag.

    • Press the button on the ProxMark to end capture after the filament has completed loading

  3. Create a Key Dictionary

    • We will discover keys one at a time and save them to a dictionary file.

    • Navigate to your Proxmark3 software installation directory. This will be specific to your Operating System and Installation.

      • macOS (Intel) Example: /usr/local/Cellar/proxmark3/4.17768/share/proxmark3/
      • macOS (ARM) Eample: /opt/homebrew/Cellar/proxmark3/4.17768/share/proxmark3/
      • Windows Example: TBD
      • Linux Example: TBD

    • Open a text editor and save a blank file called myDictionary.dic into the dictionaries/ folder of your Proxmark3 software installation directory.

      (You can call this file anything you want, but for the rest of this example, we will refer to it as "myDictionary")

    • Leave this file open, we will continue to add keys to it in the next step

  4. Extract Keys From Trace

    • Run trace list -t mf -f myDictionary to view the trace that was recorded from sniffing in the previous step.

      This uses the key dictionary myDictionary.dic that we created in step 3.

    • Read the output and look for anything that mentions a key.

      • Three Possible Formats:

        • key E0B50731BE27 prng WEAK - Follow Step 5
        • nested probable key: 50B0318A4FE7 - Follow Step 6
        • Nested authentication detected. - Follow Step 7

      • Each of these 3 entries can provide us with a valid key. Follow step 5, 6, or 7 depending on which type of key you encounter.

  5. First Key - Plain Text

    • Example: key E0B50731BE27 prng WEAK
    • This is the first key that was discovered by sniffing AMS traffic.
    • Copy/paste this key into the myDictionary.dic file that you created in step 3, then save the file.

  6. Nested Probable Key

    • Example: nested probable key: 50B0318A4FE7
    • Copy/paste this key into the myDictionary.dic file that you created in step 3, then save the file.

  7. Nested Authentication Key

    • Example: 
      Nested authentication detected.
tools/mf_nonce_brute/mf_nonce_brute 75066b1d 4db2f2ac 0101 70fcdd3d 328eb1e6 1101 28b75cfd 0010 5196401C
    • Open a second terminal window, and change directories into your Proxmark3 software installation directory. This is specific to your OS and PM3 installation.
      • macOS/Linux: cd $(brew --prefix proxmark3)/share/proxmark3/
      • Windows: TBD
    • CD into the tools folder cd tools/
    • Copy the command from ProxMark starting at mf_nonce_brute, including all the arguments (random letters/numbers) after it, and run the program from the tools/ directory.
      • Example (macOS/Linux): ./mf_nonce_brute 75066b1d 4db2f2ac 0101 70fcdd3d 328eb1e6 1101 28b75cfd 0010 5196401C
      • Example (Windows): mf_nonce_brute.exe 75066b1d 4db2f2ac 0101 70fcdd3d 328eb1e6 1101 28b75cfd 0010 5196401C
    • The program will discover a key. Copy/paste this key into your myDictionary.dic file, and SAVE IT.
      • Example Output: 
        Valid Key found [ 202efd3dcdfd ]

  8. Check Keys (Optional)

    • If you want to check how many valid keys you've discovered, you can do this test

    • This is optional, and you can choose to wait until you have discovered all of the keys

    • WARNING: Performing a key check will erase the trace that you recorded during step 2, and will require you to re-sniff data (repeat step 2)

      • If you want to save your trace to avoid re-sniffing, use trace save -f <trace-name> and trace load -f <trace-name>

    • Run hf mf fchk --1k -f myDictionary to test your keys

      • Example Output (showing 11/16 keys discovered): 
        [+] found keys:

[+] -----+-----+--------------+---+--------------+----
[+]  Sec | Blk | key A        |res| key B        |res
[+] -----+-----+--------------+---+--------------+----
[+]  000 | 003 | E0B50731BE27 | 1 | ------------ | 0
[+]  001 | 007 | 63654DB94D97 | 1 | ------------ | 0
[+]  002 | 011 | 387C06EFFDC8 | 1 | ------------ | 0
[+]  003 | 015 | 38963E577E43 | 1 | ------------ | 0
[+]  004 | 019 | 8A3EA2564692 | 1 | ------------ | 0
[+]  005 | 023 | 935E0F11857A | 1 | ------------ | 0
[+]  006 | 027 | EBC8F7D23A06 | 1 | ------------ | 0
[+]  007 | 031 | DD6128F13D4C | 1 | ------------ | 0
[+]  008 | 035 | ------------ | 0 | ------------ | 0
[+]  009 | 039 | 4E470B09521F | 1 | ------------ | 0
[+]  010 | 043 | 50EB8811A69C | 1 | ------------ | 0
[+]  011 | 047 | 4BDD25091824 | 1 | ------------ | 0
[+]  012 | 051 | ------------ | 0 | ------------ | 0
[+]  013 | 055 | ------------ | 0 | ------------ | 0
[+]  014 | 059 | ------------ | 0 | ------------ | 0
[+]  015 | 063 | ------------ | 0 | ------------ | 0
[+] -----+-----+--------------+---+--------------+----
[+] ( 0:Failed / 1:Success )

  9. Find Remaining Keys

    • Repeat step 4 until all 16 keys are discovered
    • Your dictionary may be larger than 16 entries if you accidentally copied a duplicate key or an invalid key. These invalid entries are fine, and you can ignore them
    • Recommended: When you think you have discovered all 16 keys, perform step 8 to verify that your keys are correct.

  10. Convert Dictionary to Key File

  • Run hf mf fchk --1k -f myDictionary --dump to create a key file
  • The program will report the destination of the key file that it saved. Copy this filepath to your clipboard
    • Example: 
      [+] Found keys have been dumped to /Users/mitch/hf-mf-75066B1D-key.bin
  1. Dump RFID Contents
  • Run hf mf dump -k [path-to-keyfile] to dump the contents of the tag using the 16 keys we discovered
  • There should be no errors
  • The output should tell you where your .bin file is saved
    • Example: 
      [+] saved 1024 bytes to binary file /Users/mitch/hf-mf-75066B1D-dump.bin

Tag Documentation

This contains documentation for the known and unknown data that is contained in each block on the RFID tag.

Block Overview

Summary of what kind of data is stored in each block. Detailed info for each block is documented below.

sec blk Data
0 0 Block 0 UID and Tag Manufacturer Data
0 1 Block 1 Tray Info Index
0 2 Block 2 Filament Type
0 3 Block 3 MIFARE encryption keys, Unrelated to BambuLab
1 0 Block 4 Detailed Filament Type
1 1 Block 5 Spool Weight, Color Code
1 2 Block 6 Min/Max Hotend, Bed Temp, Bed Temp Type, Drying Time, Drying Temp
1 3 Block 7 MIFARE encryption keys, Unrelated to BambuLab
2 0 Block 8 X Cam Info
2 1 Block 9 Tray UID
2 2 Block 10 Unknown
2 3 Block 11 MIFARE encryption keys, Unrelated to BambuLab
3 0 Block 12 Production Date/Time
3 1 Block 13 Unknown
3 2 Block 14 Unknown
3 3 Block 15 MIFARE encryption keys, Unrelated to BambuLab
4 0 Empty
4 1 Empty
4 2 Empty
4 3 Block 19 MIFARE encryption keys, Unrelated to BambuLab
5 0 Empty
5 1 Empty
5 2 Empty
5 3 Block 23 MIFARE encryption keys, Unrelated to BambuLab
6 0 Empty
6 1 Empty
6 2 Empty
6 3 Block 27 MIFARE encryption keys, Unrelated to BambuLab
7 0 Empty
7 1 Empty
7 2 Empty
7 3 Block 31 MIFARE encryption keys, Unrelated to BambuLab
8 0 Empty
8 1 Empty
8 2 Empty
8 3 Block 35 MIFARE encryption keys, Unrelated to BambuLab
9 0 Empty
9 1 Empty
9 2 Empty
9 3 Block 39 MIFARE encryption keys, Unrelated to BambuLab
10-15 * RSA-2048 Signature

The first part of the filament serial number seems to be the Tag UID.

Note

All numbers are encoded as Little Endian (LE).

MIFARE Encryption Keys

Every 4th block (eg Sector X, Block 3) contains encryption keys that are part of the MIFARE RFID standard. This has nothing to do with BambuLab's memory format. All BambuLab tags use the same Permission Bits (Access Control)

Example Data: AA AA AA AA AA AA PP PP PP PP BB BB BB BB BB BB

position length type Description
0 (AA) 6 RAW Bin A-Key
6 (PP) 4 RAW Bin Permission Bits (Access Control)
ALWAYS 87 87 87 69 (hex) for Bambu Tags
10 (BB) 6 RAW Bin B-Key (always 00 00 00 00 00 00 for Bambu tags)

Block 0

Note: Block 0 is Read-only. The contents are set by the tag manufacturer.

Example Data: AA AA AA AA BB BB BB BB BB BB BB BB BB BB BB BB

position length type Description
0 (AA) 4 string Tag UID
4 (BB) 12 RAW Bin Tag Manufacturer Data

Block 1

Example Data: AA AA AA AA AA AA AA AA BB BB BB BB BB BB BB BB

position length type Description
0 (AA) 8 string Tray Info Index - Material Variant Identifier
8 (BB) 16 string Tray Info Index - Unique Material Identifier

Block 2

Example Data: AA AA AA AA AA AA AA AA AA AA AA AA AA AA AA AA

position length type Description
0 (AA) 16 string Filament Type

Block 4

Example Data: AA AA AA AA AA AA AA AA AA AA AA AA AA AA AA AA

position length type description
0 (AA) 16 string Detailed Filament Type

Known Values:

  • PLA Basic
  • PLA Tough
  • Support for PLA
  • PLA-CF
  • PETG Basic

Block 5

Example Data: AA AA AA AA BB BB __ __ CC CC CC CC __ __ __ __

position length type Description
0 (AA) 4 RGBA Color in hex RBGA
4 (BB) 2 uint16 (LE) Spool Weight in grams (E8 03 --> 1000 g)
8 (CC) 8 float (LE) Filament Diameter in milimeters

Block 6

Example Data: AA AA BB BB CC CC DD DD EE EE FF FF __ __ __ __

position length type Description
0 (AA) 2 uint16 (LE) Drying Temperature in °C
2 (BB) 2 uint16 (LE) Drying time in hours
4 (CC) 4 uint16 (LE) Bed Temerature Type (types unknown)
6 (DD) 2 uint16 (LE) Bed Temperature in °C
8 (EE) 2 uint16 (LE) Min Temperature for Hotend in °C
10 (FF) 2 uint16 (LE) Max Temperature for Hotend in °C

Block 8

Example Data: AA AA AA AA AA AA AA AA AA AA AA AA BB BB BB BB

position length type description
0 (AA) 12 RAW Bin X Cam info
12 (BB) 4 float (LE) Nozzle Diameter...?

Block 9

Example Data: AA AA AA AA AA AA AA AA AA AA AA AA AA AA AA AA

position length type Description
0 (AA) 16 string Tray UID

Block 10

Example Data: __ __ __ __ AA AA __ __ __ __ __ __ __ __ __ __

position length type Description
4 (AA) 2 uint16 (LE) Spool Width in µm (E1 19 --> 6625µm --> 66.25mm )

Block 12

Example Data: AA AA AA AA AA AA AA AA AA AA AA AA AA AA AA AA

position length type Description
0 (AA) 16 string Production Date and Time in ASCII (<year>_<month>_<day>_<hour>_<minute>)

Block 13

Example Data: AA AA AA AA AA AA AA AA AA AA AA AA AA AA AA AA

position length type Description
0 (AA) 16 string Short Production Date/Time...?

Block 14

Example Data: __ __ __ __ AA AA __ __ __ __ __ __ __ __ __ __

position length type Description
4 (AA) 2 uint16 (LE) Filament length in meters...?

Compatible RFID tags - By generation

Gen 1 --> Not compatible(due to AMS checking if tag is unlockable with command 0x40)

Gen 2 --> Works

Gen 2 OTW --> Not tested

Gen 3 --> Not tested

Gen 4 --> Not tested(The best option but pricey and hard to source in small chip formfactor)

About

Instructions on how to read out the bambulab nfc tags

Resources

Readme
Activity
Custom properties

Stars

514 stars

Watchers

101 watching

Forks

53 forks
Report repository

Releases

No releases published

Packages

 
 
 

Contributors 6

Languages