SMS Trojan Steals From Android Owners
siliconbits writes "A Trojan posing as a media player for Android smartphones automatically sends text messages to premium rate numbers, according to Kaspersky Lab. Company officials say the Trojan, dubbed Trojan-SMS.AndroidOS.FakePlayer.a, is the first of its kind for the Android platform, even though SMS Trojans are currently the most widespread type of malware on mobile phones."
Or does it tell you what it's gonna do beforehand?
If you install something that says "THIS WILL COST YOU MONEY", and it sends SMS that costs you money, how exactly is that a "trojan"?
Well, what is the name of the malicious media player?
So, uhh, what's the name of the infected media player app? It's not in TFA, either.
require you to
1. enable "install from other places", since by default only market apps can be installed
2. be infinitely stupid??
regards,
Anonymous Coward
Hahaha! Good thing I have an iPhon.....*signal lost*
If mercenaries can find work in the middle east, why can't we hire them to find and dispose of the people making withdrawals from the bank accounts of the "premium rate" numbers?
This just really seems like one of those problems that some good old fashioned violence would be great for solving/deterring.
"Be prepared, son. That's my motto. Be prepared." --Joe Hallenbeck
All your text are belong to us!!
You know, I really wish articles like this would lead with THE NAME OF THE APP THAT HURTS SO BADLY. "A SMS trojan" is hardly specific. I'd like to know if that thing in my pocket is gonna rape my privacy.
It only goes to show, Winders is in there. No ways there be only Linux in there.
So, we know that the company will be releasing security software for android, we know that they have included a signature for thetrojan in their software...
But we don't know the name of the firkkin app that is actually doing it. Good thing those security software vendors are so concerned about our well being.
Why bother? I read it, and I still don't know silly details like what the name of this app is, or whether it's been pulled from the Android Market. Actually, now that I think about it, I don't even know *if* it was in the Android Market, or if it's a side-load app. For all I know, Kaspersky "discovered" a proof-of-concept app that they developed themselves. Yeah, that last bit is pretty unlikely, but reading TFA is no help at all in ruling it out.....
Content fail for TFA.
Some bring out the best in others, some the worst. Some bring out far more.
So this should lead to police activity quickly enough, right? One can't (at this time) prove where the trojan came from, but it's easy enough to see who benefits and what accounts the money gets paid into. That should all get frozen, cops should kick down some doors, machines should get confiscated?
Will this happen?
-- "Oh. This guy again."
http://www.readwriteweb.com/archives/first_trojan_for_android_phones_goes_wild.php
Absolute power corrupts absolutely. indymedia
With Trojan-SMS.AndroidOS.FakePlayer.a, you can now have two different trojans in your pocket to offer the ladies.
If your phone was in a protective case, like an iPhone 4, you would be infected with such trojans!!! Stupid Android users!!!
This type of malware was obvious from the beginning. My question is what would be the phone companies' response to this?
Will they;
a) just charge the user for the messages saying that they are SOL
b) void the charges
AccountKiller
Those installing applications from questionable sources get what they deserve.
Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
A company that makes money selling anti-virus software claims there is a Trojan that there android release will fix.
Ok, I'm willing, for the moment, to say that
s true and has happened.
The article doesn't give any information. Was this spread through the market, or did some select the option to install apps from anywhere and then get hit?
OTOH, this does follow my belief that online and smart phone financial transactions will end. The sheer number and easy or scamming people can't be stopped.
I hope I am wrong. I would love to make my smart phone my wallet.
The Kruger Dunning explains most post on
How the fuck can you get ripped off by an 'SMS Trojan'?
Okay, so it sends SMS messages to 'preimum numbers' ... so its a safe bet that the guy who wrote it is the guy who owns those 'premium numbers'.
It should take all of about 8 seconds for someone to turn off the SMS number so the messages no longer get charged to anyone and arrest the fink who started it.
Could it be someone using a trojan directed at an innocent 3rd party? Sure. Is that whats happening? No, stop being so naive.
Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
If someone you don't like makes money off of SMS messages, write a Trojan that sends them stuff, get people to download it, and viola! The SMS guys get raided!
To a Lisp hacker, XML is S-expressions in drag.
This is the iPhone we're talking about, how'd you manage to get a signal in the first place!?
(Must have one of those Vulcan pinch phone holders...)
"Victory means exit strategy, and it's important for the President to explain to us what the exit strategy is." G.W.Bush
Ever notice that most (not all, but most) of the AV firms are from Russian/Baltic regions? From the guys who write the most virum and hacking?
However we don't need to know any of that because it's clear that the application asks for permission to send SMS, the user accepts and then the app does exactly what it said it was going to do.
This is where I'm not sure the Android security model is doing you many favors.
You download a media player, go to install it, and you get a list of things it wants to do - access media library, perhaps access contacts for sharing, and so on... and way down at the end, a little notice about accessing SMS. You might not even think about it much being close to permissions for contacts.
So you agree.... and then it proceeds.
That's why I think a model where the system asks for permission as the phone accesses each protected resource is probably somewhat healthier. Then you can see in context just what it plans to do. Then you would be wondering at any point in time using the media player, why is it sending an SMS to this number I do not recognize?
It doesn't have to ask you every time, just the first few times and then it can be sure you really are OK with it accessing a specific resource.
"There is more worth loving than we have strength to love." - Brian Jay Stanley
FAT32 is still the logical choice, despite its security issues
Bill gates? Is that you?
Because at this point we all have seen when you design from the start for convenience OF THE DEVELOPER instead of security. The Windows world has been living with the consequences of that choice for decades now.
So now at the brink of a whole new wave of OS's, is not the time to repeat the mistakes of our virtual forefathers. Android could move apps into a smaller embedded filesystem in a file, but in no way should it open up users to app modifications like this.
"There is more worth loving than we have strength to love." - Brian Jay Stanley
Any suggestions for an andriod app that can quickly do a security audit (assuming the API's allow it)?
I'm thinking that it would list in table form all the installed applications (the rows) with all the security access types (columns) with all the cells checked or unchecked. This would allow an "at a glance" review of all the apps without having to navigate into the management of each one.
It's rather the convenience of the user
That's not so.
Because I already described how you would have the same exact functionality with an embedded file system in one large file on the DOS partition, where apps would go. That would be mounted and have proper security.
To the user everything works as it does now, it's just that underneath you can't have apps stored on an external partition infected by another app nearly as easily.
If you wanted to let users drag apps onto the removable storage you could still let them do that and add them to the safe partition on attachment of the card, not letting anything in the system write to the card until the app extraction was complete.
"There is more worth loving than we have strength to love." - Brian Jay Stanley
Yes, I read your sig. Which is why being willing to repeat the same mistakes really made me do a double-take.
There is a *reason* FAT32 is the standard for removable mass storage
Yes, I totally agree with that. It's utterly unreasonable at this point (probably forever sadly) for removable media to be anything but FAST 32.
I am saying apps don't have to sit naked upon that.
Perhaps I was not clear enough but I was envisioning a binary blob in the FAT 32 system, that was an EXt4 (or whatever) disk image. The system would mount that and read apps from it; apps that were moved by the user to removable media would go in there. So you'd have a mounted file system with full security and no-way for anything to access an application on the weaker FAT32 partition (the blob could be encrypted to prevent direct tampering).
So, yes, Android *could* move apps into a different file system (or even, as you suggest, into an embedded file system inside a single file), but then you would completely lose the ability to pull your SD card from your phone and access the data on the card from your PC
Not if you think carefully about the problem.
And that's my point. There's always a technical way that will work, if you think long enough about it. But in this case they rushed into a solution that was easier to the developers and left the user totally exposed. This is what I am saying "NO NO NO" to. This is what we cannot continue to allow, especially not as we transition to a whole now set of mobile OS's.
"There is more worth loving than we have strength to love." - Brian Jay Stanley
CNET reports here that this is an app external to the Android Market, and you had to get it from a maliscious (I assume) website.
I saw one report from a phone user claiming they saw it as a 13kb download that they didn't think they asked for, and deleted it. No idea if that is credible.
So it does appear, at least for now, that this is not a Market app.
deleting the extra space after periods so i can stay relevant, yeah.
If you look at the screen at all, you can't miss it.
Even though saying a user "can't miss" something in a list of other things seems wrong to me from direct experience, I'm willing to concede that point.
Because it does not matter.
That screen is telling the user that at some theoretical point in the future, the app may want to SMS someone. Well who cares then? The user doesn't know what the app really does yet, perhaps (in the movie player case) it lets them SMS URL's of cool movies. The user has no way at that point to know which features are reasonable for an application; they have not used it yet. So generally they would accept just about anything because they could see they MIGHT want to do something.
Now consider instead what happens when the user is simply watching a movie or video clip, and all the sudden they get an alert asking to SMS a number they have never seen. Now the user is thinking "what the hell" and not very likely to agree - they didn't ask to SMS anyone and they just want to get back to the movie. Permission denied.
I think it's great that Android has these list of abilities and you can turn them off individually (well as a user I think it's great but then developer opinions should not matter). But I do not think the presentation of them is great, no matter how you adorn the more perilous choices.
"There is more worth loving than we have strength to love." - Brian Jay Stanley
The Nokia N900 has this feature in official firmware.
Seriously, that sounds like the reason why I can't just drag MP3s to an ipod from any OS without apple software. Its all about security, right? Personally I would take the risk and retain the hack-ability.
I'm not saying you place all files in there, just application binaries.
Even application writable directories could be on FAT; music would certainly stay there.
There's no reason you can't leave the SD card generally writable and useful, but still prevent applications from being hacked from within.
And the reason you can't randomly drag files into an iPod by default is because most users get lost when you start talking about files and where they are. That part is not as much about security as user experience. It's not like ou can't buy a music player that does let you drag things into it, Apple simply has no interest in producing a device that you access in that way.
The inclusion of the iPod is irrelevant though, since we are talking about how to close an Android application security hole.
"There is more worth loving than we have strength to love." - Brian Jay Stanley
No trojan would spread all that rapidly unless it was spread via the marketplace, and anyone submitting anything to the marketplace (even free stuff) has to go through a credit background check. Not to mention Google has the ability (and has used it) to remotely wipe programs installed from the marketplace.
Mark of a good virus is its ability to spread ;).
There is something that I miss in all of the reports I've read about this "trojan", they fail to actually name the app that's supposedly causing all this. Seriously, was the application called "fakeplayer" or something?
It's useful information to know what app is malicious, don't you think? So that you can avoid installing it, or to remove it from your phone before it causes more damage.
80 CC D8 AF AE D3 AB 54 B7 2E CE 67 C7
Finally someone that understands what I am proposing. The only tricky part would be mounting that virtual partition, that would probably require some serious coding somewhere in the Android filesystem to make that work...
Another cool thing is then you could use this support elsewhere - like a small encrypted data bundle for an application that only it could decode. So it would provide fringe benefits.
"There is more worth loving than we have strength to love." - Brian Jay Stanley
I've read on some sites that say Android has no way to revoke permissions after an app is installed. Had anyone come up with a way to revoke permissions?
*It's not what you can do for the Dark Side but what the Dark Side can do for you!*
Yes, we should all read the permissions that an app requires. But, recently, a lot of free apps are advertisement supported. And those ask for full Internet access to fetch the ads. This seems a hole that is hard to block.
The thing that annoys me the most about Android's permissions model is that it's all-or-nothing -- you either grant every single permission in the manifest or you grant none of them and then don't get to install the app.
I'd much much much prefer being able to say "no, this dumb widget does not need to access my location (ads) or know my phone number (ads)" or "no, this 'trojan' does not need to be able to send SMS". But, you can't - you eithe grant access to everything, or you can't install the app. I was very disappointed by that.