The phone in my home office rang at 4AM this morning. It never rings at that time of the night. So half asleep, I had a look at the call display screen. The call was from India. Since I do have clients from India, I decided to answer it. The person on the other end was in a panic. They said that they got my number from someone who I had flown over there to help and that I came highly recommended.
If I wasn’t half asleep, I would have been flattered.
In any case, they explained their situation. One of their database servers was down. And it turned all their databases into .java files. That woke me up as I had a feeling I knew what was going on. I then requested to start a remote session using GoToAssist with the customer. Once I established the remote session, I started to poke around and I soon confirmed what I was thinking. They had been pwned by ransomware. The confirmation was this file that I found:

Basically, they had been pwned by a variant of the Dharma ransomware [Warning: PDF]. I say a variant because the version that I had previously seen encrypted things with a .Dharma extension. But according to this, the new variant that I was dealing with encrypted files with a .java extension. To make matters worse for the customer. He didn’t ever do backups of his databases, which were mission critical to his businesses.
#Fail. You should always backup your data. Especially if it’s mission critical.
The fortunate thing for this customer is that that there were ways to eliminate the files and possibly recover the data using file decryption software that was mentioned in the article. I then used the instructions to eradicate the virus by hand. I then confirmed that it was gone by scanning it with Trend Micro’s online scanner as the antivirus software that the server had wasn’t working. My next step was to use the file decryption software that was mentioned in the article to start encryption the databases. It took a while, but I was able to get them all back. I then was able to move them to a freshly built database server and make them accessible to the company.
Total time invested: 3.5 hours.
The thing is that this customer was VERY lucky. Ransomware attacks typically don’t have happy endings. The fact that it got in and it was able to do what it did indicates that they need a complete review of their IT security practices as clearly this ransomware was able to get in and pwn them. It could have been a human doing something dumb, or it could have come in via something like a PC that was exposed to the outside world. It could have even been a disgruntled employee. They also need to get into a backup regimen as the fact that they don’t backup mission critical data is a #fail. Thus I will be making arrangements to go there in a couple of months. But in meantime, I have some late nights and early mornings to look forward to as I plan on doing what I can from the other side of the planet.
Fun.
EXCLUSIVE: Linksys Rolling Out Firmware Fixes For WRT32X & WRT3200ACM
Posted in Commentary with tags Linksys on January 17, 2018 by itnerdI just got off the phone with representatives from Linksys who shared with me some news in relation to the WRT32X and WRT3200ACM issues that I’ve been writing about for the last month.
First, they shared with me the root cause analysis of the issues that these routers have had. One cause is this Google issue that I wrote about yesterday. But I want to add to what I wrote yesterday to say that the problems with things like Google Chromecasts and Google Home killing your WiFi also extends to Android phones. Why is this important? When I was trying to troubleshoot the WiFi issues with my WRT32X, I had a couple Android phones turned on and connected to WiFi. When they were turned off, I found that I had a much better WiFi experience than when I had them turned on. This was validated by the experiences of users who were on the Linksys Community. Now this confirmation, further validated by Google saying that they are issuing a fix for this behavior, explains what I was seeing.
However, Linksys isn’t waiting for Google to fix this. The beta firmware for the WRT32X and WRT3200ACM that I told you about this past weekend has a fix for this issue in it. Now I did mention that it was a beta, but I couldn’t find anything wrong with the WRT32X variant of this firmware. Thus I feel comfortable recommending that you install it. But if you don’t want to run beta firmware, which by the way is completely understandable, production firmware is either out or will be out soon. In the case of the WRT3200ACM, that firmware is live as of now. All you need do is turn on the auto update of your router and you’ll get it. One thing that I should note is that about 50% of WRT3200ACM routers that are in production have received this update already. The version for the WRT32X is coming very soon as it’s still in the QA process. But if you have a WRT32X, you may want to proactively turn on auto update to get this firmware when it appears as it should be out sometime over the next few days. When it does pop up, I’ll post an update on what my experiences with it are.
One other thing. To further ensure that nothing else that can be classified as “bad” happens. Such as the Google fix breaking something else, Linksys will be monitoring the situation and be doing additional validation on the Google fix to ensure all their users are happy. One thing that was stressed to me on the call with Linksys is they really want to do right by their users. That’s why you saw them handing out replacement product such as Velop whole home Wifi nodes to customers. WiFi is important to everyone everywhere and Linksys gets that.
In closing, I have an ask for anyone who has a WRT3200ACM or a WRT32X. When you get this firmware update, please leave a comment below with what it’s like as I think it’s important for people to share their feedback on this. Given the results that I saw with the beta, I suspect that users will be very happy once they get the production firmware on their routers. And I think that the world should know about that.
2 Comments »