Commentary

George Hulme
 

Hackers Claim To Have Pwned US T-Mobile. As In: Everything.

It's not the kind of forum post an executive would like to see created about their company. It's not a leaked rumor about an upcoming product or service, or even a ranting upset customer. Nope. It's a group claiming to have controlled portions of your IT network for a long time. And they published what looks to be proof of the breach. T-Mobile is investigating.

It's not the kind of forum post an executive would like to see created about their company. It's not a leaked rumor about an upcoming product or service, or even a ranting upset customer. Nope. It's a group claiming to have controlled portions of your IT network for a long time.

And they published what looks to be proof of the breach. T-Mobile is investigating.This post hit the Full Disclosure security mailing list over the weekend:


More Security Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

Hello world,

The U.S. T-Mobile network predominately uses the GSM/GPRS/EDGE 1900 MHz frequency-band, making it the largest 1900 MHz network in the United States. Service is available in 98 of the 100 largest markets and 268 million potential customers.

Like Checkpoint Tmobile has been owned for some time. We have everything, their databases, confidental documents, scripts and programs from their servers, financial documents up to 2009.

We already contacted with their competitors and they didn't show interest in buying their data -probably because the mails got to the wrong people- so now we are offering them for the highest bidder.

Please only serious offers, don't waste our time.

If true, I wonder how much customer data has been compromised? I've a feeling that we'll find out soon enough, should the culprits not get what they're asking.

If they did get financial records, that could very well be a regulatory problem for T-Mobile, specifically with Sarbanes-Oxley compliance. But that may not be the biggest concern T-Mobile has at the moment.

To back up their claims, they published a list of servers that are purported to have been breached, including applicationIDs and IP addresses. The list includes a number of billing and collection systems.

Right now, it doesn't look good. But there's a chance the entire post is a hoax.

T-Mobile has issued a statement saying that it is investigating, and that the company would notify customers if there were any evidence that customer information was compromised.

This incident begs the question: is your company ready for such an incident? Well, as ready as one could be? How would your legal, HR, and incident response teams get engaged should this happen? What's the plan? How would you handle the preliminary customer calls and questions? Who in law enforcement would you contact?

The time to answer those questions is before something like this happens. Not cobbling together the response as it is happening.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links