By using this site, you agree to the Privacy Policy and Terms of Use.
Accept
Security Parrot - Cyber Security News, Insights and ReviewsSecurity Parrot - Cyber Security News, Insights and Reviews
Notification
Latest News
OpenAI may use Associated Press archive for AI training
July 14, 2023
EU users can hold conversations with Google Bard from training set
July 14, 2023
Aptos, the new default font for Microsoft Office
July 14, 2023
BlackLotus UEFI bootkit sources published on GitHub
July 14, 2023
Hackers from the XDSpy cyber-espionage group attacked Russian organizations on behalf of the Ministry of Emergency Situations
July 14, 2023
Aa
  • News
  • Tutorials
  • Security InsiderComing Soon
  • Expert InsightComing Soon
Reading: Babuk decryptor not working and corrupting victims’ data
Share
Security Parrot - Cyber Security News, Insights and ReviewsSecurity Parrot - Cyber Security News, Insights and Reviews
Aa
Search
  • News
  • Tutorials
  • Security InsiderComing Soon
  • Expert InsightComing Soon
Follow US
Security Parrot - Cyber Security News, Insights and Reviews > News > Babuk decryptor not working and corrupting victims’ data
code-background
News

Babuk decryptor not working and corrupting victims’ data

Last updated: 2021/07/30 at 4:25 PM
Jim Koohyar Biniyaz Published July 30, 2021
Share
code-background
SHARE

McAfee experts released a report on Babuk ransomware, in which they concluded that attempts to make the malware cross-platform and use it against Linux / UNIX and ESXi or VMware have failed.

Let me remind you that at the beginning of the year, the creators of Babuk reported that they had developed a version of the ransomware for * nix, since many backends in large companies do not run under Windows at all. However, according to the researchers, the ransomware was written with many errors that “led to irreversible data corruption.”

“It looks like Babuk ran a live beta test on its victims when it came to developing the Golang binary and decoder. We observed that several victims’ machines were encrypted without the possibility of data recovery due to a faulty binary and a faulty decryptor, ”write the McAfee experts.

Thus, even if the victim agrees to pay the ransom to the hackers, it will not be possible to decrypt the affected files. Experts hope that this will ultimately affect the relationship of Babuk developers with “partners” who are directly involved in attacks and infect networks of victims with malware. If victims cannot get their data back even after paying the ransom, their grievances will turn to Babuk’s “partners”.

Since destroying data instead of encrypting it is less profitable from the point of view of criminals, experts believe that it was the complete inoperability of the * nix version of Babuk and the decryptor that forced hackers to switch to data theft and extortion, abandoning encryption.

Let me remind you that earlier this year, Babuk’s operators announced  that they were shutting down (after a  loud attack  on the Washington police department). It is believed that the hackers renamed their “leak site” to Payload.bin, and were ready to provide it to other criminals as a third-party hosting, where someone’s files can be leaked without starting their own site for this purpose, as well as as a platform on which ransomware, access brokers and other criminals will be able to “meet”. Indeed, recently, almost all major hack forums have  banned  any discussion related to ransomware and ransomware. However, things do n’t seem to be going well for the group., and the forum was unable to gain popularity, but was subjected to DDoS attacks and suffered from various bugs.

As for the failed Babuk decryptor, the researchers tell the following about it:

“In general, the decryptor is bad because it only looks for the .babyk extension and skips any files the victim might have renamed in an attempt to recover them. In addition, the decryptor checks if the file is larger than 32 bytes, since the last 32 bytes are later combined with other hard-coded values ​​to obtain the key. This is bad design, because those 32 bytes might be garbage, not a key. “

Weekly Updates For Our Loyal Readers!

Jim Koohyar Biniyaz July 30, 2021
Share this Article
Facebook Twitter Email Copy Link Print

Archives

  • July 2023
  • June 2023
  • May 2023
  • April 2023
  • February 2023
  • October 2022
  • September 2022
  • August 2022
  • July 2022
  • June 2022
  • May 2022
  • April 2022
  • March 2022
  • February 2022
  • January 2022
  • December 2021
  • November 2021
  • October 2021
  • September 2021
  • August 2021
  • July 2021
  • June 2021
  • May 2021
  • April 2021
  • March 2021
  • February 2021
  • January 2021
  • December 2020
  • November 2020
  • October 2020
  • September 2020
  • August 2020
  • July 2020

You Might Also Like

News

OpenAI may use Associated Press archive for AI training

July 14, 2023
News

EU users can hold conversations with Google Bard from training set

July 14, 2023
News

Aptos, the new default font for Microsoft Office

July 14, 2023
News

BlackLotus UEFI bootkit sources published on GitHub

July 14, 2023

© 2022 Parrot Media Network. All Rights Reserved.

  • Home
  • Parrot Media Group
  • Privacy Policy
  • Terms and Conditions
Join Us!

Subscribe to our newsletter and never miss our latest news, podcasts etc..

Zero spam, Unsubscribe at any time.

Removed from reading list

Undo
Go to mobile version
Welcome Back!

Sign in to your account

Lost your password?