Ericsson US Hit by Data Breach After Third-Party Hack Exposes Employee and Customer Information

Ericsson's U.S. division confirmed a data breach exposing employee and customer data, including Social Security numbers, after a third-party vendor was hacked. The incident highlights persistent supply chain security failures across the telecom sector.
Ericsson US Hit by Data Breach After Third-Party Hack Exposes Employee and Customer Information
Written by Dave Ritchie

Ericsson’s U.S. arm has confirmed a data breach affecting both employees and customers, triggered by a hack on one of its third-party partners. The telecom giant disclosed the incident in breach notification letters sent to affected individuals, revealing that sensitive personal data was compromised when attackers infiltrated a vendor’s systems.

Not great timing for a company that sits at the backbone of global telecommunications infrastructure.

What Happened and What Was Exposed

According to TechRadar, Ericsson US discovered that an unauthorized party gained access to data held by one of its third-party service providers. The breach notification, filed with state authorities, confirmed that the compromised information includes names, Social Security numbers, and other personally identifiable information belonging to both employees and customers.

The specifics of which third-party vendor was breached haven’t been publicly named. That’s a pattern we’ve seen repeatedly in supply chain incidents — the primary brand takes the reputational hit while the actual point of failure stays obscured. Ericsson has stated it’s working with the vendor and law enforcement to investigate the full scope of the compromise.

Details on exactly how many individuals were affected remain thin. Ericsson hasn’t released a precise headcount, though the company is offering complimentary credit monitoring and identity protection services to those impacted — a standard response that signals the exposure is significant enough to warrant real concern about identity theft and fraud.

So what do we actually know? An external partner got popped. Data flowed out. And Ericsson is now doing damage control.

The breach appears to have been discovered in early 2025, with notifications going out in recent weeks. The timeline between discovery and disclosure matters here — under evolving state-level breach notification laws across the U.S., companies face tightening windows to inform affected parties. Ericsson appears to be complying, though the gap between when the third party was initially compromised and when Ericsson learned about it remains unclear.

Third-Party Risk Isn’t Theoretical Anymore

This incident lands squarely in the growing pile of evidence that third-party and supply chain attacks are now among the most persistent threats facing large enterprises. It doesn’t matter how much you spend on internal security if your vendors are running leaky infrastructure.

The pattern is painfully familiar. MOVEit. SolarWinds. Okta’s vendor breach in 2023. And now Ericsson joins the list of major corporations burned by the security posture of their partners. According to a 2024 report from SecurityScorecard, nearly 29% of all breaches involved a third-party attack vector — a figure that’s been climbing year over year.

For telecom companies specifically, the stakes are amplified. Ericsson provides critical network equipment and services to carriers worldwide. Any breach that touches employee credentials, internal systems access, or customer data could have downstream implications for the operators relying on Ericsson’s technology. The company serves major U.S. carriers including T-Mobile and AT&T, though there’s no indication those networks were directly affected by this particular incident.

But the concern isn’t hypothetical. Telecom infrastructure has been under sustained attack. The Salt Typhoon campaign, attributed to Chinese state-sponsored hackers, targeted multiple U.S. carriers in 2024 and exposed deep vulnerabilities in how telecom supply chains are secured. While there’s no public evidence connecting Ericsson’s breach to any nation-state activity, the broader context makes every telecom-adjacent incident worth scrutinizing.

Ericsson, for its part, told affected individuals that it “takes the security of personal information seriously” — the kind of boilerplate language that appears in virtually every breach notification letter ever written. More meaningful will be what structural changes, if any, the company imposes on its vendor management practices going forward.

Here’s what industry professionals should be watching. First, whether Ericsson discloses the identity of the compromised third party. Transparency here would help other organizations assess their own exposure if they share the same vendor. Second, whether regulatory bodies — particularly the FCC, which has been increasingly aggressive on telecom security — take any action. And third, whether this breach is connected to any broader campaign targeting telecom supply chains.

The incident also raises questions about contractual security obligations between enterprises and their vendors. Many large organizations require SOC 2 compliance, penetration testing, and other security assurances from third parties. But compliance checkboxes don’t stop breaches. Real security requires continuous monitoring, access controls scoped to the minimum necessary data, and rapid detection capabilities that most vendor relationships simply don’t include.

Short version: trust but verify isn’t working when the verification is a once-a-year audit.

What Comes Next

Ericsson US will likely face scrutiny from multiple angles — regulatory, legal, and reputational. Class action attorneys are almost certainly already evaluating the breach for potential litigation, particularly given the Social Security number exposure. Lawsuits following breaches of this nature have become nearly automatic in the U.S.

For security leaders at other organizations, this is another data point reinforcing what many already know: your attack surface extends well beyond your own walls. Vendor risk management programs need teeth. That means contractual provisions with real consequences for security failures, continuous third-party risk scoring, and incident response plans that account for breaches originating outside your direct control.

As someone who’s been watching these incidents stack up for years, I’ll say this plainly — the industry’s collective approach to third-party security is still woefully inadequate relative to the threat. We keep seeing the same movie. Different cast, same ending.

Ericsson will recover. The brand is too entrenched in global telecom infrastructure for this to be existential. But for the employees and customers whose Social Security numbers are now floating around in places they shouldn’t be, the consequences are personal and lasting. Credit monitoring is a band-aid. It doesn’t undo the exposure.

The real question isn’t whether another major enterprise will suffer a similar third-party breach. It’s how many will happen before the industry fundamentally rethinks how vendor relationships are structured and secured.

Subscribe for Updates

CybersecurityUpdate Newsletter

The CybersecurityUpdate Email Newsletter is your essential source for the latest in cybersecurity news, threat intelligence, and risk management strategies. Perfect for IT security professionals and business leaders focused on protecting their organizations.

By signing up for our newsletter you agree to receive content related to ientry.com / webpronews.com and our affiliate partners. For additional information refer to our terms of service.

Notice an error?

Help us improve our content by reporting any issues you find.

Get the WebProNews newsletter delivered to your inbox

Get the free daily newsletter read by decision makers

Subscribe
Advertise with Us

Ready to get started?

Get our media kit

Advertise with Us