This morning, I decided I was going to write a post about shared hosting and the dangers involved in ceding control of much of your stack to hosting companies that may be very clueless when it comes to security, particularly a lot of me-too Nigerian shared hosting providers. That was 10 hours ago. Between that time and now, Whogohost has succeeded in making the post about them. Fine by me.
So here’s what happened. My friend @FatherMerry woke up to this email from a security firm.
We checked, and saw the files. In mindless haste, he deleted the folder without backing it up first. Which was not a problem, besides the fact that we didn’t get to see what the phishing website was all about. He replied the security firm to thank them for pointing this out and expressed genuine worry about how his hosting account got hacked in the first place.
Now this is where I would blame Ope a bit. He was using the default password he got after opening the account. Granted, it wasn’t “administrator” or “password”, but it was still an unchanged default nonetheless.
Still reeling from the fact that his account was compromised, we decided to go through the files on it and see which ones were updated recently. We ended up uncovering more folders, including one in the root called x.php
. Curious, we checked to see what it was from the browser and whoa:
I’m not an expert in being a victim to these things but this appeared like after compromising the account, they dropped a file that essentially became their own cPanel to the account, for easy upload and manipulation in the future even if passwords get changed. I don’t know but the capabilities of this one little file appear to be fueled by an exploit of cPanel or some other software on the hosting company’s end. Of course we deleted the file as well.
Being a good samaritan that he is, Ope decided to report the situation to Whogohost support because you know, they might want to check to be sure this is an isolated exploit and haven’t due to inaction, compromised accounts of other customers. Then the clock started ticking…
9 hours later, he was greeted with this:
Notice how this all reads without any form of empathy. Oh, and then he has to what? Purchase something called SiteLock? Then to crown it all, the threat to suspend his account. It’s almost as though they were the ones that uncovered the situation, except that the ones who really did and were directly affected by the attacks that followed were polite and reasonable about it.
Thoughts?