Vulnerabilities / Threats

6/19/2018
03:20 PM
Connect Directly
Twitter
LinkedIn
Google+
RSS
E-Mail
50%
50%

'Olympic Destroyer' Reappears in Attacks on Europe, Russia

The attack group known for targeting the 2018 Winter Olympics has resurfaced in campaigns against European financial and biochem companies.

The 2018 Winter Olympics may have ended on February 25, 2018 but the group behind "Olympic Destroyer," the attack known for targeting the Games, is still going strong. Kaspersky Lab researchers have spotted the threat actor(s) targeting organizations across Europe.

Olympic Destroyer, a destructive network worm, appeared prior to the Opening Ceremonies when Olympics officials confirmed technical issues affecting systems. It rendered machines unusable by deleting shadow copies and event logs, and tried to use PsExec and WMI to move across the environment, a behavior Cisco Talos analysts had seen in BadRabbit and NotPetya.

The Olympics attack stood out because it was designed to damage, explains Kurt Baumgartner, principal security researcher at Kaspersky Lab. "That's the sort of destructive activity we don't see all the time," he says of the February campaign. The way this group targeted partner organizations and supply chain vendors to disrupt the Games set them apart from other ATPs.

Disruption, along with financial gain, seems to be a motivator for the actor's latest threat. Kaspersky Lab analysts determined the group behind Olympic Destroyer is responsible for a new wave of cyberattacks targeting financial and biochemical organizations throughout Europe, a conclusion based on malware sets, targeting, and identifying and testing macros in the code.

Meet the New Targets: Financial, Biochem Firms

Researchers continued to track the group after the Olympics. It resurfaced with new activity in May and June 2018 when new spear-phishing attachments closely resembled weaponized documents used by the group in previous attacks. Based on Kaspersky Lab's telemetry, characteristics of the malicious files, and other TTPs, they determined it was the same group.

"These guys are being very careful about their infrastructure, and about tools and traces in developing their malware that may lead us to believe this is one APT instead of another," says Baumgartner. The group continues to use a non-binary executable infection vector and obfuscated scripts to avoid detection. Its spear-phishing techniques and content are very carefully considered, which he says is a continuation of their behavior during the Olympics.

This time around, the attackers behind Olympic Destroyer are targeting financial organizations in Russia, along with biological and chemical-threat prevention labs in Europe and Ukraine. Given their limited visibility, researchers can only speculate about the targets based on the email subjects, file names, and content of weaponized documents.

One such document that stood out spoke of the "Spiez Convergence," a biochemical threat research conference organized by Spiez Laboratory and held in Switzerland. Some files include words in both Russian and German; one document included an image with Russian language.

Baumgartner says there are many organizations that could be related to this particular conference, and the group's targeting of this event aligns with their targeting of Olympics partners and supply chain vendors. However, the group's decision to hit financial businesses in Russia is unusual. There could be a couple of reasons for this, he speculates.

One possibility is the group is outsourcing, pulling in people who have expertise in attacking financial institutions so they can run campaigns to generate funds while the group targets European organizations. Another is that the malware is being shared and used by multiple groups, so financial criminals with different motivations are pursuing the same targets as the Olympic Destroyer attackers. Baumgartner points out the latter scenario is less likely.

While the motivation for attacking financial organizations is rooted in money, the drive to attack European biological and chemical firms is more puzzling. Baumgartner says "the motivation in all likelihood would be non-financial … it could be for espionage purposes."

An Elusive Attacker

"The other thing I think is really interesting about this group is how masterful they are at cloaking exactly who they are," Baumgartner notes.

The true identity of the Olympic Destroyer attackers has so far remained a mystery for some security experts. Olympic Destroyer demonstrated deceptive behavior and excessive use of false flags, which tricked researchers who were trying to determine which group was responsible.

Some analysts used malware similarities to link Olympic Destroyer to three Chinese-speaking APT actors and Lazarus Group, which is allegedly based in North Korea. Some code contained hints of the EternalRomance exploit; some code was similar to NotPetya and BadRabbit.

Kaspersky Lab reports some of the TTPs and operational security used in Olympic Destroyer resemble activity from the Sofacy APT group, implying a deep knowledge of Sofacy given the difficulty of mimicking TTPs. However, given Olympic Destroyer's expertise in false flags, the researchers for now have established this connection "with low to moderate confidence."

Related Content:

 

Top industry experts will offer a range of information and insight on who the bad guys are – and why they might be targeting your enterprise. Click for more information

Kelly Sheridan is the Staff Editor at Dark Reading, where she focuses on cybersecurity news and analysis. She is a business technology journalist who previously reported for InformationWeek, where she covered Microsoft, and Insurance & Technology, where she covered financial ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
High Stress Levels Impacting CISOs Physically, Mentally
Jai Vijayan, Freelance writer,  2/14/2019
Valentine's Emails Laced with Gandcrab Ransomware
Kelly Sheridan, Staff Editor, Dark Reading,  2/14/2019
Making the Case for a Cybersecurity Moon Shot
Adam Shostack, Consultant, Entrepreneur, Technologist, Game Designer,  2/19/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
5 Emerging Cyber Threats to Watch for in 2019
Online attackers are constantly developing new, innovative ways to break into the enterprise. This Dark Reading Tech Digest gives an in-depth look at five emerging attack trends and exploits your security team should look out for, along with helpful recommendations on how you can prevent your organization from falling victim.
Flash Poll
How Enterprises Are Attacking the Cybersecurity Problem
How Enterprises Are Attacking the Cybersecurity Problem
Data breach fears and the need to comply with regulations such as GDPR are two major drivers increased spending on security products and technologies. But other factors are contributing to the trend as well. Find out more about how enterprises are attacking the cybersecurity problem by reading our report today.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-8980
PUBLISHED: 2019-02-21
A memory leak in the kernel_read_file function in fs/exec.c in the Linux kernel through 4.20.11 allows attackers to cause a denial of service (memory consumption) by triggering vfs_read failures.
CVE-2019-8979
PUBLISHED: 2019-02-21
Koseven through 3.3.9, and Kohana through 3.3.6, has SQL Injection when the order_by() parameter can be controlled.
CVE-2013-7469
PUBLISHED: 2019-02-21
Seafile through 6.2.11 always uses the same Initialization Vector (IV) with Cipher Block Chaining (CBC) Mode to encrypt private data, making it easier to conduct chosen-plaintext attacks or dictionary attacks.
CVE-2018-20146
PUBLISHED: 2019-02-21
An issue was discovered in Liquidware ProfileUnity before 6.8.0 with Liquidware FlexApp before 6.8.0. A local user could obtain administrator rights, as demonstrated by use of PowerShell.
CVE-2019-5727
PUBLISHED: 2019-02-21
Splunk Web in Splunk Enterprise 6.5.x before 6.5.5, 6.4.x before 6.4.9, 6.3.x before 6.3.12, 6.2.x before 6.2.14, 6.1.x before 6.1.14, and 6.0.x before 6.0.15 and Splunk Light before 6.6.0 has Persistent XSS, aka SPL-138827.