Uploaded June 2025 | Updated September 2026, 3 weeks ago
Counter-RAPTOR: Safeguarding tor against active routing attacks:
arxiv.org/pdf/1704.00843
Credit: /u/Yugong on Dread
Also see:
Y. Sun, A. Edmundson, L. Vanbever, O. Li, J. Rexford, M. Chiang, and
P. Mittal, “Raptor: routing attacks on privacy in Tor,” in 24th USENIX
Security Symposium (USENIX Security 15), 2015, pp. 271–286.
en.wikipedia.org/wiki/OVHcloud
w3techs.com/technologies/details/dc-ovhsasSo here's the deal: Tor's broken at the infrastructure level, and it's not because of some fancy NSA exploit or browser vulnerability. Princeton researchers mathematically proved that BGP routing attacks can unmask millions of users, and they're calling it RAPTOR (Routing Attacks on Privacy in Tor).
The attack is stupidly simple: BGP, the internet's routing protocol from the 1980s, has zero authentication. Anyone can announce they own any IP address, and other networks just... believe them. When you connect to what you think is a Tor guard relay in Germany, an attacker can redirect your traffic to their servers first, see your real IP, then forward it to the actual relay. Your anonymity dies before you even enter the Tor network.
The worst part? Major hosting providers like OVH (resilience score: 0.408) and Hetzner are incredibly vulnerable. When someone attacks their routing, 60% of users get exposed. And this isn't theoretical - real attacks happened in 2023 (AWS, 17 relays compromised) and 2024 (Hetzner, 45% of users exposed).
Princeton gave Tor the solution - Counter-RAPTOR - with working code nearly a decade ago. It includes resilience-based relay selection and real-time BGP monitoring. But here we are in 2025, and Tor still uses bandwidth-weighted selection that guides users straight to vulnerable relays.
State-sponsored attacks are up 300% according to Cloudflare. Russian ISPs hijacked 62 relays to unmask activists. The threat is real, active, and getting worse.
Full research paper linked in pinned comment. Time to demand Tor actually implements these fixes.
☆-----☆-----☆-----☆-----☆ CHAPTERS ☆-----☆-----☆-----☆-----☆
00:00 Tor is Broken at Infrastructure Level
00:36 What is BGP and Why It Matters
01:03 BGP's Fatal Security Flaw from the 1980s
01:34 How RAPTOR Attack Destroys Your Anonymity
02:18 Multiple BGP Attack Methods Explained
03:06 Princeton Researchers Measure Every Tor Relay
03:41 60% of OVH Users Exposed During Attacks
04:30 Hosting Companies Are Sitting Ducks
05:25 Why Some Networks Have Terrible Resilience
06:53 Internet Hierarchy Makes Tor Vulnerable
07:51 High Bandwidth Relays = High Risk
08:21 Real BGP Attacks Compromising Tor Relays
09:09 2023-2024 Attacks on AWS and Hetzner
09:55 State-Sponsored Attacks Up 300%
10:46 Russian ISP Hijacks 62 Relays
11:11 Counter-RAPTOR Defense System
12:09 New Guard Relay Selection Algorithm
13:29 Real-Time BGP Monitoring Solution
15:15 Detection Methods That Actually Work
16:11 9 Years Later - Tor Still Hasn't Fixed This
17:05 RPKI Can't Save You
18:51 BGP Attacks Bypass All Tor Security
19:37 You Can't Detect These Attacks
20:32 Individual Users Are Defenseless
21:22 The Math is Brutal - Millions Exposed
22:23 Why Tor Must Act Now
#tor #torproject #anonymity #cybersecurity #opsec
☆-----☆-----☆-----☆-----☆ SOCIAL MEDIA ☆-----☆-----☆-----☆-----☆
🎙️ Podcast: rss.com/podcasts/darknet
🌐 Official Website: doingfedtime.com
🌐 Official Website Mirror: sambent.com
📘 Facebook: facebook.com/TheOfficialSamBent
🐦 Twitter/X: twitter.com/DoingFedTime
💼 LinkedIn: linkedin.com/in/sam-bent
📧 Email: contact@sambent.com
📱 TikTok: facebook.com/TheOfficialSamBent
📚 Amazon Author Page: amazon.com/stores/Sam-Bent/author/B0BHX5V81S
🌐 Dread (Onion Link): http://dreadytofatroptsdj6io7l3xptbet6onoyno2yv7jicoxknyazubrad.onion/d/doingfedtime
🌐 Pitch (Onion Link): http://pitchprash4aqilfr7sbmuwve3pnkpylqwxjbj2q5o4szcfeea6d27yd.onion/@doingfedtime
🐙 GitHub: github.com/DoingFedTime
👾 Reddit (User Account): reddit.com/user/reservesteel9
📽️ Rumble: rumble.com/c/SamBent
🛡️ Breach Forums (Onion Link): http://breached26tezcofqla4adzyn22notfqwcac7gpbrleg4usehljwkgqd.onion/User-SamBent
📸 Instagram: instagram.com/sambentoffical
📌 Pinterest: pinterest.com/DoingFedTime
☆-----☆-----☆-----☆-----☆ LEGAL STUFF☆-----☆-----☆-----☆-----☆
The information provided in this video is intended for educational purposes only. It is not intended to be legal or professional advice, and should not be relied upon as such.
By watching this video, you acknowledge that you understand and agree to these terms. If you disagree with these terms, do not watch this video.
Counter-RAPTOR: Safeguarding tor against active routing attacks:
arxiv.org/pdf/1704.00843
Credit: /u/Yugong on Dread
Also see:
Y. Sun, A. Edmundson, L. Vanbever, O. Li, J. Rexford, M. Chiang, and
P. Mittal, “Raptor: routing attacks on privacy in Tor,” in 24th USENIX
Security Symposium (USENIX Security 15), 2015, pp. 271–286.
en.wikipedia.org/wiki/OVHcloud
w3techs.com/technologies/details/dc-ovhsasSo here's the deal: Tor's broken at the infrastructure level, and it's not because of some fancy NSA exploit or browser vulnerability. Princeton researchers mathematically proved that BGP routing attacks can unmask millions of users, and they're calling it RAPTOR (Routing Attacks on Privacy in Tor).
The attack is stupidly simple: BGP, the internet's routing protocol from the 1980s, has zero authentication. Anyone can announce they own any IP address, and other networks just... believe them. When you connect to what you think is a Tor guard relay in Germany, an attacker can redirect your traffic to their servers first, see your real IP, then forward it to the actual relay. Your anonymity dies before you even enter the Tor network.
The worst part? Major hosting providers like OVH (resilience score: 0.408) and Hetzner are incredibly vulnerable. When someone attacks their routing, 60% of users get exposed. And this isn't theoretical - real attacks happened in 2023 (AWS, 17 relays compromised) and 2024 (Hetzner, 45% of users exposed).
Princeton gave Tor the solution - Counter-RAPTOR - with working code nearly a decade ago. It includes resilience-based relay selection and real-time BGP monitoring. But here we are in 2025, and Tor still uses bandwidth-weighted selection that guides users straight to vulnerable relays.
State-sponsored attacks are up 300% according to Cloudflare. Russian ISPs hijacked 62 relays to unmask activists. The threat is real, active, and getting worse.
Full research paper linked in pinned comment. Time to demand Tor actually implements these fixes.
☆-----☆-----☆-----☆-----☆ CHAPTERS ☆-----☆-----☆-----☆-----☆
00:00 Tor is Broken at Infrastructure Level
00:36 What is BGP and Why It Matters
01:03 BGP's Fatal Security Flaw from the 1980s
01:34 How RAPTOR Attack Destroys Your Anonymity
02:18 Multiple BGP Attack Methods Explained
03:06 Princeton Researchers Measure Every Tor Relay
03:41 60% of OVH Users Exposed During Attacks
04:30 Hosting Companies Are Sitting Ducks
05:25 Why Some Networks Have Terrible Resilience
06:53 Internet Hierarchy Makes Tor Vulnerable
07:51 High Bandwidth Relays = High Risk
08:21 Real BGP Attacks Compromising Tor Relays
09:09 2023-2024 Attacks on AWS and Hetzner
09:55 State-Sponsored Attacks Up 300%
10:46 Russian ISP Hijacks 62 Relays
11:11 Counter-RAPTOR Defense System
12:09 New Guard Relay Selection Algorithm
13:29 Real-Time BGP Monitoring Solution
15:15 Detection Methods That Actually Work
16:11 9 Years Later - Tor Still Hasn't Fixed This
17:05 RPKI Can't Save You
18:51 BGP Attacks Bypass All Tor Security
19:37 You Can't Detect These Attacks
20:32 Individual Users Are Defenseless
21:22 The Math is Brutal - Millions Exposed
22:23 Why Tor Must Act Now
#tor #torproject #anonymity #cybersecurity #opsec
☆-----☆-----☆-----☆-----☆ SOCIAL MEDIA ☆-----☆-----☆-----☆-----☆
🎙️ Podcast: rss.com/podcasts/darknet
🌐 Official Website: doingfedtime.com
🌐 Official Website Mirror: sambent.com
📘 Facebook: facebook.com/TheOfficialSamBent
🐦 Twitter/X: twitter.com/DoingFedTime
💼 LinkedIn: linkedin.com/in/sam-bent
📧 Email: contact@sambent.com
📱 TikTok: facebook.com/TheOfficialSamBent
📚 Amazon Author Page: amazon.com/stores/Sam-Bent/author/B0BHX5V81S
🌐 Dread (Onion Link): http://dreadytofatroptsdj6io7l3xptbet6onoyno2yv7jicoxknyazubrad.onion/d/doingfedtime
🌐 Pitch (Onion Link): http://pitchprash4aqilfr7sbmuwve3pnkpylqwxjbj2q5o4szcfeea6d27yd.onion/@doingfedtime
🐙 GitHub: github.com/DoingFedTime
👾 Reddit (User Account): reddit.com/user/reservesteel9
📽️ Rumble: rumble.com/c/SamBent
🛡️ Breach Forums (Onion Link): http://breached26tezcofqla4adzyn22notfqwcac7gpbrleg4usehljwkgqd.onion/User-SamBent
📸 Instagram: instagram.com/sambentoffical
📌 Pinterest: pinterest.com/DoingFedTime
☆-----☆-----☆-----☆-----☆ LEGAL STUFF☆-----☆-----☆-----☆-----☆
The information provided in this video is intended for educational purposes only. It is not intended to be legal or professional advice, and should not be relied upon as such.
By watching this video, you acknowledge that you understand and agree to these terms. If you disagree with these terms, do not watch this video.
![The Graphene Phone by Motorola [GrapheneOS + Motorola Partnership]](https://i.ytimg.com/vi/Y5GrbhB2HHQ/mqdefault.jpg "The Graphene Phone by Motorola [GrapheneOS + Motorola Partnership]
Motorola just announced a long-term partnership with the GrapheneOS Foundation at Mobile World Congress 2026 in Barcelona to build the first non-Pixel smartphone running GrapheneOS out of the box. For years GrapheneOS was locked to Google Pixel hardware because no other manufacturer met their strict security requirements including hardware root of trust, verified boot with user-set keys, and hardware-backed brute force protection.
Motorola is now building a purpose-engineered device with a Snapdragon 8 Elite chip and custom hardware components designed specifically for GrapheneOSs hardened kernel and sandboxing features. This video covers the full story behind the partnership including GrapheneOS hinting at an OEM partner since October 2025, the Reddit leak of internal Motorola slides in February 2026, and the official announcement at MWC.
The video also covers why this matters now more than ever as Samsung strips recovery tools and bootloader access from Galaxy phones, Apple builds identity verification gates into iOS, and French law enforcement compares GrapheneOS to dismantled criminal communication networks like EncroChat and SkyECC. GrapheneOS pulled 15 servers out of France after the Paris prosecutors office threatened prosecution of privacy software developers.
Motorola also announced Private Image Data, a metadata stripping feature for photos, and Moto Analytics for enterprise fleet management under Lenovos ThinkShield ecosystem. The GrapheneOS Foundation is a Canadian nonprofit funded by donations with roughly 400,000 active devices worldwide.
☆ ☆ ☆ ☆ ☆ CHAPTERS ☆ ☆ ☆ ☆ ☆
00:00 GrapheneOS Just Broke Free From Google
00:39 The Mystery OEM Announcement
02:05 The Reddit Leak and Confirmation
03:16 Motorola Makes It Official at MWC
04:15 One Is None, Two Is One
05:11 What Is GrapheneOS?
06:18 400,000 Devices, All on Google Pixel
07:49 The Hardware Security Requirements
08:57 Motorola Building a Phone For GrapheneOS
10:09 Private Image Data and Moto Analytics
12:42 Meanwhile, Samsung Is Doing the Opposite
14:15 The Galaxy S22 Bricking Lawsuit
15:18 Apples Identity Collection in iOS
16:28 What Happened in France
18:27 France Threatens to Prosecute Developers
19:10 EncroChat and SkyECC Comparison
21:22 GrapheneOS Pulls Servers Out of France
24:02 Frances Bigger Agenda
25:53 The Scattered Spider Incident
27:25 Where GrapheneOS Stands Now
30:02 A Second Hardware Option For the First Time
☆ ☆ ☆ ☆ ☆ SOCIAL MEDIA ☆ ☆ ☆ ☆ ☆
🎙️ Podcast: https://rss.com/podcasts/darknet/
🌐 Official Website: https://www.doingfedtime.com
🌐 Official Website Mirror: https://www.sambent.com
📘 Facebook: https://www.facebook.com/TheOfficialSamBent/
🐦 Twitter/X: https://twitter.com/DoingFedTime
💼 LinkedIn: https://www.linkedin.com/in/sam-bent/
📧 Email: contact@sambent.com
📱 TikTok: https://www.facebook.com/TheOfficialSamBent/
📚 Amazon Author Page: https://www.amazon.com/stores/Sam-Bent/author/B0BHX5V81S
🌐 Dread (Onion Link): http://dreadytofatroptsdj6io7l3xptbet6onoyno2yv7jicoxknyazubrad.onion/d/doingfedtime
🌐 Pitch (Onion Link): http://pitchprash4aqilfr7sbmuwve3pnkpylqwxjbj2q5o4szcfeea6d27yd.onion/@doingfedtime
🐙 GitHub: https://github.com/DoingFedTime
👾 Reddit (User Account): https://www.reddit.com/user/reservesteel9/
📽️ Rumble: https://rumble.com/c/SamBent
🛡️ Breach Forums (Onion Link): http://breached26tezcofqla4adzyn22notfqwcac7gpbrleg4usehljwkgqd.onion/User-SamBent
📸 Instagram: https://www.instagram.com/sambentoffical/
📌 Pinterest: https://www.pinterest.com/DoingFedTime/
☆ ☆ ☆ ☆ ☆ LEGAL STUFF☆ ☆ ☆ ☆ ☆
The information provided in this video is intended for educational purposes only. It is not intended to be legal or professional advice, and should not be relied upon as such.
By watching this video, you acknowledge that you understand and agree to these terms. If you disagree with these terms, do not watch this video.")
