04:48 PM
Connect Directly

Shamoon Code 'Amateur' But Effective

Researchers drill down into Shamoon targeted malware and conclude it wasn't written by programmers as seasoned as those who created Stuxnet, Duqu, Flame

The data-destroying malware Shamoon -- which has been tied to the recent attacks on Saudi Aramco that took down 30,000 workstations at the massive oil company and possibly other Middle East targets -- contains some sloppy code riddled with errors, new research shows.

Shamoon was first revealed by Symantec last month as a destructive targeted attacked aimed at a Middle East energy firm in the wake of reports that Saudi Aramco had been hit by a massive malware attack. Neither Symantec, Kaspersky Lab, AlienVault, nor Saudi Aramco will officially confirm that Shamoon was indeed the attack on Saudi Aramco, but one industry source with knowledge of the attacks told Dark Reading it was.

What set Shamoon apart from other targeted attacks was its main goal: total annihilation of data, rather than spying or stealing information. It basically wipes files and data, and cripples the infected machine. Liam O Murchu, manager of North American operations for Symantec Security Technology & Response, said last month that this brand of malicious attack hadn't been seen in 10 years, with the exception of the recent attack on the Iranian oil ministry.

Researchers at Kaspersky Lab and AlienVault Labs have picked apart Shamoon and found that it's not the same caliber of code as Stuxnet or Flame. The authors appear to be amateurs -- determined ones at that -- who may have political hacktivist motives, thanks to the discovery of a partially obscured photo of a burning American flag used to hide some of the code.

"We've got other clues that people behind creating the Shamoon malware are not high-profile programmers, and the nature of their mistakes suggests that they are amateurs, albeit skillful amateurs, as they did create a quite practicable piece of self-replicating destructive malware," says Dmitry Tarakanov, Kaspersky Lab Expert, in a new blog post today.

Jaime Blasco, manager of AlienVault Labs, says that, overall, the code is rudimentary. "From a technical point of view, the code is quite simple," Blasco says. But whether the writers were amateurs or pros all depends on how you define a professional malware operation. "Of course, [Shamoon] is not close to the complexity of Stuxnet, Duqu, or Flame, but I've seen other targeted attacks using less complex malware than Shamoon. Sometimes the attackers just want to accomplish the objective, so they don't require complex code, just the code that works for the target," he says. "And in the case of Shamoon, it seems it was able to accomplish the mission."

The most sophisticated part of the code: how the attackers employed a legitimate, digitally signed driver inside. "The only part of the system that can be mentioned is that they used a benign third-party driver -- signed -- to overwrite the files on the systems," Blasco says. That driver was signed by EldoS Corp., which provides security-related software components for software developers and the corporate market.

Among the errors in the code pinpointed by Kaspersky Lab was in Shamoon's communication module, which included a typo in the format string of the code that precludes the malware from executing other programs. "This shows at least lack of testing," Kaspersky's Tarakanov told Dark Reading.

Another error he found was a flawed dates-comparison routine, he says. "[An] experienced programmer would be ashamed [of] himself to leave the comparison code in that state as it has been done in Shamoon. There are additional conditions which cover special cases, but don't resolve the task fully. It was visible that author tried to accomplish that mission, but failed and stopped when it worked in [a] special case," he says.

The coding errors could mean lack of experience or inattention indicative of a younger coder, he says.

The fragment of a photo of a burning U.S. flag was used to overwrite the content of the files on the infected machines, says Blasco, whose firm also released new information on the malware (PDF) this month. "This can be interpreted as a message if it is confirmed that Islamic groups are behind the attack. Three different hacking groups have claimed responsibility of the attack," including the Arab Youth Group and the Cutting Sword of Justice, he says.

Kaspersky's Tarakanov concurs. "The fact that they used a picture of a fragment of a burning U.S. flag possibly shows that the motive of Shamoon's authors is to create and use malware in a politically driven way. Moreover, they wished that their protest, which was embedded into the malware, would not go unnoticed," Tarakanov says.

But the fragmented photo of the flag could also have been "just for trolling," he told Dark Reading.

And Shamoon was no Wiper, the targeted malware aimed at taking down machines in Iranian businesses, according to Kaspersky Lab. "By all appearances, the Shamoon author/s encountered the same issue like The Wiper authors. In the modern world, it's time-consuming to fill an entire disk even with fixed data. To have the wiping done a bit quicker but efficiently, it is not necessary to wipe all the data but to rewrite parts dispersively throughout the disk. The Wiper authors completed this task fairly smartly, whereas in Shamoon it's done rather crudely," Tarakanov wrote.

[ Oil company's revelation matches counts by hackers claiming responsibility and Shamoon connection. See 30,000 Machines Infected In Targeted Attack On Saudi Aramco. ]

Meanwhile, Saudi Aramco yesterday released a press statement that its network is back up and running after the massive virus attack it suffered last month, and that the company has beefed up its network security systems as well as other security features in its environment. Saudi Aramco also repeated its previous comment that none of its oil and gas operations were interrupted or affected by the virus.

"The virus, which only affected personal workstations in the company, had no significant impact on the company's administrative operations or the productivity of its employees. This was achieved through restoring the affected workstations in a fast and effective manner and in time for employees returning to work after the 'Id holiday. Internal email services were also restored in a timely manner by the company's experts," the statement said.

Have a comment on this story? Please click "Add Your Comment" below. If you'd like to contact Dark Reading's editors directly, send us a message. Kelly Jackson Higgins is Executive Editor at 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

Comment  | 
Print  | 
More Insights
Newest First  |  Oldest First  |  Threaded View
13 Russians Indicted for Massive Operation to Sway US Election
Kelly Sheridan, Associate Editor, Dark Reading,  2/16/2018
Facebook Aims to Make Security More Social
Kelly Sheridan, Associate Editor, Dark Reading,  2/20/2018
From DevOps to DevSecOps: Structuring Communication for Better Security
Robert Hawk, Privacy & Security Lead at xMatters,  2/15/2018
Register for Dark Reading Newsletters
White Papers
Cartoon Contest
Current Issue
How to Cope with the IT Security Skills Shortage
Most enterprises don't have all the in-house skills they need to meet the rising threat from online attackers. Here are some tips on ways to beat the shortage.
Flash Poll
[Strategic Security Report] Navigating the Threat Intelligence Maze
[Strategic Security Report] Navigating the Threat Intelligence Maze
Most enterprises are using threat intel services, but many are still figuring out how to use the data they're collecting. In this Dark Reading survey we give you a look at what they're doing today - and where they hope to go.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
Published: 2017-05-09
NScript in mpengine in Microsoft Malware Protection Engine with Engine Version before 1.1.13704.0, as used in Windows Defender and other products, allows remote attackers to execute arbitrary code or cause a denial of service (type confusion and application crash) via crafted JavaScript code within ...

Published: 2017-05-08
unixsocket.c in lxterminal through 0.3.0 insecurely uses /tmp for a socket file, allowing a local user to cause a denial of service (preventing terminal launch), or possibly have other impact (bypassing terminal access control).

Published: 2017-05-08
A privilege escalation vulnerability in Brocade Fibre Channel SAN products running Brocade Fabric OS (FOS) releases earlier than v7.4.1d and v8.0.1b could allow an authenticated attacker to elevate the privileges of user accounts accessing the system via command line interface. With affected version...

Published: 2017-05-08
Improper checks for unusual or exceptional conditions in Brocade NetIron 05.8.00 and later releases up to and including 06.1.00, when the Management Module is continuously scanned on port 22, may allow attackers to cause a denial of service (crash and reload) of the management module.

Published: 2017-05-08
Nextcloud Server before 11.0.3 is vulnerable to an inadequate escaping leading to a XSS vulnerability in the search module. To be exploitable a user has to write or paste malicious content into the search dialogue.