> Microsoft provided the FBI with the history of IP addresses tied to that specific GDID.
This article, and most articles about this, doesn't explain where FBI got that GDID from. Ok, Microsoft has a list of IP addresses that has been used by a computer with a certain GDID, but FBI needs to get the GDID in the first place, and then try to bind that to a person.
I found another article that explains the process a bit better:
> Stokes got caught because he used the same Windows device for everything, and the GDID stitched all of it back together after the fact.
> Scattered Spider members phoned the jewelry retailer’s IT help desk from Google Voice numbers, posed as locked out employees, and talked support staff into resetting three accounts, two with administrator privileges. From there they installed a tunneling tool called ngrok to get past the retailer’s network defenses, moved roughly 77 gigabytes of data to Amazon cloud storage using ngrok [...]
> Investigators later subpoenaed ngrok and found the account used in the attack had been created on May 12, 2025, at 19:21 UTC from a VPN proxy IP address run by Tzulo, a hosting provider. The IP was a dead end. VPN proxies do that. But the GDID is built different.
> Microsoft’s records showed that at that exact same minute, a Windows device carrying GDID g:6755467234350028 had visited the ngrok signup page. Three hours later, the same GDID visited the retailer’s own website, through the same Tzulo proxy address used to set up the ngrok account. It gave the FBI a device, that don’t rotate the way VPN exit nodes do.
This seems like something that should be easy to confirm, but I haven't seen anyone do it. Do they keep a database of every website visit all Edge users make?
Speculation: if you turn on browser sync so you can have your open tabs and history on different computers, that stuff will be on MS' cloud with your consent, with whatever E2EE they have or claim to have.
But it would be very foolish for a blackhat to turn on browser sync...
They claim it was an ngrok account that was used to host an endpoint used in the compromise, tied to a microsoft account / gdid that was passed when ngrok software was downloaded from the "microsoft store".
I think it's likely that Microsoft is running a process to correlate "new" GDIDs to old ones, ex:
"Oh look, this one has all the same serial numbers of components and attached devices as that other one, it's probably the same computer with a fresh install, let's make a note of that..."
But it is regenerated by reinstalling. So I suspect that its less fingerprint based and more of an in disk IDs thing. Which goes back to if you clear the right things while the system is not running you might be able to change it
I think the difference is that, on Windows, there are background services that constantly ping Microsoft with the device ID. A device ID on its own is not really harmful if it's not exposed to the internet.
Right, the danger here isn't a stable unique ID itself, but the OS "telemetry" which steals [0] it and reports to Big-Brother in ways which betray other information to Big Brother.
There's no informed consent here, the average consumer does not think "Microsoft is tracking every single website I visit and when I visit it in Edge."
[0] It seems wrong to use the verb "leaks" when it's so obviously intentional.
I mean, there's a ton of unique identifiers on machines already tied to hardware and disks, but that must be a systemd thing since my Devuan machine does not have it.
But given there's no cloud accounts on linux I would imagine it's trivially changed just like a NIC's MAC
Also, seems unlikely it would be used for any single-signon with cloud services.
> Microsoft provided the FBI with the history of IP addresses tied to that specific GDID.
This article, and most articles about this, doesn't explain where FBI got that GDID from. Ok, Microsoft has a list of IP addresses that has been used by a computer with a certain GDID, but FBI needs to get the GDID in the first place, and then try to bind that to a person.
I found another article that explains the process a bit better:
> Stokes got caught because he used the same Windows device for everything, and the GDID stitched all of it back together after the fact.
> Scattered Spider members phoned the jewelry retailer’s IT help desk from Google Voice numbers, posed as locked out employees, and talked support staff into resetting three accounts, two with administrator privileges. From there they installed a tunneling tool called ngrok to get past the retailer’s network defenses, moved roughly 77 gigabytes of data to Amazon cloud storage using ngrok [...]
> Investigators later subpoenaed ngrok and found the account used in the attack had been created on May 12, 2025, at 19:21 UTC from a VPN proxy IP address run by Tzulo, a hosting provider. The IP was a dead end. VPN proxies do that. But the GDID is built different.
> Microsoft’s records showed that at that exact same minute, a Windows device carrying GDID g:6755467234350028 had visited the ngrok signup page. Three hours later, the same GDID visited the retailer’s own website, through the same Tzulo proxy address used to set up the ngrok account. It gave the FBI a device, that don’t rotate the way VPN exit nodes do.
https://www.windowslatest.com/2026/07/10/you-cant-fully-disa...
Although this doesn't explain where Microsoft got that traffic data from. How do Microsoft know which sites a computer visit?
They make the default web browser on Windows, and that sends your browsing data if you don't disable its telemetry.
See https://news.ycombinator.com/item?id=48921595
This seems like something that should be easy to confirm, but I haven't seen anyone do it. Do they keep a database of every website visit all Edge users make?
Speculation: if you turn on browser sync so you can have your open tabs and history on different computers, that stuff will be on MS' cloud with your consent, with whatever E2EE they have or claim to have.
But it would be very foolish for a blackhat to turn on browser sync...
They claim it was an ngrok account that was used to host an endpoint used in the compromise, tied to a microsoft account / gdid that was passed when ngrok software was downloaded from the "microsoft store".
That wouldn't explain how they connected the GDID to the visit to the retailers website
> Three hours later, the same GDID visited the retailer’s own website, through the same Tzulo proxy address used to set up the ngrok account.
I think it's likely that Microsoft is running a process to correlate "new" GDIDs to old ones, ex:
"Oh look, this one has all the same serial numbers of components and attached devices as that other one, it's probably the same computer with a fresh install, let's make a note of that..."
I have a sneaking suspicion that that ID can be deleted either with a specific service not running or with Windows powered off.
it is generated from identifiers on device by a remote microsoft system where it is stored ..
But it is regenerated by reinstalling. So I suspect that its less fingerprint based and more of an in disk IDs thing. Which goes back to if you clear the right things while the system is not running you might be able to change it
wow.. How is this not a bigger deal
Obvious workaround to get off windows and use Linux…
But do any popular linux distributions use an identifier? Ubuntu, Kali, Mint, Arch, etc?
It seems an attractive way for devs to work out telemetry. Awful in reality; but I imagine attractive.
At least Debian and Ubuntu have /etc/machine-id, presumably easily changed - but it’s there.
I think the difference is that, on Windows, there are background services that constantly ping Microsoft with the device ID. A device ID on its own is not really harmful if it's not exposed to the internet.
Right, the danger here isn't a stable unique ID itself, but the OS "telemetry" which steals [0] it and reports to Big-Brother in ways which betray other information to Big Brother.
There's no informed consent here, the average consumer does not think "Microsoft is tracking every single website I visit and when I visit it in Edge."
[0] It seems wrong to use the verb "leaks" when it's so obviously intentional.
I mean, there's a ton of unique identifiers on machines already tied to hardware and disks, but that must be a systemd thing since my Devuan machine does not have it.
But given there's no cloud accounts on linux I would imagine it's trivially changed just like a NIC's MAC
Also, seems unlikely it would be used for any single-signon with cloud services.