WastedLocker Ransomware Piergiorgio Venuti

WastedLocker: Next generation ransomware

WastedLocker is ransomware attack software that began targeting businesses and other organizations in May 2020. It is known for its high ransom demands reaching millions of dollars per victim. It is the product of a group of highly skilled cyber criminals who have been operating for over a decade: Evil Corp.

Who is behind WastedLocker Ransomware

The group behind WastedLocker goes by the name of Evil Corp and some of the individuals associated with it have a long history in the world of cybercrime. The group is best known for managing the Dridex malware and botnet since 2011, but has also been responsible for creating ransomware programs over the years.

Through various episodes of criminal attacks, the group has been developing malware targeting mainly US companies since 2011. For this reason they have been known to the police for some time. After a period of inactivity, the group reappeared in January 2020 and their activity resumed as usual, with victims appearing in the same regions as before.

WastedLocker is a completely new program from Evil Corp that began infecting organizations in May 2020. It does not share the code with BitPaymer (a previously used software) but shows other similarities in the ransom note and per-victim customization. Evil Corp’s lack of activity between March and May could be explained by the group that was working on developing this new cyber threat as well as other tools that make up its toolset.

WastedLocker Hacker

How does it work

According to Symantec reports, the infection chain for WastedLocker starts with a JavaScript-based attack framework. The framework, called SocGholish, is distributed as a fake browser update from warnings displayed on legitimate but compromised websites. Hacked news websites are a common vector.

The SocGholish framework is distributed as a ZIP file. Once opened and executed, it initiates a chain of attacks that involves downloading and running PowerShell scripts and the Cobalt Strike backdoor. Evil Corp has used this same distribution technique in the past to distribute the Dridex Trojan, so it has been part of its arsenal for a long time.

Once hackers gain access to a computer, they begin distributing various tools to steal user credentials. In addition, they can also increase privileges and perform a lateral movement to other machines. The attackers’ goal is to identify and gain access to high-value systems such as servers. They then implement an ad hoc binary file on the compromised machines for the victims.

The use of manual hacking and system administration tools are part of a trend observed in recent years. According to this trend, cybercriminals are increasingly adopting attack techniques that in the past were associated with cyber espionage. This trend poses a serious problem for smaller organizations that lack the budget and IT resources to deploy defenses against advanced threats, but are a frequent target for ransomware groups and other financially motivated cybercriminals.

WestedLocker in detail

WastedLocker uses a combination of AES and RSA encryption in its encryption routine which is similar to other ransomware programs. Each file is encrypted with a unique 256-bit AES key generated on-the-fly. These AES keys along with other information about the encrypted files are then encrypted with a 4096-bit public RSA key which is encoded in the WastedLocker binary. Attackers keep the private part of the RSA key pair needed to retrieve AES keys and decrypt individual files.

According to an analysis by Kaspersky Lab, the encryption routine is strong and correctly implemented. So the victims cannot recover their files without the attacker’s private RSA key. Because it is a manually distributed ransomware threat customized to each target, attackers generate unique RSA key pairs for each victim. I mean, the key received from one organization after paying the ransom will not work to decrypt the files of another affected organization.

Some distinctive aspects of WastedLocker

The WastedLocker ransomware has a mechanism that allows attackers to prioritize certain directories during the encryption routine. This is probably used to ensure that the most important and valuable files are encrypted first in case the encryption process is detected by the system administrators and stopped while it is in progress.

The malware appends an extension to files consisting of the victim’s name and the word “wasted”. Also, it generates a text file with the ransom note for each file, which means that each directory will contain hundreds or thousands of copies of the ransom note.

WastedLocker is designed to delete shadow copies (the default backups made by the Windows operating system) and tries to encrypt files on the network, including remote backups.

After the July 2020 attacks

The Securonix Threat Research Team (STR) is actively investigating the details of Wastedlocker ransomware critical attacks. These have reportedly already affected more than 31 companies, of which 8 are Fortune 500 companies.

Impact

Here are the key details regarding the impact of WastedLocker ransomware attacks:

– WastedLocker ransomware is relatively new, used by EvilCorp, which previously used the Dridex trojan to distribute BitPaymer ransomware in attacks against government organizations and businesses in the US and Europe.

– Evil Corp group is currently focusing on targeted attacks on multiple industry casualties in recent months. Garmin is one of the latest high profile victims attacked (officially confirmed by Garmin on July 27).

– The most recent ransom amount requested was $10 million and appears to be based on the victim’s financial data. Based on the available details, the ransom has probably been paid.

– To date, a mono-extortion scheme appears to have been used, ie with only encryption and no or minimal data loss.

WastedLocker hacker

How to defend yourself

Following the analysis of the attacks and the data available, we want to suggest methods of mitigation and prevention of attacks.

– Review the backup retention policies. Make sure these are stored in a location that cannot be accessed / encrypted by the operator who placed the targeted ransomware. For example, consider write-only remote backup.

– Implement a training program on the safety of end users (company employees). Since end users are the targets of ransomware, it is best that they are aware of the current risks. It is important that they are aware of the threat of ransomware and how it occurs.

– Patches of infrastructure operating systems, software and firmware. Consider the possibility of leveraging a centralized patch management system.

– Maintain regular, air-gaped backups of critical company / infrastructure data. An air-gaped backup and recovery strategy means making sure that at least one copy of your organization’s data is offline and not accessible from any network.

– Implement security monitoring, particularly for high-value targets, to detect in advance any malicious ransomware operator positioning activity.

As always, we at Cyberfero are available for advice and to suggest you which services you can implement for the safety of your company. Contact us to find out how we can help you keep your business defenses high.

Useful links:

Share


RSS

More Articles…

Categories …

Tags

RSS feed: Unknown Feed Unknown Feed

RSS feed: Full Disclosure Full Disclosure

  • SEC Consult SA-20261104-0 :: Improper device certificate validation enables AiTM attacks in Siemens SICAM Toolbox II device communication November 5, 2026
    Posted by SEC Consult Vulnerability Lab via Fulldisclosure on Nov 04SEC Consult Vulnerability Lab Security Advisory < 20261104-0 > ======================================================================= title: Improper device certificate validation enables AiTM attacks product: Siemens SICAM Toolbox II device communication vulnerable version:
  • Apache Struts2 Tiles Plugin <=7.4.0 and >=6.3.0 Preparer Cache Vulnerabilities November 5, 2026
    Posted by Daniel Owens via Fulldisclosure on Nov 04The Apache Struts2 Tiles plugin version =6.3.0) codebase includes a `ViewPreparer` construct, replete with multiple ViewPreparer factories, that contains several important vulnerabilities including unsynchronised, unbounded caches. The lack of proper synchronisation means that certain factories will create caches that race, risking lost cache entries, corrupted internal bucket […]
  • unixODBC <=2.3.14 Rude Truncation via Narrowing Conversion Causes Out-of-Bounds `memcpy` November 5, 2026
    Posted by Daniel Owens via Fulldisclosure on Nov 04unixODBC versions
  • unixODBC <=2.3.14 Multiple Races November 5, 2026
    Posted by Daniel Owens via Fulldisclosure on Nov 04The unixODBC driver manager library contains multiple races of importance / interest, including a set of data races in the connection-pooling configuration state data that can cause one thread to read a half-written pool-size or timeout value, which can lead to a variety of harmful effects, as […]
  • unixODBC <=2.3.14 Multiple Heap Buffer Overflows, Underflows, and Over-Reads November 5, 2026
    Posted by Daniel Owens via Fulldisclosure on Nov 04unixODBC versions 2.3.14 and below contain multiple heap buffer overflows, underflows, and over-reads. Attackers who can influence various arguments passed thereto can trigger the heap-based buffer overflows inside of the unixODBC driver manager itself, potentially corrupting the shared heap state across connections, crash the driver manager (thereby […]
  • Apache Struts2 Core Arbitrary Code Execution via OGNL Sandbox Escape November 2, 2026
    Posted by Daniel Owens via Fulldisclosure on Nov 01Description Apache Struts2 Core version 7.4.0 and below attempt to prevent arbitrary code execution via Object-Graph Navigation Language (OGNL) through several different mechanisms but only in a cursory fashion -- the libraries only guard against immediate calls evaluated by the OGNL engine via `SecurityMemberAccess`, but an allowed […]
  • Apache Struts2 Core TokenHelper Token Cryptographic Timing Side-Channel November 2, 2026
    Posted by Daniel Owens via Fulldisclosure on Nov 01Description The Apache Struts2 Core 7.4.0 and below performs session token comparisons cryptographically insecure early-exit comparison functions (e.g., `!=`, `memcmp`, byte-by-byte loops with `break`) that return as soon as the first mismatched byte is encountered. The execution time of the comparison is therefore proportional to the number […]
  • Apache Struts2 Spring Plugin Uses a Previously Closed Resource November 2, 2026
    Posted by Daniel Owens via Fulldisclosure on Nov 01Description The Apache Struts2 Spring Plugin opens a Spring `ApplicationContex` via a try-with-resources block and, outside of said block, then continues to use the closed resource, resulting in an uncaught `IllegalStateException`. This particular issue prevents proper functionality and indicates poor code quality and code review standards and […]
  • Apache Struts2 Core Integer Overflow November 2, 2026
    Posted by Daniel Owens via Fulldisclosure on Nov 01Description Apache Struts2 Core version 7.4.0 and below fails to properly prevent integer overflows, causing wrap-arounds and other issues on a downstream forced casting into types smaller than `BigInteger`. Importantly, this finding underscores why all applications using Struts and other such platforms should perform their own input […]
  • Apache Struts2 Core Cross-Origin Protection Exemption Miskeyed to a Deployment-Wide Path November 2, 2026
    Posted by Daniel Owens via Fulldisclosure on Nov 01Description Apache Struts2 Core version 7.4.0 and below&apos;s `FetchMetadataInterceptor`, `CoepInterceptor`, and `CoopInterceptor` each compare their `exemptedPaths` configuration -- a per-interceptor-reference, administrator-supplied set of paths intended to exempt specific actions from the corresponding cross-origin protection -- against `HttpServletRequest.getContextPath()`. `getContextPath()` is fixed for the entire deployed web...

Customers