News for hackers. Stuff that matters.
Re:VPN location claims don't match real traffic exits by dsl on Sunday December 14, 2025 @04:38AM (#46261920)
At my previous company we had a subscription to Spur Intelligence. It is like Palantir for IP address info, and probably the closest to what you are talking about.

They recently added GeoIP to their data and in the bit of testing I was able to do before I left it was scary good. I also had an amusing chat with one of their engineers at a conference about how you can spoof IPInfo's location probes...

Re:VPN location claims don't match real traffic exits by reincoder on Sunday December 14, 2025 @06:50AM (#46262416)
> how you can spoof IPInfo's location probes...

Interesting. I would love to know how this is possible. Like with Geofeed or something else?

Re:VPN location claims don't match real traffic exits by monerozcash on Sunday December 14, 2025 @12:30PM (#46264874)
If you're doing latency-based probing, location spoofing is presumably possible to an extent by adding artificial delays and possibly spoofing ICMP "TTL expired" packets like https://github.com/blechschmidt/fakeroute
Re:VPN location claims don't match real traffic exits by reincoder on Monday December 15, 2025 @04:49AM (#46272345)
I am not sure whether this kind of IP spoofing will impact our accuracy because we will likely identify the noise and behavioral anomaly and discard the location hint derived from traceroute.

We have tons of historical traceroute data patterns, and generic traceroute behaviors are likely modeled out internally. So, if you can spoof the traceroute to your IP address, our traceroute-based location hint scoring weight for that IP address will decrease, and we will rely on the other location hints.

You have to be extremely deliberate to misguide us. But I would love to see this in action, though.

Re:VPN location claims don't match real traffic exits by monerozcash on Monday December 15, 2025 @07:31AM (#46273628)
Yeah, I doubt there are more than a couple of hosts on the entire internet serving fake traceroutes anyway. Even finding hosts that don't enforce BCP38 requires quite some effort these days.
Re:VPN location claims don't match real traffic exits by dsl on Monday December 15, 2025 @01:24AM (#46271071)
I don't think it is fair to IPInfo to give the specifics publicly, because once you have the "ah ha" moment you realize it is an entire class of difficult to address problems with how they use their sensor network. That knowledge only helps the bad guys.
Re:VPN location claims don't match real traffic exits by reincoder on Monday December 15, 2025 @04:39AM (#46272250)
We are actively trying to improve our system and build it as figuratively 'antifragile'. We can not afford to get comfortable and we need to constantly find faults in it. If you know anything, you can contact our founder or me directly.

The problem is that everyone knows we are the most accurate data provider and our growth is exponential. To my knowledge, most cybersecurity teams use our data to some degree. We cannot risk having any secrets out there that could disrupt the accuracy of the system. We are aware of several cases where accuracy may be affected, with the most notable being adversarial geofeed submissions.

If the issue is an adversarial geofeed submission, it is a well-known problem. When active measurement fails, we have to fallback to some location hint. There are layers of location hints we have to fall through to ultimately landing on echoing geofeed location hint.

But aside from that... I'm not sure what could possibly impact us. A substantial systemic malicious change in data accuracy seems highly unlikely and quite impossible.

Re:VPN location claims don't match real traffic exits by immibis on Monday December 15, 2025 @04:43AM (#46272285)
Why do we assume that only "bad guys" would want to bypass internet censorship?