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.

Security Management //

SOC

12/18/2018
08:15 AM
Scott Ferguson
Scott Ferguson
News Analysis-Security Now
50%
50%

Shamoon Malware Re-Emerges With Attacks in Italy, Middle East

Over the last week, several reports emerged that the Shamoon malware, which was last seen in 2016, has re-emerged with attacks in Italy and the Middle East. This version includes a destructive data file wiper.

Over the last week, several reports have found that the Shamoon malware has re-emerged, including attacks against oil and gas companies in Italy and the Middle East, following a two-year absence.

Additionally, security researchers have found that this version of Shamoon includes a destructive data wiper that can delete files from infected systems before the malware fully removes all the data from the Master Boot Record.

The first attack appears to have targeted Saipem, an Italian oil company, which announced the incident on December 10. Since then, the company has continued to recover, finding about 300 PCs infected with the malware.

Later, researchers at Symantec issued a December 14 report that found additional Shamoon attacks that targeted organizations in Saudi Arabia and the United Arab Emirates.

In the case of the incident involving Saipem, researchers with Palo Alto Network's Unit42 found that the attack involved Disttrack malware -- another name for Shamoon -- and that the sample they examined contained similarities between this one and others that happened in 2016, which are sometimes called Shamoon 2.

It's through this examination that researchers found the new wiping capabilities.

"Unlike past Shamoon attacks, this particular Disttrack wiper would not overwrite files with an image. Instead it would overwrite the MBR [Master Boot Record], partitions, and files on the system with randomly generated data," according to the Unit42 analysis.

In this case, Disttrack acts as a dropper in order to infect a PC and install the data wiper onto the system. However, researchers also found that the malware also helps spread the attack throughout the network by using stolen usernames and passwords to log into other computers.

Researchers also noted that the malware sample contained a specific wipe date of "12/7/2017," which would appear to be a mistake by the group. However, it can still be effective: "This older date is still effective as the Disttrack dropper will install and run the wiper module as long as the system date is after the wipe date," according to the report.

In its analysis, Symantec researchers found that the group behind the attack usually gathers these credentials during a reconnaissance phase before the main attack. This list is then copied first to a file called OCLC.exe and then sent to another tool by the name or Spreader.exe. This sequence then copies all the malware to as many computers as possible.

Symantec has its own name for this part of the attack called the Filerase Trojan.

During the recent attack, Symantec noted that between the malware's ability to spread through the network, combined with the wipe capabilities, this particular attack is difficult to recover from once it starts.

"While a computer infected by Shamoon could be unusable, files on the hard disk may be forensically recoverable. However, if the files are first wiped by the Filerase malware, recovery becomes impossible," according to the company's analysis.

In the case of this most recent attack, Symantec noted that one company targeted by Shamoon had also been a victim of another piece of malware called Stonedrill, which is used by an Advanced Persistent Threat group (APT) called Elfin or APT33. It's possible the two are related but researchers could not draw a direct link as of yet.

From a historical perspective, researchers first noted Shamoon in 2012, when it attacked the network of Saudi Aramco -- the largest oil producer in Saudi Arabia -- infecting about 30,000 machines and stopping work at the company for some time.

Related posts:

— Scott Ferguson is the managing editor of Light Reading and the editor of Security Now. Follow him on Twitter @sferguson_LR.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Manchester United Suffers Cyberattack
Dark Reading Staff 11/23/2020
As 'Anywhere Work' Evolves, Security Will Be Key Challenge
Robert Lemos, Contributing Writer,  11/23/2020
Cloud Security Startup Lightspin Emerges From Stealth
Kelly Sheridan, Staff Editor, Dark Reading,  11/24/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-20934
PUBLISHED: 2020-11-28
An issue was discovered in the Linux kernel before 5.2.6. On NUMA systems, the Linux fair scheduler has a use-after-free in show_numa_stats() because NUMA fault statistics are inappropriately freed, aka CID-16d51a590a8c.
CVE-2020-29368
PUBLISHED: 2020-11-28
An issue was discovered in __split_huge_pmd in mm/huge_memory.c in the Linux kernel before 5.7.5. The copy-on-write implementation can grant unintended write access because of a race condition in a THP mapcount check, aka CID-c444eb564fb1.
CVE-2020-29369
PUBLISHED: 2020-11-28
An issue was discovered in mm/mmap.c in the Linux kernel before 5.7.11. There is a race condition between certain expand functions (expand_downwards and expand_upwards) and page-table free operations from an munmap call, aka CID-246c320a8cfe.
CVE-2020-29370
PUBLISHED: 2020-11-28
An issue was discovered in kmem_cache_alloc_bulk in mm/slub.c in the Linux kernel before 5.5.11. The slowpath lacks the required TID increment, aka CID-fd4d9c7d0c71.
CVE-2020-29371
PUBLISHED: 2020-11-28
An issue was discovered in romfs_dev_read in fs/romfs/storage.c in the Linux kernel before 5.8.4. Uninitialized memory leaks to userspace, aka CID-bcf85fcedfdd.