Your Privacy is at Risk
h3h3ProductionsCited 5× on HN, 2016–2022
commentary · general · 2016–2022 on HN
h3h3Productions describes how a hacker took over their phone number by getting a SIM card from T-Mobile, and gives security advice such as using a hardware key and an authenticator app.
HN cites it as a well-known example of SIM-swap social engineering that defeated even a carrier PIN, in discussions of SMS-based two-factor authentication.
Up next
11 mo on HNBehind the Scenes of iOS Security
Black Hat
9 HN recommender · 2016–2026
11 mo on HNWhy Electronic Voting Is Still A Bad Idea
Tom Scott
11 HN recommender · 2020–2026
10 mo on HNUSENIX Security '18-Q: Why Do Keynote Speakers Keep Suggesting That Improving Security Is Possible?
USENIX
10 HN recommender · 2018–2026
10 mo on HNDefcon 18 Changing threats to privacy Moxie Marlinspike Part
killab66661
6 HN recommender · 2012–2019
9 mo on HN28c3: The Science of Insecurity
28c3
9 HN recommender · 2012–2024
8 mo on HNDEF CON 25 - John Sotos - Genetic Diseases to Guide Digital Hacks of the Human Genome
DEFCONConference
11 HN recommender · 2017–2023
7 mo on HNElevator Hacking: From the Pit to the Penthouse
DeviantOllam
9 HN recommender · 2014–2026
7 mo on HNCompiling C to printable x86, to make an executable research paper
suckerpinch
8 HN recommender · 2018–2023
7 mo on HNBreak Me00 The MoVfuscator Turning mov into a soul crushing RE nightmare Christopher Domas
Adrian Crenshaw
6 HN recommender · 2017–2026
7 mo on HNBlackHat USA 2011: SSL And The Future Of Authenticity
Christiaan008
9 HN recommender · 2011–2017
7 mo on HN27C3: Adventures in analyzing Stuxnet (Bruce Dang from Microsoft)
basti0007
8 HN recommender · 2011–2024
7 mo on HNFrank Abagnale | Catch Me If You Can | Talks at Google
Talks at Google
8 HN recommender · 2018–2023
5 comments from Hacker News
But, to add, sim swap attacks are a known issue and anything of value becomes a target. The main issue is that retail employees in 'authorized reseller' locations are allowed to make changes to accounts with the PIN of the account holder, but that is often easy to guess or is easy to figure out by anyone that does enough digging into someone's life. link ▶ this video (tldr he got cold called to set up 'extra security', gave the attacker a PIN number, and the attacker used that to impersonate them within a T-Mobile store and swap the sim card from the phone into a new phone, thus receiving SMS 2fa codes for their accounts).
Since everyone is wondering why, and since I happened to stumble across a reason during my time as a pentester, here you go: Spearphishing is still one of the most common ways of breaching a corporate network. If I target you, you will likely fall for one of my attempts. If you are a company rather than a person, my odds go way up, because I have N chances to trick someone rather than 1 (where N is roughly the number of people at the company with email access). This is one of those things that everyone says "Ha, I'm smart. I'd notice. You can't trick me." And maybe you are. But you're also distracted. And that's my greatest advantage against you. All I need is to sneak in an unexpected Github prompt that looks completely authentic, and now I have your Github password. Wanna bet you don't have 2FA turned on, even though you know you really ought to? And even if you do, it's getting easier to social engineer your way past AT&T's lovely customer support: ▶ this video Ok, what's the point? This: Every character in the URL bar unrelated to the apex name is a deadly distraction. Right now, how do you know you're actually on HN instead of some knockoff? "ycombinator.com". How many characters do you have to read unrelated to that? " link . /item?id=17927972" The most vital part of a URL for vetting identity is also, usually, the hardest to see. Now, I don't know whether google made this change in order to assist with this. But it's one possible justification, and a step in a good direct
Either some sort of ss7 exploit [0] or the attackers socially engineered the cell service provider [1]. This happened to some big YouTubers in the past [2]. [0] link [1] link [2] ▶ this video
Using social engineering to bypass this is a big enough issue that even the FTC has a blog post about it [1]. It's happened to popular Youtube producer H3H3 (even with a pin) [2]. Fusion did a thing about it at DefCon this year as well, demonstrating exactly how easy it is. The whole video [3] is worth watching, but I'll like to the relevant bit. [1] link [2] ▶ this video [3] link
One of the biggest weaknesses of SMS 2FA that I didn't see the article cover is when an attacker can socially engineer their way into your account with your cell service provider. I'm thinking of a high-profile example when an attacker tried to take over h3h3's YouTube account by requesting his SIM card from T-mobile by pretending to be a T-mobile employee: ▶ this video