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.

Attacks/Breaches

3/6/2020
05:30 PM
Connect Directly
Twitter
LinkedIn
RSS
E-Mail
100%
0%

New Ransomware Variant Developed Entirely as Shellcode

PwndLocker is harder to detect than other crypto-malware, Crypsis Group says.

Researchers have discovered a new ransomware variant that they say has significantly different behavior and characteristics than most other ransomware types.

The ransomware, called PwndLocker, was found by The Crypsis Group in February during a client engagement. Subsequent analysis showed it was developed entirely as shellcode—something that malware authors have traditionally reserved for more specialized purposes.

The malware also implemented a custom encryption algorithm that the researchers discovered was potentially breakable, and in fact has already been broken. However, according to Crypsis, the malware authors can easily swap out the existing encryption algorithm with a stronger one at any time.

Matt Thaxton, senior consultant with The Crypsis Group, says PwndLocker's use of shellcode - or location-independent code - makes it a more complex and harder-to-spot ransomware variant than others. "The reason these types of code are harder for automated tools to spot is because they usually don't reside on disk and because they are often injected into other legitimate processes such as native, signed Windows-processes," he says.

Shellcode can sometimes be classified as fileless malware. But in the case of PwndLocker, it wouldn't be classified as fileless because it loads from a fake avi file, Thaxton noted.

Many exploits use shellcode to force vulnerable legitimate processes to use or to run illegitimate code. But typically malware authors have used shellcode only in secondary malware downloaders and sophisticated implants because of how complex and time-consuming it can be to create and implement such code. This is the first time, however, that ransomware has been developed using shellcode, Thaxton says.

"I'm not sure why this threat actor decided to write their ransomware in this way," he says. "My only guess would be that they wanted it to be very unique so that it is harder to spot through the usual [methods]." Also, it is possible that the malware authors wanted to be distinctive simply for the sake of differentiating from other variants.

Another noteworthy feature with PwndLocker is its use of a relatively weak custom-developed encryption algorithm rather than the more robust Windows crypto API, Thaxton notes. There's no real reason why they couldn't have just used the API like almost every other ransomware in the wild currently does, he says. "There may have been a reason for creating it this way that is yet to be determined. But at this point, it's not clear," Thaxton says.

In an alert Friday, security vendor Emsisoft said it has developed a way to decrypt files that PwndLocker might have encrypted. However, each decryptor requires customization before use. That means that victims of PwndLocker who want their files decrypted will need to send the ransomware executable that was used in the particular attack, Emsisoft said. "While the ransomware automatically deletes the executable, it is often possible to recover it using file recovery tools," the vendor said.

According to Emsisoft, PwndLocker has been observed mainly targeting business and government organizations and demanding ransom of more than $500,000. The malware has numerous variants, all of which are designed to delete shadow copies of data, which makes recovery harder.

"There is always going to be a mix of old and new ransomware variants as threat actors work to gain fast cash or put their unique stamp on an evolving threat landscape," Thaxton says. "Enterprises can't 'guess' what is going to come next."

The best approach is to adhere to best practices across the enterprise, and pay attention to end-user training within the security program, he says.

Related Content:

Check out The Edge, Dark Reading's new section for features, threat data, and in-depth perspectives. Today's featured story: "The Perfect Travel Security Policy for a Globe-Trotting Laptop."

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
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-2021-27905
PUBLISHED: 2021-04-13
The ReplicationHandler (normally registered at "/replication" under a Solr core) in Apache Solr has a "masterUrl" (also "leaderUrl" alias) parameter that is used to designate another ReplicationHandler on another Solr core to replicate index data into the local core. To...
CVE-2021-29262
PUBLISHED: 2021-04-13
When starting Apache Solr versions prior to 8.8.2, configured with the SaslZkACLProvider or VMParamsAllAndReadonlyDigestZkACLProvider and no existing security.json znode, if the optional read-only user is configured then Solr would not treat that node as a sensitive path and would allow it to be rea...
CVE-2021-29425
PUBLISHED: 2021-04-13
In Apache Commons IO before 2.7, When invoking the method FileNameUtils.normalize with an improper input string, like "//../foo", or "\\..\foo", the result would be the same value, thus possibly providing access to files in the parent directory, but not further above (thus "...
CVE-2021-29943
PUBLISHED: 2021-04-13
When using ConfigurableInternodeAuthHadoopPlugin for authentication, Apache Solr versions prior to 8.8.2 would forward/proxy distributed requests using server credentials instead of original client credentials. This would result in incorrect authorization resolution on the receiving hosts.
CVE-2021-28938
PUBLISHED: 2021-04-13
Siren Federate before 6.8.14-10.3.9, 6.9.x through 7.6.x before 7.6.2-20.2, 7.7.x through 7.9.x before 7.9.3-21.6, 7.10.x before 7.10.2-22.2, and 7.11.x before 7.11.2-23.0 can leak user information across thread contexts. This occurs in opportunistic circumstances when there is concurrent query exec...