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.


09:00 AM
Connect Directly

Botnets Behind Georgian Attacks Offer Clues

Scrutiny of botnet activity indicates Russia's attacks on Georgia weren't state-sponsored

At a closed-door Internet security summit in Estonia this week, a researcher will reveal new findings on the botnets behind the cyber-attacks on the former Soviet republic of Georgia that began last month and remains under way today. (See Georgian Government, News Sites Under Cyber Attack.)

Arbor Networks researchers Danny McPherson and Jose Nazario say that their latest findings indicate Georgia retaliated by waging some distributed denial-of-service (DDOS) attacks of its own on Russian Websites. The researchers found no evidence that Russia’s attacks on Georgia -- nor Georgia's responses -- were full-blown, state-sponsored cyber-warfare.

McPherson will present this new research on Thursday at the Internet Security Operations and Intelligence summit in Tallinn, Estonia.

At the height of the attacks last month, the Georgian government issued a statement from a temporary Website saying that its sites and some Georgian news sites were under a coordinated denial-of-service attack from Russia. The attacks started in July with a DDOS on the president of Georgia’s Website.

Nazario, security researcher for Arbor, says the Georgian president’s Website, Georgian ministries, and other sites there are still under DDOS attack.

And the researchers discovered a couple of botnets that have been DDOS’ing both .ru (Russian) and .ge (Georgian) hosts, suggesting that the attacks may be the work of instigators from outside both governments. “We have further strengthened our feeling that this is non-state actors at this time. But we don’t know why the botnets struck. Was it nationalism? Was it anger? Or was it for-hire? We don’t know and we may never know,” Nazario says.

The Russian-run Machbot botnet was behind the July attacks on the Georgian president’s site, the researchers say. “Machbot is primarily a Web-based Russian DDOS botnet written in Russian, used by several different groups, but not widely available,” says McPherson, chief research officer for Arbor. “These were the first attacks we observed that appeared to be related to this conflict. Interestingly, the C&C [command and control] of Machbot is located in the U.S.”

The Arbor researchers warned back in January that Machbot and other Web-based botnets from Russia could signal the arrival of larger and more politically motivated DDOS attacks worldwide. (See DDOS Botnets Thriving, Threatening.)

One of those botnets, Black Energy, was a key player in the Georgian DDOS strikes. At their peak, the Georgian attacks hit 800 Mbit/s, eight times larger than the attacks on Estonia. But the peak attack duration was six hours, which was shorter than the peak in Estonia, Nazario says. “There were more botnets, it seems, than there were in the Estonia” attacks, he says.

While the botnets waged brute-force attacks, the targets they went after weren’t especially sensitive, he says. “Almost none of [the sites] were required for daily operations,” Nazario says.

McPherson says he didn’t see much volunteer bot activity, despite reports that some Russians were offering up their machines to DDOS Georgia. “There were lots of invitations sent, as with Estonia, and perhaps even more. We didn't see any indication of a large number of these types of participants this time around,” he says.

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

  • Arbor Networks Inc. Kelly Jackson Higgins is the Executive Editor of Dark Reading. She is an award-winning veteran technology and business journalist with more than two decades of experience in reporting and editing for various publications, including Network Computing, Secure Enterprise ... View Full Bio

    Recommended Reading:

    Comment  | 
    Print  | 
    More Insights
  • Comments
    Newest First  |  Oldest First  |  Threaded View
    COVID-19: Latest Security News & Commentary
    Dark Reading Staff 6/1/2020
    Stay-at-Home Orders Coincide With Massive DNS Surge
    Robert Lemos, Contributing Writer,  5/27/2020
    Register for Dark Reading Newsletters
    White Papers
    Cartoon Contest
    Write a Caption, Win a Starbucks Card! Click Here
    Latest Comment: It's the latest version of antivirus.
    Current Issue
    How Cybersecurity Incident Response Programs Work (and Why Some Don't)
    This Tech Digest takes a look at the vital role cybersecurity incident response (IR) plays in managing cyber-risk within organizations. Download the Tech Digest today to find out how well-planned IR programs can detect intrusions, contain breaches, and help an organization restore normal operations.
    Flash Poll
    Twitter Feed
    Dark Reading - Bug Report
    Bug Report
    Enterprise Vulnerabilities
    From DHS/US-CERT's National Vulnerability Database
    PUBLISHED: 2020-06-02
    ZNC before 1.8.1-rc1 allows attackers to trigger an application crash (with a NULL pointer dereference) if echo-message is not enabled and there is no network.
    PUBLISHED: 2020-06-02
    An issue was discovered in fastecdsa before 2.1.2. When using the NIST P-256 curve in the ECDSA implementation, the point at infinity is mishandled. This means that for an extreme value in k and s^-1, the signature verification fails even if the signature is correct. This behavior is not solely a us...
    PUBLISHED: 2020-06-02
    common.php in the Gravity Forms plugin before 2.4.9 for WordPress can leak hashed passwords because user_pass is not considered a special case for a $current_user->get($property) call.
    PUBLISHED: 2020-06-02
    In Joomla! before 3.9.19, missing token checks in com_postinstall lead to CSRF.
    PUBLISHED: 2020-06-02
    In Joomla! before 3.9.19, lack of input validation in the heading tag option of the "Articles - Newsflash" and "Articles - Categories" modules allows XSS.