Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Vulnerabilities / Threats

Russian Masterminds Ran Rustock Botnet, Microsoft Says

Forensic analysis of server hard drives points to Russian controllers and turns up email templates mentioning that old favorite, Viagra.

Strategic Security Survey: Global Threat, LocalPain
Strategic Security Survey: Global Threat, Local Pain
(click image for larger view and for full slideshow)
Has your botnet gone missing? Microsoft has taken the unusual step of running advertisements in two Russian newspapers, alerting the owners of the Rustock botnet that they can attempt to reclaim their confiscated property. The move is part of Microsoft's efforts to identify and serve court summonses to the Rustock botnet masterminds.

"Based on evidence gathered in the case, we have reason to believe that the people behind the Rustock botnet either have operated or are operating out of Russia," said Richard Boscovich, a senior attorney in the Microsoft Digital Crimes Unit, in a blog post. "Consequently, we have placed advertisements in two mainstream Russian newspapers, the Delovoy Petersburg in St. Petersburg and Moscow's daily paper, The Moscow News."

In April, the U.S. District Court for the Western District of Washington instructed Microsoft to submit status updates about its efforts to put names to the "John Does" in its initial anti-Rustock lawsuit. That civil lawsuit, unsealed by the court in March, had alleged that John Does were "controlling a computer botnet and thereby injuring Microsoft and its customers."

Accordingly, Boscovich said that the advertisements "honor our legal obligation to make a good faith effort to contact the owners of the IP address and domain names that were shut down when Rustock was taken offline." The ads also designate a time and place where the botnet owners can argue their side of the case, as well as a related website, if they would rather argue their case remotely.

"Although history suggests that the people associated with the IP addresses and domain names connected with the Rustock botnet are unlikely to come forward in response to a court summons, we hope the defendants in this case will present themselves," he said.

What evidence does Microsoft have that the botnets were being run by people in Russia? According to court documents, Microsoft analyzed 20 seized hard drives from servers that ran Rustock, and found that they'd been used to access numerous websites based in Russia, including the Web-based email service mail.ru, as well as the free software downloading portal freesoft.ru. Another one of the drives had also been used to launch "cyber-attacks into Russian IP (Internet Protocol) space," according to the documents.

Microsoft said that it also had identified a specific WebMoney account that was used to pay for some command-and-control servers. According to the court documents, "WebMoney's records indicate that the owner of the WebMoney account is identified as a Vladimir Alexandrovich Shergin, associated with an address in Khimki, a city near Moscow." To date, however, Microsoft doesn't know whether this name is authentic, fake, or stolen.

The court documents also provide an interesting glimpse into how criminals create and manage botnets. For example, 18 of the seized hard drives used The Onion Router (better known as TOR) to give attackers anonymous access to the servers, as well as to give the servers anonymous access to the Internet. Microsoft also found "custom written software relating to assembly of spam emails and text files"--with one text file alone containing 427,000 harvested email addresses--as well as email templates relating to numerous pharmaceuticals, including Valium, Viagra, and Vicodin.

Microsoft is continuing to pursue botnet leads. For example, it's identified email addresses associated with the botnet masterminds, and is currently awaiting responses to subpoenas it's served to domain registrars and email hosting providers, which may help positively identify the owners of those email addresses.

Microsoft said it's also continuing to investigate "Cosma2k," which was the username associated with someone who signed up for multiple command-and-control servers. According to Microsoft, "this nickname has been associated with the several names: Dmitri A. Sergeev, Artem Sergeev, and Sergey Vladomirovich Sergeev."

Microsoft's use of a civil lawsuit to shut down a botnet was a novel legal strategy that earned it both praise and condemnation from various security, privacy, and legal experts, chiefly because Microsoft didn't just sue the botnet's unknown operators, but physically confiscated their equipment.

But Microsoft was also taking advantage of a rare opportunity. All of the physical servers that served as the Rustock command-and-control system were located--somewhat brazenly, on the part of the masterminds--at U.S. hosting sites. Accordingly, Microsoft gained a court order that enabled it, in conjunction with the U.S. Marshals Service, to physically seize those servers, knocking Rustock offline.

Industry watchers say that Microsoft's Rustock-busting strategy appears to have worked. A recent report from McAfee confirmed that the volume of Rustock traffic has decreased significantly.

In this new Tech Center report, we profile five database breaches--and extract the lessons to be learned from each. Plus: A rundown of six technologies to reduce your risk. Download it here (registration required).

Comment  | 
Print  | 
More Insights
Comments
Oldest First  |  Newest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 9/21/2020
Hacking Yourself: Marie Moe and Pacemaker Security
Gary McGraw Ph.D., Co-founder Berryville Institute of Machine Learning,  9/21/2020
Startup Aims to Map and Track All the IT and Security Things
Kelly Jackson Higgins, Executive Editor at Dark Reading,  9/22/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Special Report: Computing's New Normal
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
How IT Security Organizations are Attacking the Cybersecurity Problem
How IT Security Organizations are Attacking the Cybersecurity Problem
The COVID-19 pandemic turned the world -- and enterprise computing -- on end. Here's a look at how cybersecurity teams are retrenching their defense strategies, rebuilding their teams, and selecting new technologies to stop the oncoming rise of online attacks.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-24213
PUBLISHED: 2020-09-23
An integer overflow was discovered in YGOPro ygocore v13.51. Attackers can use it to leak the game server thread's memory.
CVE-2020-2279
PUBLISHED: 2020-09-23
A sandbox bypass vulnerability in Jenkins Script Security Plugin 1.74 and earlier allows attackers with permission to define sandboxed scripts to provide crafted return values or script binding content that can result in arbitrary code execution on the Jenkins controller JVM.
CVE-2020-2280
PUBLISHED: 2020-09-23
A cross-site request forgery (CSRF) vulnerability in Jenkins Warnings Plugin 5.0.1 and earlier allows attackers to execute arbitrary code.
CVE-2020-2281
PUBLISHED: 2020-09-23
A cross-site request forgery (CSRF) vulnerability in Jenkins Lockable Resources Plugin 2.8 and earlier allows attackers to reserve, unreserve, unlock, and reset resources.
CVE-2020-2282
PUBLISHED: 2020-09-23
Jenkins Implied Labels Plugin 0.6 and earlier does not perform a permission check in an HTTP endpoint, allowing attackers with Overall/Read permission to configure the plugin.