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.

Application Security //

Ransomware

5/26/2017
08:05 AM
Curtis Franklin
Curtis Franklin
Curt Franklin
50%
50%

New Insight on WannaCry's Roots

Is it possible we've been looking in the wrong direction for the source of the WannaCry attack?

Ever since news of the WannaCry attack broke, people have been searching for the culprits -- those responsible for the attack and from which evil lair the attacks were launched. Many fingers were pointed at Russia and eastern Europe -- but were those fingers pointed at the wrong target?

According to an article in Foreign Policy, those early fingers might have been pointed too far to the West. The article references researchers at Symantec and other anti-malware companies who found tell-tale electronic fingerprints on the attack -- fingerprints that would seem to belong to hackers in North Korea.

For years, security researchers have used digital "fingerprints," or snippets of code that tend to be unique to an individual programmer or group of programmers, to identify the source of attacks and vulnerability exploits. Over time, these researchers have found that this evidence that a particular programmer worked on a block of code tend to be persistent, no matter how many other hackers might touch the malware, because of the tendency to cut and paste rather than develop each attack from a clean sheet of paper.

The fingerprints on the WannaCry code indicate that it spent time in North Korea. What it doesn't really say, is whether the attack was launched, or ordered, by North Koreans. There are plenty of signs to indicate that the attack didn't come from a nation state: It didn't really raise very much money, and the feature that allowed a researcher to stop WannaCry in its tracks was rather crudely implemented.

Why does all this matter?

Because, like plant and animal DNA, the digital fingerprints on malware ultimately allow researchers to tell the story of where the software has been, how it's evolved, and how it's likely to be used in the future. All of that adds up to information that makes it possible to more effectively fight the malware and remediate the damage done, and ultimately, to point the finger of responsibility in the right direction.

— Curtis Franklin is the editor of SecurityNow.com. Follow him on Twitter @kg4gwa.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
News
Former CISA Director Chris Krebs Discusses Risk Management & Threat Intel
Kelly Sheridan, Staff Editor, Dark Reading,  2/23/2021
Edge-DRsplash-10-edge-articles
Security + Fraud Protection: Your One-Two Punch Against Cyberattacks
Joshua Goldfarb, Director of Product Management at F5,  2/23/2021
News
Cybercrime Groups More Prolific, Focus on Healthcare in 2020
Robert Lemos, Contributing Writer,  2/22/2021
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
Building the SOC of the Future
Building the SOC of the Future
Digital transformation, cloud-focused attacks, and a worldwide pandemic. The past year has changed the way business works and the way security teams operate. There is no going back.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-20327
PUBLISHED: 2021-02-25
A specific version of the Node.js mongodb-client-encryption module does not perform correct validation of the KMS server’s certificate. This vulnerability in combination with a privileged network position active MITM attack could result in interception of traffic between the Node....
CVE-2021-20328
PUBLISHED: 2021-02-25
Specific versions of the Java driver that support client-side field level encryption (CSFLE) fail to perform correct host name verification on the KMS server’s certificate. This vulnerability in combination with a privileged network position active MITM attack could result in inte...
CVE-2020-27543
PUBLISHED: 2021-02-25
The restify-paginate package 0.0.5 for Node.js allows remote attackers to cause a Denial-of-Service by omitting the HTTP Host header. A Restify-based web service would crash with an uncaught exception.
CVE-2020-23534
PUBLISHED: 2021-02-25
A server-side request forgery (SSRF) vulnerability in Upgrade.php of gopeak masterlab 2.1.5, via the 'source' parameter.
CVE-2021-27330
PUBLISHED: 2021-02-25
Triconsole Datepicker Calendar <3.77 is affected by cross-site scripting (XSS) in calendar_form.php. Attackers can read authentication cookies that are still active, which can be used to perform further attacks such as reading browser history, directory listings, and file contents.