Fourth malware strain discovered in SolarWinds incident | ZDNet
Symantec said it identified Raindrop, the fourth malware strain used in the SolarWinds breach, after Sunspot, Sunburst, and Teardrop.
Catalin Cimpanu
By Catalin Cimpanu for Zero Day | January 19, 2021 -- 12:00 GMT (12:00 GMT) | Topic: Security
raindrop rain
Image via Ben Maguire
Cyber-security firm Symantec said it identified another malware strain that was used during the SolarWinds supply chain attack, bringing the total number to four, after the likes of Sunspot, Sunburst (Solorigate), and Teardrop.
SOLARWINDS UPDATES
SolarWinds: The more we learn, the worse it looks
CISA: US govt agencies must update right away
A second hacking group targets SolarWinds systems
Hackers accessed Microsoft source code
Microsoft quarantines trojanized apps
Microsoft identifies 40+ victims, most in US
Microsoft and industry partners seize key domain used in hack
SEC filing: 18,000 customers impacted
Breach is not a marketing opportunity
Named Raindrop, Symantec said the malware was used only during the very last stages of an intrusion, deployed only on the networks of very few selected targets.
Symantec said it encountered only four Raindrop samples in the cases it investigated until today.
Also: Best VPNs • Best security keys • Best antivirus
TIMELINE OF THE SOLARWINDS SUPPLY CHAIN ATTACK
But to understand Raindrop's role and position in these attacks, we must first go over the timeline of the entire SolarWinds incident.
Based on reports and information published by Microsoft, FireEye, CrowdStrike, and others, the SolarWinds intrusion is believed to have taken place in mid-2019 when hackers, believed to be linked to the Russian government, breached the internal network of SolarWinds, a Texas-based software maker.
The intruders first deployed the Sunspot malware, which they used exclusively inside SolarWinds' own network. CrowdStrike said the attackers used the malware to modify the build process of the SolarWinds Orion app and insert the Sunburst (Solorigate) malware inside new versions of Orion, an IT inventory management system.
These trojanized Orion versions went undetected and were active on the official SolarWinds update servers between March and June 2020. Companies who applied Orion updates also unwittingly installed the Sunburst malware on their systems.
But the Sunburst malware wasn't particularly complex and didn't do much except gather info about the infected network and send the data to a remote server.
Even if around 18,000 SolarWinds customers got themselves infected with the Sunburst malware, the Russian hacking group carefully selected its targets and opted to escalate attacks only in a handful of cases, for the likes of high-profile targets such as US government agencies, Microsoft, or security firm FireEye.
When hackers decided to "escalate their access," they used Sunburst to download and install the Teardrop malware [see past reports from Symantec and Check Point].
RAINDROP — TEARDROP'S SIBLING
But Symantec says that in some cases, the hackers chose to deploy the Raindrop malware strain instead of the more widely used Teardrop.
Despite being different strains, Symantec said the two backdoors had similar functionality, which the company described as being "a loader for [the] Cobalt Strike Beacon," which the intruders later used to escalate and broaden their access inside a hacked IT network.
But while both Raindrop and Teardrop were used for the same purpose, Symantec said that some differences also exist between the two, most being under the hood, at the code level, best described in the table below:
raindrop-teardrop-comparison.png
Image: Symantec
The other major difference is how the two malware strains were deployed.
Symantec said that the more widely used Teardrop was installed directly by the Sunburst malware, while Raindrop mysteriously appeared on systems where Sunburst was also found, with no direct evidence that Sunburst triggered its installation.
The US security firm said it's currently investigating how Raindrop was installed.
The most obvious avenue is found in previous reports on the SolarWinds hacks that mentioned that hackers also used the Sunburst malware to run various fileless PowerShell payloads, many of which would leave minimal forensic evidence on infected hosts. While unconfirmed, it may be possible that Raindrop is the result of these operations.
But the lesson here is that security teams investigating SolarWinds incidents inside their networks now also need to scan for the presence of another malware strain — Raindrop.
Catalin Cimpanu
By Catalin Cimpanu for Zero Day | January 19, 2021 -- 12:00 GMT (12:00 GMT) | Topic: Security
raindrop rain
Image via Ben Maguire
Cyber-security firm Symantec said it identified another malware strain that was used during the SolarWinds supply chain attack, bringing the total number to four, after the likes of Sunspot, Sunburst (Solorigate), and Teardrop.
SOLARWINDS UPDATES
SolarWinds: The more we learn, the worse it looks
CISA: US govt agencies must update right away
A second hacking group targets SolarWinds systems
Hackers accessed Microsoft source code
Microsoft quarantines trojanized apps
Microsoft identifies 40+ victims, most in US
Microsoft and industry partners seize key domain used in hack
SEC filing: 18,000 customers impacted
Breach is not a marketing opportunity
Named Raindrop, Symantec said the malware was used only during the very last stages of an intrusion, deployed only on the networks of very few selected targets.
Symantec said it encountered only four Raindrop samples in the cases it investigated until today.
Also: Best VPNs • Best security keys • Best antivirus
TIMELINE OF THE SOLARWINDS SUPPLY CHAIN ATTACK
But to understand Raindrop's role and position in these attacks, we must first go over the timeline of the entire SolarWinds incident.
Based on reports and information published by Microsoft, FireEye, CrowdStrike, and others, the SolarWinds intrusion is believed to have taken place in mid-2019 when hackers, believed to be linked to the Russian government, breached the internal network of SolarWinds, a Texas-based software maker.
The intruders first deployed the Sunspot malware, which they used exclusively inside SolarWinds' own network. CrowdStrike said the attackers used the malware to modify the build process of the SolarWinds Orion app and insert the Sunburst (Solorigate) malware inside new versions of Orion, an IT inventory management system.
These trojanized Orion versions went undetected and were active on the official SolarWinds update servers between March and June 2020. Companies who applied Orion updates also unwittingly installed the Sunburst malware on their systems.
But the Sunburst malware wasn't particularly complex and didn't do much except gather info about the infected network and send the data to a remote server.
Even if around 18,000 SolarWinds customers got themselves infected with the Sunburst malware, the Russian hacking group carefully selected its targets and opted to escalate attacks only in a handful of cases, for the likes of high-profile targets such as US government agencies, Microsoft, or security firm FireEye.
When hackers decided to "escalate their access," they used Sunburst to download and install the Teardrop malware [see past reports from Symantec and Check Point].
RAINDROP — TEARDROP'S SIBLING
But Symantec says that in some cases, the hackers chose to deploy the Raindrop malware strain instead of the more widely used Teardrop.
Despite being different strains, Symantec said the two backdoors had similar functionality, which the company described as being "a loader for [the] Cobalt Strike Beacon," which the intruders later used to escalate and broaden their access inside a hacked IT network.
But while both Raindrop and Teardrop were used for the same purpose, Symantec said that some differences also exist between the two, most being under the hood, at the code level, best described in the table below:
raindrop-teardrop-comparison.png
Image: Symantec
The other major difference is how the two malware strains were deployed.
Symantec said that the more widely used Teardrop was installed directly by the Sunburst malware, while Raindrop mysteriously appeared on systems where Sunburst was also found, with no direct evidence that Sunburst triggered its installation.
The US security firm said it's currently investigating how Raindrop was installed.
The most obvious avenue is found in previous reports on the SolarWinds hacks that mentioned that hackers also used the Sunburst malware to run various fileless PowerShell payloads, many of which would leave minimal forensic evidence on infected hosts. While unconfirmed, it may be possible that Raindrop is the result of these operations.
But the lesson here is that security teams investigating SolarWinds incidents inside their networks now also need to scan for the presence of another malware strain — Raindrop.
