{"id":18141,"date":"2022-02-02T11:12:01","date_gmt":"2022-02-02T19:12:01","guid":{"rendered":"https:\/\/www.palada.net\/index.php\/2022\/02\/02\/news-11874\/"},"modified":"2022-02-02T11:12:01","modified_gmt":"2022-02-02T19:12:01","slug":"news-11874","status":"publish","type":"post","link":"https:\/\/www.palada.net\/index.php\/2022\/02\/02\/news-11874\/","title":{"rendered":"[updated]QNAP update stops Deadbolt ransomware, annoys some users, starts debate"},"content":{"rendered":"

Credit to Author: Pieter Arntz| Date: Fri, 28 Jan 2022 16:32:41 +0000<\/strong><\/p>\n

Earlier this week (25 January, 2022) news broke that a ransomware group was targeting QNAP Network Attached Storage<\/a> (NAS) devices. The threat actors claimed the attack was based on a zero-day vulnerability specific to the devices.<\/p>\n

Today QNAP\u00ae Systems, Inc. (QNAP) pushed out an automatic, forced, update with firmware containing the latest security updates to protect against the attackers’ “DeadBolt” ransomware.<\/p>\n

You might think that that is a good thing\u2014if not exactly cause for celebration, at least a cause for relief\u2014but some customers aren’t happy.<\/p>\n

Deadbolt<\/h3>\n

The ransomware group responsible for this attack is calling themselves Deadbolt. They also use the same name in the file extension of the encrypted files their ransomware generates. Rather then using the habitual method of dropping ransom notes in each folder on a affected device, Deadbolt ransomware hijacks the QNAP device’s login page. The hijacked screen starts with “WARNING: Your files have been locked by DeadBolt”. The complete ransom message is shown below:<\/p>\n

WARNING: YOUR FILES HAVE BEEN LOCKED BY DEADBOLT  ? What happened?  All your files have been encrypted. This includes (but is not limited to) Photos, Documents and Spreadsheets.  ? Why me?  This is not a personal] attack. You have been targeted because of the inadequate security provided by your vendor (QNAP).  ? What now?  You can sake a paywent of (exactly) 0.030000 bitcoin to the following address: \u25a0\u25a0\u25a0\u25a0\u25a0\u25a0\u25a0\u25a0\u25a0\u25a0\u25a0\u25a0\u25a0\u25a0\u25a0\u25a0\u25a0\u25a0\u25a0\u25a0\u25a0\u25a0\u25a0\u25a0\u25a0\u25a0\u25a0\u25a0\u25a0\u25a0\u25a0\u25a0\u25a0\u25a0  Once the payment has been made we'll follow up with a transaction to the same address, this transaction will include the decryption key as part of the transaction details.[more information]  You can enter the decryption key below to start the decryption process and get access to all your files again.  important message for QNAP<\/pre>\n
Reportedly, the ransomware has already affected at least 3,600 victims<\/a>. Besides urging individual victims to pay for a decryption key, the ransomware gang is also trying to sell the full details of the alleged zero-day vulnerability to QNAP for five bitcoins, and is apparently also willing to sell QNAP the master decryption key that can decrypt the files for all affected victims, and the zero-day info, for 50 bitcoins. There are many good reasons for not giving in to  ransomware gangs’ demands, and QNAP doesn’t need the zero-day information because it has already created an update to thwart the vulnerability. However, the update hasn’t been as welcome as you might expect. <\/p>\n
Forced update<\/h3>\n
The day after the news broke (26 January) QNAP issued a statement<\/a> in response to the ransomware. It urged NAS users to follow the recommended security setting instructions to ensure the security of their routers, and immediately update to the latest version of QTS\u2014the Linux based operating system developed by QNAP to run on their devices.<\/p>\n
Later that day, QNAP took more drastic action and force-updated the firmware for all customers’ NAS devices to version 5.0.0.1891, the latest universal firmware which has been available since December 23rd, 2021.<\/p>\n
Problems<\/h3>\n
As you might expect after a forced update, a number of unexpected side-effects arose, making users that were affected by these problems unhappy.<\/p>\n
Some users reporteded losing their devices’ ISCSI connections (ISCSI is a networking standard for linking data storage facilities), and some adaperts were apparently left disabled by the update. The firmware update removed the ransomware executable and the ransom screen used to initiate decryption, which apparently caused some victims who had paid the ransom to be unable to proceed with decrypting the files after the update.<\/p>\n
When warnings alone are not enough<\/h3>\n
As we all know, there is often a lawning gap between when a patch becomes available and when it’s actually applied. In this case, QNAP seems to have decided that closing that gap is the lesser of two evils.<\/p>\n
And in all fairness, QNAP has been urging users to secure their devices<\/a> since 7 January, 2022, with elaborate instructions on how to check whether their NAS devices are exposed to the Internet, how to disable the Port Forwarding function of the router, and how to disable the UPnP function.<\/p>\n
This is just good advice either way since QNAP NAS owners were already being targeted by other ransomware operations like Qlocker and eCh0raix<\/a>. Rather ironic, since many NAS owners use their devices to store backups in case their main systems become dislabed by things like ransomware.<\/p>\n
In response to criticism<\/a> about the unannounced forced update, QNAP support stated:<\/p>\n
\n
\u201cI know there are arguments both ways as to whether or not we should do this. It is a hard decision to make. But it is because of deadbolt and our desire to stop this attack as soon as possible that we did this.\u201d<\/p>\n<\/blockquote>\n
We are curious as to how our readers feel about this. Let us know in the comments. Should device vendors be allowed to push updates when there is a clear and imminent danger?<\/p>\n
Unless both business and conusmer users get to grips with patching sooner, we can probably expect to see more of these kind of forced updates.<\/p>\n
Update February 1, 2022<\/h2>\n
Today QNAP explained<\/a> how it was able to update systems of which the owners were convinced they had disabled the auto update<\/strong> setting. QNAP actively updates NAS system software to ensure that each of their products runs efficiently throughout every stage of its lifecycle. These updates include feature updates, bug fixes, and security patches.\u00a0<\/p>\n
To allow users to obtain the latest version of system software more easily, QNAP has introduced the auto update to \u201cLatest Version\u201d feature in QTS 4.5.0 \/ QuTS hero h4.5.0. Further, an auto update to “Recommended Version” feature is implemented in QTS 4.5.3 \/ QuTS hero h4.5.3 to give users more flexibility.<\/p>\n
Users that disabled the auto-update<\/strong> after installing 4.5.0 which introduced the option to auto-update, but before installing 4.5.3 which introduced recommended updates<\/strong> may find that their device will still auto-update the recommended updates. The update intended to mitigate and isolate the Deadbolt attack was pushed as a recommended update.<\/p>\n
The post [updated]QNAP update stops Deadbolt ransomware, annoys some users, starts debate<\/a> appeared first on Malwarebytes Labs<\/a>.<\/p>\n
https:\/\/blog.malwarebytes.com\/feed\/<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"
Credit to Author: Pieter Arntz| Date: Fri, 28 Jan 2022 16:32:41 +0000<\/strong><\/p>\n\n\n\n
<\/a><\/td>\n<\/tr>\n
After several warnings to their user and thousands of victims, QNAP pushed out a forced update to their NAS devices.<\/p>\n
Categories: Ransomware<\/a><\/p>\n
Tags: deadbolt<\/a>forced update<\/a>icsci<\/a>nas<\/a>qnap<\/a>ransomware<\/a><\/p>\n\n\n
\n
(Read more…<\/a>)<\/b><\/p>\n<\/td>\n<\/tr>\n<\/table>\n<\/td>\n<\/tr>\n<\/table>\n
The post [updated]QNAP update stops Deadbolt ransomware, annoys some users, starts debate<\/a> appeared first on Malwarebytes Labs<\/a>.<\/p>\n","protected":false},"author":4,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"colormag_page_container_layout":"default_layout","colormag_page_sidebar_layout":"default_layout","footnotes":""},"categories":[10488,10378],"tags":[24751,24752,24753,16919,18557,3765],"class_list":["post-18141","post","type-post","status-publish","format-standard","hentry","category-malwarebytes","category-security","tag-deadbolt","tag-forced-update","tag-icsci","tag-nas","tag-qnap","tag-ransomware"],"_links":{"self":[{"href":"https:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/posts\/18141","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/comments?post=18141"}],"version-history":[{"count":0,"href":"https:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/posts\/18141\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/media?parent=18141"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/categories?post=18141"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/tags?post=18141"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}