T-Mobile undeterred as telecom sector reels from attack campaign


T-Mobile has an infamously poor reputation in cybersecurity due to a pattern of repeated security lapses. The wireless network operator publicly acknowledged eight data breaches between 2018 and early 2023.

One of those attacks, a massive data breach in 2021 that exposed personal data on more than 76 million people and resulted in a $500 million class-action settlement, was widely regarded as the largest carrier breach on record. 

That record was challenged in the late spring and early summer when the threat group Salt Typhoon, sponsored by China’s government, infiltrated at least eight U.S. telecom companies. The revelations about the campaign, which came to light this week, resulted in the theft of a large amount of records, including metadata and some private communications, as part of a widespread and ongoing espionage campaign.

T-Mobile said it successfully stopped an attacker with striking similarities to Salt Typhoon’s known tactics from maneuvering deeper into its network, preventing the theft of sensitive customer data. In conversation with Cybersecurity Dive on Tuesday, T-Mobile CSO Jeff Simon credited the deterrence to, among other things, the network operator’s efforts to revamp its internal cybersecurity. 

Simon spoke with Cybersecurity Dive as details emerged about the broad and unprecedented damages caused by Salt Typhoon’s global campaign.

Editor’s note: This interview has been edited for clarity and brevity.

CYBERSECURITY DIVE: Can you walk me through what happened here? In your blog post last week, you said the threat actor attempted to use their compromise of a wireline provider’s network to access T-Mobile’s systems. Is that what allowed the threat actor to access some of T-Mobile’s routers or was this two separate access vectors?

JEFF SIMON: Let me start a little bit further back in time, just so you get the complete timeline. We’ve obviously been tracking Salt Typhoon for some time, really since the summer of this year we started to get intelligence. It was one of the main threat actors on our radar. We started hunting for the tactics, techniques and procedures that they’re known to be using on our infrastructure.

And frankly, we saw nothing. It was almost surprising how little we were able to find of Salt Typhoon on T-Mobile infrastructure. We did not see evidence of them at all.

Then more recently, while just continuing our normal monitoring processes across our infrastructure, we detected suspicious activity on some of our routers that you’re referencing. That suspicious activity, to this day, we don’t know who was behind it, whether it was Salt Typhoon or another actor, but there were definitely some indications in the behavior we saw. …  We don’t have any specific intelligence from our government or private sector partners saying definitely, this is Salt Typhoon.

We detected that activity and we were able to do it fairly quickly from the time that they started the activity. It was a single-digit number of days from them being active, trying to probe our infrastructure and do discovery type activity to us identifying it and being able to close the door.

We were able to track it back pretty quickly to that other telecom provider, the wireline provider, that was the source of the traffic into our network that was essentially targeting our edge routing infrastructure.

With the T-Mobile routers that were accessed, it sounded like more discovery there — the threat actor was trying to learn more about the network and perhaps leapfrog from there. Is that how they got access to T-Mobile routers, from this wireline provider’s network access to T-Mobile?

Mostly, yes is the answer to your question. I just might word it a little bit differently. The other provider doesn’t necessarily have access to T-Mobile. I would think of it more as a peering relationship between the two telecom operators, where we leverage their backhaul network for transport. That’s the relationship.

It’s not that the wireline provider had specific provisioned access into our environment. When you say access it sounds like there’s other human users at that other telco that we would expect to be logging into our systems. Not the case. This was a communications-type setup. We use them for backhaul-type communications.

Can you explain how they got access to T-Mobile’s routers? Did they exploit a vulnerability in T-Mobile’s routers? I’m still kind of hung up on that piece. 



Source link