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.

Endpoint

5/20/2016
03:00 PM
Connect Directly
Twitter
LinkedIn
RSS
E-Mail
50%
50%

TeslaCrypt Ransomware Group Pulls Plug, Releases Decrypt Key

But don't be surprised if group revives campaign or launches another one, security researchers say.

The somewhat surprising move this week by the operators of the TeslaCrypt ransomware sample, to cease operations and publicly release the universal master decryption key for it, is good news for victims of the malware.

It now means that they have a way to unlock data that might have been encrypted by TeslaCrypt. But the move, welcome as it is, doesn't necessarily mean that the group won’t simply release another sample or start afresh with a new malware campaign altogether, security researchers warned.

Slovakia-based ESET, which has been tracking TeslaCrypt for the past several months, recently noticed an announcement from the group behind the malware of its decision to cease operations. A security researcher at ESET reached out anonymously to the group via its support channel for victims, and asked for the master decryption key. “Surprisingly, they made it public,” the company announced on its blog.

ESET has released a free decryption tool based on the master key that it says can unlock files that were encrypted by any variant of TeslaCrypt. The company has provided instructions on how to use the tool at its ESET Knowledgebase website.

In comments to Dark Reading, ESET security researcher Lysa Myers says it’s unclear what prompted the change of heart within the TeslaCrypt group. “While it’s possible that the authors felt remorse, it’s also possible that they’ve decided to shut down this codebase in favor of starting fresh,” she says.

At the same time though, it does not necessarily mean that the group has suddenly decided to give up writing malware or even that they have abandoned ransomware campaigns, she cautions.

Similar things have happened in the past, she says. As one example, Myers pointed to an incident last year where someone purporting to be the creator of the Locky ransomware sample, apologized for activating the tool and publicly released a decryption key for the malware on PasteBin. Interestingly enough, a year later, Locky continues to be active and is actually the most widely distributed ransomware sample in circulation.

Importantly, releasing the master decryption key does not mean the threat actors behind TeslaCrypt have abandoned malware altogether.

“The most likely scenario is that authors could start fresh with a new codebase, learning from their previous efforts, and then begin infecting people again,” Myers says. “People who were previously infected with the older variant would be an obvious target, as they’ve [shown themselves] to be vulnerable.”

Engin Kirda, co-founder and chief architect
 at cybersecurity firm Lastline says that without direct information from the group behind TeslaCrypt, it is only possible to speculate on their motives.

“In reality, it could be anything,” he says. “It might be that they are moving to a new, illegal online business, or it might be because they are concerned that the authorities have some concrete evidence against them.”

According to Kirda, the mere fact that the master key was publicly released does not mean that TeslaCrypt’s operators cannot resume their operations using new keys and new infectors. “Typically, it is easy to shut down an operation by malware authors, and just as easy to restart it.”

It is also possible that the TeslaCrypt group could start using multiple encryption keys for locking data, so while some data can be released other data might remained encrypted.

“Whatever happens is only limited by the imagination of the malware authors and what they really plan to do,” Kirda says. “We have also seen cases in the past where malware authors have done things just to have fun with security professional such as choosing easily guessable passwords and providing wrong information.”

Related stories:

Jai Vijayan is a seasoned technology reporter with over 20 years of experience in IT trade journalism. He was most recently a Senior Editor at Computerworld, where he covered information security and data privacy issues for the publication. Over the course of his 20-year ... View Full Bio
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
RyanSepe
100%
0%
RyanSepe,
User Rank: Ninja
5/23/2016 | 8:56:07 AM
Surprised
As the article denotes, I would also be very surprised if a new strain or revised strain does not surface from this group. TeslaCrypt has been one of the more prevalent ransomware variants and the yield has been quite lucrative. For these reasons I foresee another recurrence.
clark1clark1
100%
0%
clark1clark1,
User Rank: Strategist
5/22/2016 | 12:14:25 AM
WTF
Talos, the intelligence wing of Cisco, has had a decryption tool for this for a couple of months now.  Please see the link to their blog.

(url got blocked) just search teslacrypt and talos. damn I hate this site.

 

I'm not sure if this release by telsacrypt is for something newer but its worth checking out and updating the article.  It may be a motivator for them if its already out in the security community.

 

Let us know if its relevant.

 

-Austin

 
News
Inside the Ransomware Campaigns Targeting Exchange Servers
Kelly Sheridan, Staff Editor, Dark Reading,  4/2/2021
Commentary
Beyond MITRE ATT&CK: The Case for a New Cyber Kill Chain
Rik Turner, Principal Analyst, Infrastructure Solutions, Omdia,  3/30/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
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
How Enterprises are Developing Secure Applications
How Enterprises are Developing Secure Applications
Recent breaches of third-party apps are driving many organizations to think harder about the security of their off-the-shelf software as they continue to move left in secure software development practices.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2015-20001
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.2.0, BinaryHeap is not panic-safe. The binary heap is left in an inconsistent state when the comparison of generic elements inside sift_up or sift_down_range panics. This bug leads to a drop of zeroed memory as an arbitrary type, which can result in a memory ...
CVE-2020-36317
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.49.0, String::retain() function has a panic safety problem. It allows creation of a non-UTF-8 Rust string when the provided closure panics. This bug could result in a memory safety violation when other string APIs assume that UTF-8 encoding is used on the sam...
CVE-2020-36318
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.49.0, VecDeque::make_contiguous has a bug that pops the same element more than once under certain condition. This bug could result in a use-after-free or double free.
CVE-2021-28875
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.50.0, read_to_end() does not validate the return value from Read in an unsafe context. This bug could lead to a buffer overflow.
CVE-2021-28876
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.52.0, the Zip implementation has a panic safety issue. It calls __iterator_get_unchecked() more than once for the same index when the underlying iterator panics (in certain conditions). This bug could lead to a memory safety violation due to an unmet safety r...