June 8, 2015 By Douglas Bonderud 2 min read

New trends in malware are always a hot security topic, with experts trying to predict what might come next and determine how companies can best protect their assets. It’s unlikely, however, that anyone saw this coming: The author of the file-encrypting Locker ransomware has publicly apologized and provided the free decryption keys for any compromised files. While there’s no word on why the cybercriminal had a change of heart and decided to own up, it’s certainly an interesting security development. Has malware finally become so ubiquitous that to stay relevant malicious actors must display some kind of conscience?

Rise and Shine With Locker Ransomware

As noted by Network World, the Locker ransomware was a so-called “sleeper,” which lays dormant on user systems for weeks or even months after being offloaded by a Trojan.Downloader. On May 25, a command was sent to install Locker on all affected computers and then started scanning for files to encrypt — everything from .doc to .ppt, .jpg to .raw. Removable drives were also scanned and encrypted.

Once encryption was complete, users received a message saying that their files were no longer accessible; their return cost 0.1 bitcoin (around $24), which increased to 1 bitcoin after 72 hours. But on May 30, a post was made on Pastebin by “Poka BrightMinds,” stating that he or she authored the malware and was “very sorry about what happened.” The post claimed the malware was never intended for release, that all new infections had stopped and that on June 2 at midnight, all infected computers would be automatically decrypted — and that’s exactly what happened. But security researchers are now left wondering why.

Compassionate Criminal?

There are several lines of speculation when it comes to the Locker ransomware turnaround. Some experts suggested that the author had made enough money from the efforts and decided to quit while ahead, or that the creator ran afoul of law enforcement. CEO of KnowBe4 Stu Sjouwerman suggested the attack didn’t have the hallmarks of “an experienced cybercriminal” and postulated that the author might have been affiliated with an organized crime outfit, decided to go solo and then had the plan backfire.

The malware itself is a little more forgiving than similar encryption attacks. For instance, on the splash screen displayed after files are locked down, Locker stated that “you can still safely use your computer, no new files will be encrypted and no malware will be installed,” according to a post on KnowBe4. The author also told the truth about decryption: Infected computers were cleared, and keys were also provided for users who had already cleared the infection but still had locked files. The act and apology weren’t entirely noble, however, since the creator didn’t offer to return any stolen bitcoins, and it’s hard to believe that this kind of sleeper malware was simply designed as a thought experiment. There’s also the disturbing notion that the apology itself may be yet another trick. Did the automatic decrypt leave anything else behind? Perhaps another, even more subtle piece of malware?

Apparently, malware creators are human, too, and can suffer attacks of conscience. In the case of the Locker ransomware, users had files returned and computers cleared but were still out any bitcoins. Perhaps this marks the dawning of a “compassionate criminal” era in malware development — but apology or not, it comes with a cost.

More from

Unpacking the NIST cybersecurity framework 2.0

4 min read - The NIST cybersecurity framework (CSF) helps organizations improve risk management using common language that focuses on business drivers to enhance cybersecurity.NIST CSF 1.0 was released in February 2014, and version 1.1 in April 2018. In February 2024, NIST released its newest CSF iteration: 2.0. The journey to CSF 2.0 began with a request for information (RFI) in February 2022. Over the next two years, NIST engaged the cybersecurity community through analysis, workshops, comments and draft revision to refine existing standards…

What should Security Operations teams take away from the IBM X-Force 2024 Threat Intelligence Index?

3 min read - The IBM X-Force 2024 Threat Intelligence Index has been released. The headlines are in and among them are the fact that a global identity crisis is emerging. X-Force noted a 71% increase year-to-year in attacks using valid credentials.In this blog post, I’ll explore three cybersecurity recommendations from the Threat Intelligence Index, and define a checklist your Security Operations Center (SOC) should consider as you help your organization manage identity risk.The report identified six action items:Remove identity silosReduce the risk of…

Obtaining security clearance: Hurdles and requirements

3 min read - As security moves closer to the top of the operational priority list for private and public organizations, needing to obtain a security clearance for jobs is more commonplace. Security clearance is a prerequisite for a wide range of roles, especially those related to national security and defense.Obtaining that clearance, however, is far from simple. The process often involves scrutinizing one’s background, financial history and even personal character. Let’s briefly explore some of the hurdles, expectations and requirements of obtaining a…

Topic updates

Get email updates and stay ahead of the latest threats to the security landscape, thought leadership and research.
Subscribe today