Welcome Guest. | Log In | Register | Membership Benefits

New Windows Worm Wriggling Through Networks

'Morto' targets weak passwords, usernames and spreads via the Remote Desktop Protocol

Aug 29, 2011 | 04:10 PM | 

By Kelly Jackson Higgins
Dark Reading
A retro worm attack is underway that takes the unusual spin of employing the Remote Desktop Protocol (RDP) in Windows' remote desktop connection feature as its attack vector.

Researchers from Microsoft, F-Secure, eEye Digital Security, and other organizations say the so-called Morto worm infects Windows workstations and Windows servers. It spreads by uploading a Windows DLL file to a targeted machine. The worm looks for weak administrator passwords in Remote Desktop on an organization's network -- everything from "12345" to "admin" and "password."

Researchers say the attack could be used for various purposes, including distributed denial-of-service (DDoS) attacks against targeted organizations. "The remote control feature allows bot-like control of the infected machines and they can be used for basically any purpose," says Mikko Hypponen, chief research officer of F-Secure Lab.

Microsoft's Malware Protection Center (MMPC), which sounded the alarm about the worm over the weekend, on Friday added detection for Worm:Win32/Morto.A. The relative number of infections isn't as high as with other malware families, but the worm generates "noticeable" amounts of traffic, according to Microsoft.

As of Saturday, there were only a few thousand computers infected with Morto, according to Microsoft's data. That's in contrast to nearly 30,000 infected with the Sality family of malware, and more than 10,000 with IRCbot malware, according to Microsoft.

"Based on telemetry through the remainder of Sunday, August 28, we are continuing to see low detections in comparison to established malware families as mentioned in the MMPC blog," says Pete Voss, senior response communication manager for Microsoft Trustworthy Computing. "It’s important to remember that this malware does not exploit a vulnerability in Remote Desktop Protocol, but instead relies on weak passwords ... We encourage people to use strong passwords to help protect their systems."

Researchers for the Contagio blog note that Morto generates significant traffic, and appears to have ties to China and Hong Kong. "I can add that it runs what it looks like a quick DoS test against one Google IP. In addition, it creates a lot of traffic: RDP scans, downloads, receiving commands, and interesting DNS queries for command and control servers," says a post by "Mila" today. "Judging by the domain owners of CC servers (China) and their location (Hong Kong), I would say it is likely it be cybercrimeware originating in erm...Asia. I don't know how difficult it is for a foreigner to register domains with Jiangsu Bangning Science & technology Co. Ltd.in China. One of the domains existed for a few years and changed several Chinese registrars and hosting companies. Like in Russia, DDoS attack crimes are very common in China."

Once Morto compromises one system, it connects to a command and control server to download information and to update its malware. "It also terminates processes for locally running security applications in order to ensure its activity continues uninterrupted. Affected users should note that a reboot may be required in order to complete the cleaning process," Hil Gradascevic of MMPC Melbourne blogged yesterday.

Marc Maiffret, CTO of eEye, says there are some common-sense ways to prevent being hit by "this silly worm."

Among his recommendations: RDP access from the Internet should use VPN authentication. "You need to always be minimizing your attack surface, and a great example of that is not allowing RDP to be probed by any joe hacker with a port scanner," Maiffret blogged today. Stop using weak passwords, he says, and try to throw off the worm and other attacks by moving your network services to different, non-standard ports. "This can be done for RDP through a simple registry key change which makes it easy to standardize across your entire network if you so choose," he says.

Meanwhile, Microsoft says Morto also tries to connect to targeted host systems if it can't get to an admin account, using easy-to-guess usernames like "admin" and "guest," for example.

Morto is also known as Trojan horse Generic24.OJQ (AVG); Trojan.DownLoader4.48720 (Dr.Web) ; Win-Trojan/Helpagent.7184 (AhnLab); Troj/Agent-TEE (Sophos); and Backdoor:Win32/Morto.A (Microsoft).

Have a comment on this story? Please click "Add Your Comment" below. If you'd like to contact Dark Reading's editors directly, send us a message.



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

Dark Reading encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dark Reading 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. Dark Reading 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.
Subscribe to RSS



Authentication Reports

report What's Next for Certificate Technology
A recent rash of certificate authority breaches has left a bad taste in many people's mouths. There is no one reason for the breaches. The compromises were the result of a breakdown in people, processes and technology, but not necessarily the certificates themselves. We take a look at what?s wrong with certificate technology, what can be done to fix it, and what's down the road for certificates and CAs.

report Will Smartcards Live Up to Their Name?
Recent compromises of smartcard data have exacerbated concerns about the technology?s privacy, security and standards (or lack thereof). Yet the promise of smartcards is too compelling to ignore. New technologies and applications prompt us to take a fresh look.

report Get The Best Of Biometrics
As data volume and sensitivity grow, companies cannot rely on password- and token-based authentication. Biometrics can be used to provide strong access control, but you must weigh added complexity and costs against assurance that users are who they say they are.

Other reports from the Authentication Tech Center:




Featured Webcasts
Featured Whitepapers
Featured Reports