LevelBlue Completes Acquisition of Cybereason. Learn more

LevelBlue Completes Acquisition of Cybereason. Learn more

Services
Cyber Advisory
Managed Cloud Security
Data Security
Managed Detection & Response
Email Security
Managed Network Infrastructure Security
Exposure Management
Security Operations Platforms
Incident Readiness & Response
SpiderLabs Threat Intelligence
Solutions
BY TOPIC
Offensive Security
Solutions to maximize your security ROI
Operational Technology
End-to-end OT security
Microsoft Security
Unlock the full power of Microsoft Security
Securing the IoT Landscape
Test, monitor and secure network objects
Why LevelBlue
About Us
Awards and Accolades
LevelBlue SpiderLabs
LevelBlue Security Operations Platforms
Security Colony
Partners
Microsoft
Unlock the full power of Microsoft Security
Technology Alliance Partners
Key alliances who align and support our ecosystem of security offerings

Did Grum Really Get Killed?

For several years before July 2012 takedown, Grum was one of the notorious spam botnets and at one time was responsible for more than 30% of spam worldwide. Last year's Grum botnet takedown was a victorious feat by the security community and could be considered as one of the most significant takedowns of2012. However, the effect of this takedown seems to be temporary as we've observed spam volume from Grum bot trickling back:

8475_2b04f4fb-74ff-47ee-bd37-189617fbbedf

Over the last little while, we run a number of Grum samples and observed new command & control (C&C) servers that the bot connects to:

  • 188.93.233.2
  • 185.4.227.170
  • 198.144.156.187
  • 80.86.253.3
  • 84.22.104.163

The usual set of command which is basically a HTTP GET request at port 80 can be observed when it communicates to its C&C server.

  • GET /spm/s_get_host.php?ver=[bot version]

    s_get_host.php - get the infected machine's IP address and hostname

  • GET /spm/s_alive.php?id=[botmachineid]&tick=[system tick]&ver=[bot version]&smtp=[ok|bad]

s_alive.php - reports back to the control server that the bot is alive. The data includes bot id, systemtick, bot version and smtp status to control server

  • GET /spm/s_task.php?id=[bot machineid]&tid=xxxxx

s_task.php - get task and spam templates.

  • GET /spm/s_report.php?task=[task id]&id=[botmachine id]&errors[xxx]=xx

s_report.php - reports back errors to the command and control server.

The spamming began right after it received the encrypted spam template:

12278_e300210f-dff7-4c1c-83f6-49892b613a26

The spam campaigns from Grum were the usual suspect: pharmaceutical spam. The link in the spam points to an illegal pharmacy website operation. I've also listed the Russian domains related to this spam campaign, here.

10150_7ba13323-7a0a-4e5c-a804-bf532439c139

The spam volume from Grum that we are seeing today is a pale shadow of what it was before the July 2012takedown. But it is worth noting that Grum is showing a slow come back. Perhaps bot herders behind Grum botnet are slowly rebuilding it again. We've been involved in helping various botnet takedowns before, but most of the time, the effect is temporary. It seems this botnet is deeply rooted, that you couldn't take it down by its branch and fruit, but by its roots.

ABOUT LEVELBLUE

LevelBlue is a globally recognized cybersecurity leader that reduces cyber risk and fortifies organizations against disruptive and damaging cyber threats. Our comprehensive offensive and defensive cybersecurity portfolio detects what others cannot, responds with greater speed and effectiveness, optimizes client investment, and improves security resilience. Learn more about us.

Latest Intelligence

Discover how our specialists can tailor a security program to fit the needs of
your organization.

Request a Demo