Hackers Claim To Hit T-Mobile Hard
dasButcher writes "Hackers are
claiming to own T-Mobile USA's servers and to have access to the cellular phone carrier's operations, finance and subscriber data." (Here's the seclists.org post of the claimed breach.)
Why isn't this stuff encrypted?
My guesses: legacy, convenience, lack of care, lack of duty.
Now, I'm not going to cheer crackers breaking into a private corporation's data services. The breech has tremendous privacy implications, and a lot of these fall squarely on the head of the consumer. However, I'd like to see a silver lining to this by seeing the data employed to put paid to the idea that SMSes have to cost so much. Time after time, the data has shown that SMSes *should* be giant cash cows for these monopolistic entities, but lacking internal financial data it has always been difficult to make an issue out of this at Congress. Of course the cell companies have every interest to keep this data private, but maybe in this case T-Mobile won't have the choice.
www.eissq.com/BandP.html Ball and Plate System. Amuse your friends. Crush your enemies.
Maybe the hackers can offer better service?
Have you fscked your local propeller head today?
From the "hackers" 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. Seriously, how do they think T-Mobile's competitors are going to legally pay and use such information?
Run and catch, run and catch, the lamb is caught in the blackberry patch.
My guess is the conversations go like this:
Front-line Manager: We need to encrypt our dataz.
Middle Manager: How much will this cost?
Front-line Manager: (insert any number)
Middle Manager: No.
Chicken fried butter sticks? Do
What stuff? You mean the raw database? Theoretically, there are various layers of security here: firewalls to the outside, authentication to particular views on the inside where only data you Need To Know is available to you, and proper firewalls on each database server to limit access to the database port(s) and probably ssh.
If the hackers could get through all of this, they must be *very* good. More likely, however, is that they have someone on the inside which bypasses all of this. And it would bypass the encryption on the data anyway since s/he obviously already had Need To Know to get at the data anyway, and thus would have the decryption key. There isn't much a corporation can do against an insider that needs that info just to perform the job they were hired to perform.
If the hackers could get through all of this, they must be *very* good.
Practical computer security typically has more to do with those responsible for maintaining the security getting sloppy or being un-knowledgeable than with some extreme degree of skill or knowledge on the part of those penetrating the system.
Interesting. I only saw HP-UX, SunOS, AIX and Linux. No Windows used in T-Mobile, or they could not be cracked? Or T-Mobile just don't put anything important on Windows servers?
And the best thing they can think of doing with it all is to offer it to T-Mobiles competitors? Seriously? I can think of tons of ways to profit off of all that information.
However not one of those ways involves attempting to sell the information to companies that are legally required to report it. Or when that fails, announcing it to the public and getting every police agency in the world on my trail.
What is there in this data that would cause an AT&T executive to risk losing his job and perhaps going to prison?
Warning: this article may contain humor, sarcasm, parody, and perhaps even irony. Read at your own risk.
I'll wait for some validation. Cuz, you know;
prodsrv1|192.168.1.200|root@cia.gov sekret files|for realz|RHEL4
isn't especially convincing.
Even if it's a real list, it could be something as simple as a pilfered company document off a laptop, a script-kiddie wannabe hacker employee showing off to his friends on IRC, or any of a hundred scenarios.
Do I doubt it's difficult to own a bunch of HP-UX boxes? Nah.
Have I learned to not spastically freak out every time some random people claim they hacked something? Yah.
Trouble is, T-Mobile wouldn't exactly be forthcoming with any confirmations.
At the end of the day, you just have to plan around being hacked. You have to ensure your payment method associated with external services can handle being owned. You have to be ready for people getting your SSN and private info, since it's moronically being used for frivolous purposes everywhere.
Which is not to say you shouldn't do your best to keep your data protected and secure - I just try to plan around any data I give out to various companies being owned.
There is no way to know and it's a moot point. Presumably they attacked the systems while they were live, so the information would have been decrypted anyway in order for the database system to access it. There is also the inside job scenario that someone outlined above.
Encryption doesn't really matter in this type of break in, it's more for "oh shit I left my hard drive and laptop in an airport" type of scenarios.
As a purveyor of security software (to a different industry), I've seen countless times that almost always the conversation really does go along an only slightly-less direct route:
A. We need to secure X
B. How much does it cost?
A. (insert any dollars)
B. Do we have to spend that?
A. We do if we want to be reasonably secure.
B (thinks... We're smart people; we can install a few firewalls; that'll keep the Bad Guys out)
B. (Having insight) But this is like insurance, right? If we keep people out of the network, we don't get anything for those dollars.
A. Well, sort of, I suppose so.
B. Right, we'll save those dollars.
---
You have to assume that Bad Guys CAN get into your network if they really want to. Because the truth is, whatever your in-house people have told you, they can. Of you doubt me, talk to people whose job is to break into networks. All the ones I've known will tell you that 100% of targeted commercial networks fall to a concerted attack.
When they do fall, security's job is to make sure, at a minimum:
1) the Bad Guys can't learn anything useful
2) the Bad Guys can't interfere with the service you're selling
3) there's a high probability that you'll detect the event and be able to track the Bad Guys
B's insight isn't a bad one at all... security *is* a kind of insurance. Which means that most of the time, if you have a well-designed system you really are "wasting" the dollars. But one day you or your successor will regret those "saved" dollars.
B's job really is to make a proper cost/benefit analysis. My experience is that that almost never happens. They either just "save" the dollars without thinking or, more often, either a) look to what their competition is doing or b) assume that the risk is so small ("we haven't been hacked so far") that it's not worth spending any money.
If I were an AT&T official and they contacted me? I'd absolutely be interested. I'd also be on the phone to internal corporate security and the FBI before I finished reading the email.
If this story is true, those are some mighty bold thieves. AT&T probably has more resources than anyone else on the planet for tracking down the originator of that communication. For that matter, AT&T are probably the ones the FBI contacts when they want to hunt down a bad guy, so you know there's a long relationship there, too.
Times may be tough, but various competing corporations often have informal and even friendly relationships with each other when it comes to Loss Prevention departments. They share info on thieves and threats, and despite outward animosity between two competing companies, their L.P. departments do tend to help each other out with situations like these. I know that's the case in retail, where organized crime investigations actually can have cooperation between companies like Walmart and Best Buy. There's definitely an "old boy's network" behind the scenes as these employees shift between companies and don't forget their old friends. It's a lot like the cop brotherhood (in part because many of the L.P. staffs are actually retired cops.) AT&T likely wants these guys caught almost as much as T-Mobile does.
John
What stuff? You mean the raw database? Theoretically, there are various layers of security here: firewalls to the outside, authentication to particular views on the inside where only data you Need To Know is available to you, and proper firewalls on each database server to limit access to the database port(s) and probably ssh.
It seems your theory is kind of flawed, because if their protection was indeed that good the thieves probably wouldn't have gotten the data they did.
I think the reality is they have a firewall, and probably overly simplistic authentication on the databases, and virtually nothing else. Consider an inept DBA running SQL Server 2005 who ties the SQL Server's SA account to the machine's administrator account. And add another inept system administrator who has a shared admin account across all the database servers, as well as some IIS servers and maybe some FTP servers as well. So the hacker worms his way to an admin account on ftp_serve_01.tmobile.com and ta-da! He's suddenly got admin rights to their data!
Never ascribe to ingenuity that which can be adequately explained by stupidity.
John
How hard is it to keep a Linux, AIX and SunOS servers patched with security updates, seriously. These boxes must of never been properly secured in the first place for that many operating systems to be compromised. I know it is a bit of security through obscurity but having multiple server OS usually offers you some protection but to have this many fail seems like they need to pay more $$$$ and get a competent sysadmin group. I would not be surprised if a majority of their day to day sysadmin work was outsourced. If you do not have someone that is there with the firewall logs in real time, at least one honeypot behind the firewall and tripwire setups that page everyone but god when your honeypot is disturbed you are not even trying. Hell, I have that at home.
An Education is the Font of All Liberty
Almost any risk can be covered one of two ways:
This is simply an application of Murphy's law. Any outcome which is not systematically excluded will occur eventually. You can either incur the overhead of building a system that excludes the negative outcomes or you can accept the risk that they will occur.
Of course, in practice you can't absolutely exclude negative outcomes, but as you say, you may be able to analyze them and break them down into manageable cases.
Oh this is hilarious. When T-mobile's stock tanks Monday morning, someone is going to have made a killing on short-selling the stock.
Follow the money. Who stands to gain a lot by a supposed breach of all of T-Mobile's systems? Is there some proof the system is really hacked? I doubt anyone on ATT or Verizon's payroll would be dumb enough to pull this. But there are lots of hedge fund traders looking for new 'angles' to make a buck, and after having destroyed the banking system, I suspect someone has gotten wise to what could be pulled off with a little hacking. (Or suggestions of hacking)
Well, unless you bought your phone at a store with cash, and buy refills the same way..
I guess I am the "not smart" T-Mobile user, as I bought my prepaid phone through their web site.. You seem to be imply that T-Mobile is somehow a flyby night company ... They are in fact 8th largest in the world.. Verizon is 14th., AT&T is 15th., Sprint doesn't make the top 20 and they have slightly more than half as many subscribers as AT&T... Of all these companies, why should I not have trust in T-Mobile ?
waiting for ad.doubleclick.net
I think we are entering an age where everyone knows the employee's loyality goes just as far as the permanence of their job, and no job is permanent anymore. So everyone is out for themselves, and if they see a chance to grab some kind of a big payoff they are going to take it. Or toss a wrench into the works just to see what happens.
Well, over the last 20 years or so, companies in general have made it abundantly clear that they feel little or no obligation to their workers. Their stockholders and CEOs, yes, but not their workers. I'm not saying they really ever did, but for perhaps 50 years there was a facade (pensions, long-term employment, etc.).
So it's entirely reasonable that workers return the favour.
"If you are, you better start thinking about where to go next. Their service is now wide open. Anything transferred through their network is now questionable."
I'm a T-Mobile customer. I use pretty much voice only, no data, I don't text, but I get texts. I have no friends, and largely call my immediate family. The rest of the time, the phone is simply to order takeout, or to pay a bill with a virtual credit card account number, or to call Comcast when their shitty service konks out again.
The only reason I keep the service is because they are GSM, their low rates compared to Verizon and AT&T, and damn good, friendly customer service. Their CR people try, and I mean really try, but what they have to work with is near worthless.
For awhile now, I've felt they've been owned or would be. If you've ever paid your bill online, and looked at how they handle data, such as the confirmed payment printable receipt, it's obviously they have bad coders--they put your data (i.e. name, address, telephone number, account number, amount paid, etc.) in the https header, which while technically secure/SSL'd, is stupid, since if they have any logging, it likely goes in unencrypted; it's just bad form.
When you have voicemails 2 weeks old saved that are suddenly deleted, and you call in to find out at least why, and they can't get a trace on the problem, they have an incompetent logging setup.
When their entire system bonks and deletes everything except the bare necessity in your account, including calling information, which happened to me in February, and again they can't pull up any sort of traceable logs or records to figure out what happened, they have security problems.
When they do several system "upgrades" over the past few years, and every upgrade has a correlating outage, voicemail loss, or some strange change in features that gets fixed a few days later, you know the people doing this are incompetent, overworked, or working with crap when they can't even perform a basic test or rollout of the new system first.
Any observant T-Mobile customer knows T-Mobile's underpinnings are really, really, really shitty. And that's aside from their crappy frequency which doesn't seem to penetrate most city buildings and has dropout points in coverage areas which are just weird. It feels as if they have some incompetent, ancient legacy boss who tries to do the right thing but doesn't.
I hate Verizon given they are the spawn of the hated landline baby bell company. I used to be with AT&T, but their rates just suck. I've been tempted to go to Sprint, but I've heard horrors a few years back about their nationwide coverage.
You might be asking why I stay with T-Mobile, aside from the fact their rates are cheap. I stay with T-Mobile since, despite all their problems, they've otherwise given me the fewest grief of any telephone provider I've ever had. Which is sort of a sad comment on the state of cellular providers in the US.
And the US export encryption laws, described at http://www.bis.doc.gov/encryption/default.htm. It would also interfere with the Patriot Act warrant and supervision free phone tapping, and whatever the NSA has put in lately to tap the major fiber optic backbones without warrant or any appeal to inappropriate monitoring available, as they've previously done to AT&T.
A warning does not hurt. Ignoring one might.
>Their service is now wide open.
Oh, please. The servers listed are a tiny fraction of Tmo's network. You think they provide billing and data services to 30,000,000+ customers with 511 systems?
Did you notice how many of those systems had their regions attached? Do all your systems in say Kansas, have the word Kansas in their /etc/ directory somewhere? This looks more like a "server deployment database dump" than an actual hacker's list of compromised systems.
Did you notice the variety of systems they claim to have compromised HPUX, Sun and AIX, and Linux, but not one single Windows server? What are the odds, even if they were all equally secure (cough). The enterprise still uses plenty of Windows software, and it's obvious when dealing with tmo Customer Care that their desktops are Windows. 20k systems in the hands of low-wage employees and not one of them on this list?
And what did you think the big companies do to keep your phone records safe? With the major carriers all having 20k+ customer care reps, did you expect "DOD Secret Level Clearance" was required to work there? Your phone records at any company are available for a price. ("pssst, no one cares who you're callling.").
>Their inability to keep hackers out equals no reason to be in business.
Maybe in BizarroLand. All the proof we have is a list of suspiciously Unix-centric systems that are likely on the T-Mobile network. Compromising a single DNS server in the DMZ might have given them access to some engineer's home directory where a .csv was sitting ready for a perl script to translate it to DNS entries as part of some routine maintenance task. And if they have a friendly customer care rep that will risk their job to provide 3 months worth of phone records for $100.... Well, that hasn't been news in 5 years.
I think your tinfoil hat needs another layer. Have you tried Copper foil for better Chi alignment?
nice!
We all joke, and to some extent say, "good job" to the hackers. We forget these guys are no different than the robbers and thugs you see on "cops" or the evening news, they are just more covert. No one cheers on the armed gunman, robbing a convenience store. It bothers me these guys aren't viewed in the same light.
If you could reason with religious people, there would be no religious people
No doubt that they are bad guys, but to say that they are 'no different' is taking it a little far. How many convenience store robberies have you heard of that have ended badly for the staff? There is a good chance that a convenience store robber is willing to deprive someone of their life to get what they want. A hacker is merely willing to deprive someone of property. They are more like the guy who breaks into the convenience store after hours, with the intent to run away if confronted.
The curious thing is that the typical slashdotter would have some appreciation for the skills required to pull off such a hack (assuming they didn't just find a backup tape full of passwords in the trash :) - we can more readily identify with the nerd in his basement with the world at his fingertips 'sticking it to the man' than we could with the armed robber desperate to get cash for his next drug hit. And we all hate cell phone companies. I don't know what's on the agenda for these guys though... presumably blackmail or extortion.
But when you are king and are rounding up all the hackers, remember to include the guys who are unlawfully downloading copyright material too :)
Maybe some of it is encrypted. But perhaps with some pilfered credentials a database or other internal system will happily respond to your queries and pass back the results as plaintext. After all, somebody somewhere has to be able to decrypt the customer/billing information or it's useless.
Encryption isn't the be-all and end-all of security. For example, using TrueCrypt on your laptop is a great idea to reduce your risk in case of theft, but when you've mounted an encrypted partition and someone is rooting your box over the network it's not going to help you.
I've worked in I.T. long enough to know that the vast majority of security products and services out there are little more than selling companies a "bill of goods". Sometimes, it's a great investment, simply as a CYA move. (As a systems administrator, you're a lot less likely to get fired because of a hack if you can show you tried your best to secure everything, using products X, Y and Z, right?)
But ultimately, you can go with the most highly regarded firewall product, the top-rated anti-spyware and anti-virus solutions, implement policies requiring employees change their passwords every 30 days, encrypt sensitive information, and the whole 9 yards. But one employee who has been given access is all it takes to make it all come tumbling down. (And I imagine the vast majority of the time, that's a key component of successful hacks anyway. Remember the AOL credit card leaks a while back? Total inside job.)
In most cases, you really don't have much of a guarantee that a given product truly gives you the security it claims either. How do you REALLY know that expensive firewall doesn't have some kind of back-door in it that's never been publicized? Maybe one of their developers stuck it in there secretly, knowing he'd made FAR more than his salary selling the password to a few key hackers in the underground later?
Unless a product offers to cover all your expenses to recover from a hack, if their product or service is hacked, it's pretty weak insurance.
They might have technical chops or they might just be taking advantage of a disgruntled employee or other low-tech hole; it's impossible to say so far. What's clear is that they obviously had no idea what to do with the data once they got their hands on it.
I mean, did they really think they could just grab a dump of T-Mobile's customer database and sell it to AT&T? C'mon. Let's think about that for a minute -- what the hell is AT&T going to do with it? I'm sure their marketing department knows all about T-Mobile's demographics versus their own, and if not (and if they care) they could find out with a few calls and some relatively small payments to a research firm. Same with just about anything else I can possibly imagine them extracting from T-Mobile's servers. If AT&T or Verizon is really dying to know something about T-Mobile's operations, they have lots of easier ways to figure it out that involve a lot less risk than buying red-hot DB dumps from criminals.
Also, anyone with half a brain ought to realize that all the telco companies live in fear of being broken into, and that a major breakin is going to hurt the public's perception of the entire industry. The U.S. cellular telcos are, basically, a cartel: and if there's one thing cartel members hate more than each other, it's disruptive outsiders. T-Mobile's competitors probably didn't respond because they thought it was a joke, or some sort of Nigeria scam; if they'd known it was serious, they almost certainly would have done what Pepsi did and called the cops. Not for altruistic reasons, but for sound business ones: having basically mercenary criminals screwing around, stealing data, scaring customers, and generally upsetting the normal business environment is not to any legitimate player's advantage.
The other red-flag that screams amateur hour about the whole thing is what they did after being turned down by the "competitors" -- they posted what amounts to a "for sale" ad to the Full Disclosure list. They thought that was the best venue for selling a shitload of customer financial records? Really? There are bulletin boards, whole online communities, where criminals trade identity information. It's a mature underground economy; the information they had -- names, addresses, CC numbers, SSNs -- would have been a fungible, commodity product, well-understood and easy to resell for cash.
However they got the information in the first place, it's pretty clear they didn't think their cunning plan all the way through.)
"Ladies and gentlemen, my killbot features Lotus Notes and a machine gun. It is the finest available."
It's not worthless - it's so valuable that it's radioactive. Any competitor coming anywhere near this data would get sued into oblivion.
As if they would confirm this. You'd have to be insane to turn around and go "yes, we have been compromised and any calls you make can and probably will be monitored by hackers". There would be a mass exodus from T-Mobile within the hour, and they would effectively go broke by the end of the month. If I was them, I'd be coordinating teams to vet every single one of the machines to be sure - not adding to the potential for a public hysteria in already troubled environments.
Even if this is a hoax, which it may well be, you don't want to be talking about it until afterwards when you can say something like "We had hackers breach our perimiter systems, but our superb security teams saw and stopped them before they were able to get anything but our publically available user manuals". It might be bullshit, but it sounds better than "we've been hacked, you're in the shit". Your average person could deal with the former, but doubtful that they could deal with the latter.
Me failed English...
FreeBSD over Linux. If my comments seem odd, this may explain...
What part of that did you mistake to read "I can't encrypt server side even if I must make clients use clear text" ?