Risk
9/26/2010
10:49 PM
George V. Hulme
George V. Hulme
Commentary
50%
50%

Zeus Targeting Mobile Phone Authentication

A new variant of the Zeus botnet aims to circumvent an increasingly popular mode of two-factor authentication among financial institutions and other enterprises.

A new variant of the Zeus botnet aims to circumvent an increasingly popular mode of two-factor authentication among financial institutions and other enterprises.Anyone who has been following IT security long enough knows that it's a never ending game of leapfrog. As businesses and the security industry devise new ways to thwart attacks, criminal attackers find new ways to do their deeds. It's a game that's as old as crime itself, and I don't see it going away any time soon.

Enter the new variant of the infamous Zeus malware. According to Spanish security firm S21sec, Zeus authors have a plan to render an increasingly popular form of multi-factor less effective.

Increasingly banks and others are turning to mobile phone SMS texting features as a way to add a layer of additional authentication for users and transactions. For instance, last week when I used my online banking service to make a transfer to another customer the bank sent a code to my cell phone that I had to enter back online to complete the transaction.

Bad guys want to get in the middle of these transactions. From S21sec's security blog:

In this post, we are going to talk about a better alternative planned by a ZeuS gang: infect the mobile device and sniff all the SMS messages that are being delivered. The scenario is now easier:

- The attacker steals both the online username and password using a malware (ZeuS 2.x)

- The attacker infects the user's mobile device by forcing him to install a malicious application (he sends a SMS with a link to the malicious mobile application)

- The attacker logs in with the stolen credentials using the user's computer as a socks/proxy and performs a specific operation that needs SMS authentication

- An SMS is sent to the user's mobile device with the authentication code. The malicious software running in the device forwards the SMS to other terminal controlled by the attacker

- The attacker fills in the authentication code and completes the operation.

That's certainly worthy of note, and it shows that attackers aren't going to stand still. They never have, and they never will. Does this mean SMS is dead as a form of additional authentication? Absolutely not. It still significantly raises the bar for the bad guys.

Interesting, however, that this bad news for SMS authentication tactics hits around the same time that Google announces its going to support SMS text messaging to authenticate to its online applications.

For my security and technology observations throughout the day, follow me on Twitter.

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Flash Poll
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2013-7444
Published: 2015-09-01
The Special:Contributions page in MediaWiki before 1.22.0 allows remote attackers to determine if an IP is autoblocked via the "Change block" text.

CVE-2015-2807
Published: 2015-09-01
Cross-site scripting (XSS) vulnerability in js/window.php in the Navis DocumentCloud plugin before 0.1.1 for WordPress allows remote attackers to inject arbitrary web script or HTML via the wpbase parameter.

CVE-2015-6520
Published: 2015-09-01
IPPUSBXD before 1.22 listens on all interfaces, which allows remote attackers to obtain access to USB connected printers via a direct request.

CVE-2015-6727
Published: 2015-09-01
The Special:DeletedContributions page in MediaWiki before 1.23.10, 1.24.x before 1.24.3, and 1.25.x before 1.25.2 allows remote attackers to determine if an IP is autoblocked via the "Change block" text.

CVE-2015-6728
Published: 2015-09-01
The ApiBase::getWatchlistUser function in MediaWiki before 1.23.10, 1.24.x before 1.24.3, and 1.25.x before 1.25.2 does not perform token comparison in constant time, which allows remote attackers to guess the watchlist token and bypass CSRF protection via a timing attack.

Dark Reading Radio
Archived Dark Reading Radio
Another Black Hat is in the books and Dark Reading was there. Join the editors as they share their top stories, biggest lessons, and best conversations from the premier security conference.