{"id":924,"date":"2026-11-16T22:02:55","date_gmt":"2026-11-16T22:02:55","guid":{"rendered":"https:\/\/anthonyparkes.co.uk\/?p=924"},"modified":"2026-11-16T22:09:36","modified_gmt":"2026-11-16T22:09:36","slug":"scan-me-what-your-conference-badge-qr-code-actually-says","status":"publish","type":"post","link":"https:\/\/anthonyparkes.co.uk\/?p=924","title":{"rendered":"Scan Me: What Your Conference Badge QR Code Actually Says"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\"><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Every conference ends the same way: a selfie, a LinkedIn post, and a lanyard with a QR code printed right on the badge. Microsoft Ignite is no exception. I had one in front of me, so I scanned it to see what was inside. A QR code isn\u2019t a secret \u2014 it\u2019s just a picture of data, and anything a camera can read, so can you.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Point a reader at the badge and you don\u2019t get a name. You get a URL: a genuine Microsoft link, a long badge ID, and a lump called \u201cdata\u201d. That data is URL-encoded Base64. Decode it and you get a mess \u2014 a few readable characters, then a stream of accented gibberish. The tell is the pattern: it\u2019s a JavaScript string scrambled in the browser. Which means it can be unscrambled outside of it.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">And it was barely scrambled. Not real encryption \u2014 just a fixed shift of each character, a Caesar cipher\u2019s grown-up cousin. To break one you need a scrap of text you already know. The badge helpfully prints it on the front: the attendee\u2019s name and company. Subtract the letters you know, and the key drops straight out \u2014 twenty characters, repeating, with the event\u2019s own name sitting inside it. Hand-rolled, and the same for every badge at the show.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Apply it and the blob falls open:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">1785137280637001Jrkt^Firstname^Lastname^Company Ltd^<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Name, company, badge ID. I tried a second badge \u2014 different person, different company, registered three months apart \u2014 and the exact same key decoded it. Crack one, crack them all.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">So how bad is it? Honestly, barely. Every field is already printed on the front of the badge. The one thing you can\u2019t see with your eyes is buried in the badge ID: it starts with a timestamp, down to the millisecond, revealing the precise moment that person registered. Mildly creepy, entirely harmless.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Which is the whole point. This is the benign version of a problem that often isn\u2019t. \u201cData hidden in a code, barely scrambled\u201d describes a lot of what you photograph without thinking. A boarding-pass barcode holds your name and booking reference \u2014 frequently enough to log into the airline and change your flight. Those \u201cscan to save my details\u201d squares carry home addresses and personal mobiles. And a bonus that isn\u2019t even a QR code: a photo of your keys. The cuts on a house or office key can be read straight off a clear picture and copied by a locksmith. That \u201cwe got the keys!\u201d snap is, to the wrong person, an order form.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">None of this is a reason to panic. It\u2019s a reason to pause before the photo goes up. Blur the QR. Treat boarding passes like passwords. Keep your keys in your pocket. A code printed big and glossy isn\u2019t private \u2014 it\u2019s just portable.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><em>Scan before you share. The camera always sees more than you do.<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Every conference ends the same way: a selfie, a LinkedIn post, and a lanyard with a QR code printed right on the badge. Microsoft Ignite<\/p>\n","protected":false},"author":2,"featured_media":926,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"template-fullwidth.php","format":"standard","meta":{"footnotes":""},"categories":[22],"tags":[],"class_list":["post-924","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-digital-rights"],"_links":{"self":[{"href":"https:\/\/anthonyparkes.co.uk\/index.php?rest_route=\/wp\/v2\/posts\/924","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/anthonyparkes.co.uk\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/anthonyparkes.co.uk\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/anthonyparkes.co.uk\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/anthonyparkes.co.uk\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=924"}],"version-history":[{"count":1,"href":"https:\/\/anthonyparkes.co.uk\/index.php?rest_route=\/wp\/v2\/posts\/924\/revisions"}],"predecessor-version":[{"id":925,"href":"https:\/\/anthonyparkes.co.uk\/index.php?rest_route=\/wp\/v2\/posts\/924\/revisions\/925"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/anthonyparkes.co.uk\/index.php?rest_route=\/wp\/v2\/media\/926"}],"wp:attachment":[{"href":"https:\/\/anthonyparkes.co.uk\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=924"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/anthonyparkes.co.uk\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=924"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/anthonyparkes.co.uk\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=924"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}