News for hackers. Stuff that matters.

Tell HN: T-Mobile breach- double fuck up

I work for Metro by T-Mobile. Our store computers run thin clients operated by T-Mobile and the internal account management software EDGE fucked up the internal memo disclosing the recent data breach.

Upon accessing a cx account today I see the following memo: ———— High Priority Memo | Created by 11111 on 20-Jan-2023) Customer received the following SMS notification: IMPORTANT: Some of your account information was obtained without authorization. Passwords, SSN, payment methods were NOT affected. Your name, # of lines, contact details and other account information may have been. Learn more: metro-tmo.co/CustInfo. See https://www.metrocare-agent.com/announcements/<Redacted>… ————

First off, “metro-tmo.co” is a spam domain that isn’t owned or operated by T-Mobile. Not only could the person who wrote this memo fail to write complete English sentences, but they fail to link the correct domain to the announcement regarding their own data breach. as of this current moment, their internal account memo system continues to link this incorrect spam link. and to make matters worse, they even sent this spam domain to potentially millions of customers phones via sms.

( 21 comments | on HN )
Re:Tell HN: T-Mobile breach- double fuck up by mtmail on Friday January 20, 2023 @06:44PM (#34461856)
So the customer got SMS spam from a third-party and there was no T-Mobile breach? The fuck up is the spammer makes spelling mistakes?
Re:Tell HN: T-Mobile breach- double fuck up by TmoSecuritySux on Friday January 20, 2023 @06:49PM (#34461903)
No, whoever is in charge of writing High Priority Memos on cx accounts at Metro by T-Mobile / T-Mobile Corporate made a typo in the Memo itself which links to a spam domain. The memo also claims this exact message was also sent to customers phones.

Typo URL in internal account memos + texts sent by the company to subscribers : http://metro-tmo.co/CustInfo

Actual legitimate URL they meant to put : http://metro-tmo.com/CustInfo

Re:Tell HN: T-Mobile breach- double fuck up by winternett on Saturday January 21, 2023 @11:43PM (#34474365)
If only one of these data breaches led to account balances getting wiped, THEN we'd see big changes. :/
Re:Tell HN: T-Mobile breach- double fuck up by readonthegoapp on Friday January 20, 2023 @08:00PM (#34462566)
didn't Metro shut down?
Re:Tell HN: T-Mobile breach- double fuck up by stonogo on Friday January 20, 2023 @08:25PM (#34462753)
Who would OP be working for in this scenario?
Re:Tell HN: T-Mobile breach- double fuck up by mr3martinis on Friday January 20, 2023 @10:16PM (#34463511)
T-Mo, under the metro brand.
[dead]
Re:Tell HN: T-Mobile breach- double fuck up by simfree on Saturday January 21, 2023 @12:13AM (#34464087)
Franchisees shouldn't have their Franchisor making hiring and firing decisions, that just seems legally dubious given the franchisee is supposed to be a separate (but affiliated) company.
Re:Tell HN: T-Mobile breach- double fuck up by zinekeller on Friday January 20, 2023 @09:08PM (#34463083)
The original MetroPCS did get merged into T-Mobile and is now a value brand.
Re:Tell HN: T-Mobile breach- double fuck up by azgolfer05 on Friday January 20, 2023 @10:54PM (#34463710)
I received this text just now, is this a scam??
Re:Tell HN: T-Mobile breach- double fuck up by llZielll on Friday January 20, 2023 @11:19PM (#34463850)
I did so as well, so I’m wondering if it’s a scam.
Re:Tell HN: T-Mobile breach- double fuck up by leowrlds on Friday January 20, 2023 @11:17PM (#34463835)
i think so, otherwise some shit would've happened.
[dead]
Re:Tell HN: T-Mobile breach- double fuck up by propogandist on Saturday January 21, 2023 @03:22AM (#34464832)
the website does not resolve for me, but if it has adspam, serving targeted text add (contextual) can be a big money maker for a clever marketer
Re:Tell HN: T-Mobile breach- double fuck up by anonomousename on Saturday January 21, 2023 @08:45PM (#34473208)
It could also be changed to a copy of the official T-Mobile site, resulting in widespread phishing.
Re:Tell HN: T-Mobile breach- double fuck up by voakbasda on Saturday January 21, 2023 @01:45PM (#34468976)
An “accident” that permits them to seize someone’s assets does not sound like an accident to me.
Re:Tell HN: T-Mobile breach- double fuck up by zinekeller on Friday January 20, 2023 @11:53PM (#34464015)
Nope, T-Mobile did get hacked: https://www.t-mobile.com/brand/customer-information-2023, https://www.cnn.com/2023/01/19/tech/tmobile-hack/index.html

However, the link was NOT the correct one, it's like that time when Equifax got hacked and asked users to go to https://securityequifax2017.com/ (which looked like this: https://web.archive.org/web/20170908172914/https://securitye...) instead of the genuine https://equifaxsecurity2017.com/.

[dead]
Re:Tell HN: T-Mobile breach- double fuck up by cakefacebrit on Monday January 23, 2023 @08:54PM (#34498051)
I just received a text with the exact message saying to click the “ http://metro-tmo.com/CustInfo” website. I reported it as junk text on my phone but itd be nice to see these people get shut down.
Re:Tell HN: T-Mobile breach- double fuck up by seytonic on Saturday January 21, 2023 @05:04AM (#34465288)
Can you post a screenshot of the text?
Re:Tell HN: T-Mobile breach- double fuck up by badrabbit on Friday January 20, 2023 @11:02PM (#34463755)
Just fyi: they usually (but not always) do that incomplete sentence and bad spelling/grammar on purpose, so as to lure less "smart" people into pwnage (myself included lmao)
Re:Tell HN: T-Mobile breach- double fuck up by function_seven on Friday January 20, 2023 @11:55PM (#34464021)
Except in this case the message was really written by T-Mobile. They just messed up the domain.
Re:Tell HN: T-Mobile breach- double fuck up by cakefacebrit on Monday January 23, 2023 @08:56PM (#34498071)
Just received a text not even 5 mins ago. The exact message as above. I’m going to report it everywhere I can in hopes to help maybe we can all get these people shut down!
Re:Tell HN: T-Mobile breach- double fuck up by SantaFeSlayer on Wednesday January 25, 2023 @05:12AM (#34516571)
I just received the same text at 20:47 last night, 20230124, but it was ".com", not ".co", so I guess it has been fixed.