nyanbinary

@nyanbinary@infosec.exchange

Little goblin with catears.

Unfinished projects, complaining about computers, reinventing the wheel (badly), has not fully read any docs since 2015.

Proud bot parent to four failsons:
@enojifier_bot
@dreizehnzwoelf_bot
@perfect10_bot
@dotdotslash_bot

Testimonials:
"not helpful" @LucasWerkmeister

All my opinions are that of my employer but they don't know it yet & I am not telling you were I work. Apropos: If you need some idiot to kick computers for purposes of making them secure hmu, this job fucking sucks (vulnerability management, automation/engineering for your soc/isrt, ...).

PFP by a lizard that I am pretty sure transitioned at some point but I kinda lost contact with around the same time so I might only know their deadname & at this point it's too awkward to seek them out & ask. So instead I am going to credit them by their last discord handle I am aware of: fuck, md

Languages
German, English
Pronomen (🇩🇪)
egal
Pronouns (🇬🇧/🇺🇸)
name reference > they/it > whatever
18Posts
0Following0Followers
nyanbinary@nyanbinary@infosec.exchange

Replying to @sharkfie@infosec.exchange

@sharkfie ok, but like, the question still is: Who/how is this linkage connected.

Lets take 26. as an example:

According to Microsoft records, on or about May 12, 2025, at 19:21 UTC—when, according to ngrok records, the ngrok account was created—the device with the GDID accessed, among other ngrok pages, “dashboard.ngrok.com/signup,” the ngrok page to set up an ngrok account.

ngrok isn't MS & afaik isn't even Azure-hosted. I'm trying to look for a way that MS still would be able to know about the page visit for the device ID without just pulling non-anonymized browsing data from device, lmao.