Mullvad exit IPs are surprisingly identifying
tmctmt.com/posts/mullvad-exi…
You can get an approximate edge-to-origin timing on most Cloudflare sites by subtracting the latency of /cdn-cgi/trace (hits edge only) from your normal requests' latency.
If you have a bunch of proxies you can cycle between edges and get a good idea of the origin's geoloc
Demo: gist.github.com/tmctmt/3f1d2…
It uses Mullvad proxies to cycle edges so you need to be connected to their VPN to use this.
I made a searchable pastebin archive since there weren't any left: pastes.zip
I can confirm that Mullvad's new mitigation (currently available on select servers) indeed fixes the IP position correlation flaw.
On Friday the 15th of May, we became aware of a fingerprinting issue affecting Mullvad users.
We have a method which changes this behaviour currently being tested, with plans to begin rolling it out to our VPN servers in the coming weeks.
Read more here: mullvad.net/blog/exit-ip-fin…
Just released a tool for identifying domains under common ownership using Cloudflare nameserver pair correlation (with some historical data support!):
tmctmt.github.io/cloudflare-…
For those unfamiliar with the technique, this post by Aidan Thomson describes it pretty well:
interrupt.sh/blog/discoverin…
tmctmt retweeted
A novel-ish means of finding Satoshi, including a website where you can test your own guesses.
All bad writing is by me. Done in collaboration with @tmctmt.
foxchapelresearch.substack.c…
If you're interested in funding this, please lmk.
tmctmt retweeted
Totally forgot to post about this, but after researching, I had suspicion that some of the netflow data from tzulo.com (AS11878) was being fed into Team Cymru's platform. A bunch of VPN providers, including Mullvad (22% of their servers!), ivpn and Windscribe were Tzulo clients at the time. After trying direct contact with Tzulo and getting a not-so-helpful response, I decided to reach out to the VPNs. Out of all of them, surprisingly @windscribe was the only one that took a closer look at it. They escalated it to Tzulo, who confirmed the culprit was Sharktech, their upstream provider (also mentioned in my initial research). Tzulo has since migrated away from them, but this confirms netflow data from some of these servers was indeed being captured before September 2025 (when Windscribe sent me this email). Hopefully this has contributed a bit to the privacy community.
Kudos to @windscribe for caring and to @404mediaco for inspiring this research :)
Spent pretty much the whole day compiling information on how and from where Team Cymru captures netflow data.
I've published an initial version of all the resources I could find here (Includes a WIP version of ISPs that share data with them!):
github.com/beescuit/netflow-…
The worst part about the YellowKey exploit is the sheer number of misinformed people who are unknowingly going to bottleneck their SSD speeds by like 80% after switching to VeraCrypt instead of simply using password-based BitLocker
github.com/veracrypt/VeraCry…
reddit.com/r/VeraCrypt/comme…
























