On Sunday we reported that a number of sites hosted by Bluehost had been hacked (including their CEO’s blog).
On Monday while browsing through some of their forums, we noticed a thread regarding the exploit with remarks from forum moderators and administrators to curious customers that didn’t quite make sense.
#1 from one moderator:
Since such a negligible percentage of Bluehost sites were hacked it is just about guaranteed that it is an individual script issue rather than anything more widespread.
If it were something other than individual scripts being vulnerable then a lot more than 0.00006% of accounts would be affected.
It would be interesting to learn what Bluehost considers a negligible percentage for something like this. We’re also curious to learn more about how the .00006 percentage was determined. More on the numbers we calculated included below.
No matter how you look at this, there is a “script” causing problems for various people across the Bluehost service.
#2 from a bluehost system admin:
Bluehost is looking into it, yes, and the article referenced claiming “a good number of sites hosted at Bluehost have been hacked and infected” is very misleading. What is considered “a good number”? Less than 0.00006% of the domains we host actually show this compromise, which is much lower than most of the wordpress compromises we usually see, which is the cost of allowing people to run whatever they want on their site.
According to Bluehost, only .00006% of their customer sites were exploited. Even using their “NOW HOSTING OVER *1,000,000 DOMAINS” as a baseline, that would be less than 1 site infected.
Based on the infected sites we found and Bluehost’s advertised user count, we found that at least .03% of their client base has been affected. Now, you may say that is a small number, and we would agree, but that’s still hundreds of sites infected and serving malware on your network with no root cause for how the script propagated.
*According to Google, Bluehost has around 250k indexed sites in their network. If this in fact is a more accurate count of active sites they host, the percentage of infected sites is a lot higher than what we’ve estimated.
We replied to them on their forum and talked to the numbers a bit:
Hey,
I don’t think the numbers are so small as mentioned. Even Bluehost’s CEO blog got hacked…
We (during our initial assessment) found more than 140 sites hosted at Bluehost with this malware. Note that we don’t have access to all sites hosted in there to do a complete check, so it is probably a LOT more than that.
Google says bluehost have 240k sites (they claim over 1 million). With just those 140 sites we found, it would be at minimum 0.01% of the sites infected.
We fixed already a few sites in there, some were using WordPress, some Joomla, so it doesn’t look like anything that you can blame the user.
*just trying to clear the facts.
Only to get bashed and banned from their forum by an admin. Was our comment outside of the forum acceptable use policy?
ok, posts like this just create FUD and confuse people.
Consider that Sucuri did NOT contact bluehost about what they are seeing before they went public, before they attempted a grand stand and a “look at how good we are, come buy our product”, I would take what they say with a grain of salt and think about the reason they are doing and saying what they are. Real and honest security groups will always try to get a situation resolved and fixed by working with the victims before they show it to the world. Look at the motivations involved.
Bluehost cares a lot about it’s customers, we are looking into the issue, and will do whatever we can for our customers.
We reached out to Bluehost via LinkedIn about the exploits we discovered. We stated we would be releasing an article about the discovery, and that various other sites hosted by Bluehost had been affected.
We are a business that finds malicious issues on the internet, and tries to fix them as soon as possible. If you want to call that a grand stand, that’s your right, but don’t down talk us or our product without better research and understanding of how we help people when providers fail to provide adequate assistance to their customers. Get your ducks in a row.
Our service pointed out an exploit we discovered on Bluehost accounts, including the CEO’s blog, only to have them question our honesty and intentions, then ban us from their forum. Very Interesting posture from one of their senior leaders.
This isn’t a matter of disclosing some obscure vulnerability that hadn’t already been exploited, in fact, to recap, Bluehost has admitted that some percentage of their customers had already been exploited.
We’re doing our part to assist and have offered up a free clean-up script to those affected.
Check out some of the comments on our original article.
Bluehost has historically offered a great service, and we’re sure they truly care about their customers. We’d like to learn more about how they typically handle situations like this. In the end, we wonder what valid information they’re disclosing to those who own a site in the “negligible percentage of Bluehost sites” that were exploited.
Update 1: This is a poor response from Bluehost regarding this security problem. Clients are calling them to ask about this attack and their support personal are saying that nothing happened and it is probably an isolated incident. Someone sent them a link to our site and they responded that our article is a lie.
We have numbers to prove and a list of sites affected. We can send upon request.
Bluehost: some sites got reinfected today, including your CEO blog (which is currently down). Why not step up and take responsibility? This is not a small incident, since the number of affected sites are in the thousands now.
If you are a Bluehost client, call them up and ask for an answer.
If you have any questions about this article, the “domainameat” script issue, or just want to say hello, feel free to leave a comment below, or email us at support@sucuri.net.
Protect your interwebs,
Dre Armeda
Co-Founder
Sucuri.net







![Malware comes in many different varieties. Analyst Krasimir Konov is on this month’s Sucuri Sit-Down to help keep them all straight. From malicious iframes to SEO spam, join host Justin Channell as he racks Krasimir’s brain on all the different types of malware. Also, Krasimir discusses his recent blog post about a malicious cURL downloader, and Justin breaks down the latest website security news, including patched plugins you should update. Podcast Transcript Justin Channell: Hello, and welcome to the Sucuri Sit Down. I'm your host, Justin Channell, and this is a monthly podcast about website security, where we get in-depth with the malware removal experts here at Sucuri. Later in the show, I'll have our analyst Krasimir Konov to chat about some different types of malware, but first, let's take a look at other topics we've published on our blog and Sucuri labs notes this month. First up, we have some new information about credit card skimming with hackers using a hybrid method to steal payment information from eCommerce websites. Our analyst Dennis Sinegubko wrote about this for the Sucuri blog back at the beginning of June. Now, most credit card stealing malware is a client side JavaScript that grabs data and sends it to a third party server. But, that approach has a drawback for bad actors because it's still possible to track the requests and catch them as being suspicious. Now, to get around that, bad actors have started harvesting information server side by modifying core PHP files. In this case, the infection would be undetectable from the outside, but it's still going to be pretty easy to find because you're rarely modifying any of those core files, so any of those changes that are going to come up are going to be suspicious. To get around both of these drawbacks, we're seeing bad actors combine the two. So client side snippets of JavaScript are sending stolen credit card data to server side scripts that they've installed on the same server as the site. Now, this allows bad actors to cover their tracks a little bit because the traffic that's being redirected is going to the same server, and that's less likely to be flagged as suspicious. It's a bit more complicated to pull this off, but our team has been seeing this hybrid approach in the wild, so it's something to be on the lookout for. Now, another month has passed, and we found more cross site scripting attacks targeting WordPress plugins. Most notably, we discovered one that affects users of the YITH WooCommerce Ajax Product Filter plugin. Now, this is a plugin that allows WooCommerce stores to be filtered by product type, and it's pretty popular. It's got about 100,000 users right now, so with it being vulnerable, it's very important that all of them update to the latest version, which is 3.11.1. Some of the other plugins we found cross site scripting vulnerabilities with included Elementor Page Builder, Careerfy, JobSearch, and Newspaper. If you're looking for a full list of vulnerabilities that have been patched this month, John Castro at the Sucuri Labs blog has you covered. Check out our show notes for the link. Also, this month I had a blog go up detailing what's called a jibberish hack. It's basically the same motivation as an SEO spam attack where bad actors use your site's good standing to redirect visitors to their own sites. But in this attack, you'll find a bunch of randomly named folders filled with a ton of HTML files with really nonsensical file names like cheap-cool-hairstyles-photos.html. It's just going to be a mishmash of keywords that clearly you didn't put there. Unfortunately, just deleting all those HTML files and folders is not going to be enough to get rid of that jibberish hack though. You're going to need to fully clean any hacked files and database tables, and then you're going to have to deal with all the damage caused to your site's standing. And just keep in mind, if you find anything about that process too daunting, we're always here to help. Now, for this month's Sit Down, we have Sucuri analyst Krasimir Konov. Earlier in June, he had written a lab's note about a malicious downloader script that used the curl function, and we chatted a bit about it, but more importantly, we went really in-depth on all the different varieties of malware that website owners need to be aware of. But, before I get started with Krasimir, I just wanted to remind you about the Sucuri Sync-Up, our sister podcast. It's a weekly website security news briefing that you can find anywhere you get your podcasts, as well as the video version on our social media feed, and now you can even get it on your Amazon Alexa smart speakers. Just search Amazon skills for Sucuri Sync-Up, add the flash briefing, and get new content delivered every Monday. Now, on with the show. Hi Krasimir, thanks for joining us on the show. I thought we could start off and maybe have you tell us a little bit about yourself and what you do here at Sucuri? Krasimir Konov: Yeah, sure. Well, I joined Sucuri originally in 2014, but I've been in the IT business for about 10 years. Nine of those I did security. And currently at Sucuri I'm one of the malware analysts. I used to work in the front lines, used to clean websites and whatnot, and then I gradually moved up, and now I'm working in the malware research department. And my day to day job is basically analyzing malware, and then once I analyze it and figure out what it is, then I will create a signature for it. And we'll add those signatures to our tools, so we can automate some of the work we do. And I also write some Labs Notes blog posts. Usually, if I find something interesting in malware or some security topic, I'll write about it. Justin Channell: Yeah. And of those topics recently that you wrote about, one was about a malicious curl downloader, and how exactly did that work? Krasimir Konov: Right, yeah. That was an interesting one, but not very unique or anything like that. We see that a lot with curl being used as a downloader. It's a very common malware. So rather than including the actual malware in the file, the attackers would use curl to download the malicious code. In this case, they'll download it from Pastebin, but it could be anything. It could be another website or anything like that, and curl would just make a call to the website, request the code. The website will respond with the code, and then later on, there is some code to either save the output somewhere on the website, or you'll just run it through eval and execute the actual code right away. Justin Channell: Right. And you said that it's commonly found in malware, but let's kind of maybe talk a bit broader about malware in general. What is everything that is classified as malware? Krasimir Konov: Well, in general it will be anything that the owner of the website didn't authorize, anything that was added by a third party. There is a lot of different malware. It could be even something like a defacement that will also be considered malware because it was something the user did not authorize. Even though it might not be doing anything malicious on the website, it's not infecting users, the visit is still something they did not authorize. So defacement would also be considered malware. And even something like ransomware where the website is technically not really damaged, it's all encrypted, but it's not infecting anybody. It's not doing anything malicious, but it's still encrypting the entire website and asking the user or the customer, the owner of the website for a ransom they need to pay in order to get the website back online. Justin Channell: Okay. Let's maybe break it down to each individual type of malware. For example, what would be a way that maybe I-frames could be maliciously used by a hacker? Krasimir Konov: Yeah. An I-frame can be used maliciously when it loads content from another location. You can look at the I-frame as a window that just opens another website. So anything that website has on it, you're pretty much loading it through the I-frame. So if that website is infected and it's serving some kind of malware, by opening an I-frame, you're loading all those elements, everything that was on this website. And sometimes the I-frame can be as small as pixel or something hidden somewhere off the screen, so you wouldn't even know that it was opening it. Justin Channell: And yeah, I feel like we've also seen a lot of them where they're used almost to mimic popups as well. Krasimir Konov: Yeah. I mean the I-frame, it could just load from another website and the other website could do anything. It could be serving just malware and it would try to infect the user that doesn't even know that they're being connected to the other website. It could just have some other JavaScript that's just trying to open up pop ups on the original website through the I-frame. Yeah, it could be a lot of things. Justin Channell: Okay. And also, let's talk a little bit about conditional redirects and how those work. What allows a script to detect which devices are coming in and where they're coming from? Krasimir Konov: Right. Yeah. That's a common one we see a lot. Basically, a conditional redirect would be something, it's a redirect on the website. It's obviously malicious, but there's certain conditions that need to be met before the redirect is actually executed or the redirect happens. For example, let's say if it's on a phishing website or a phishing page that is hidden somewhere on the website. For example, if Google visits it, obviously the attacker doesn't want Google to see the actual phishing page and record it as a phishing page. So they'll look for, for example, the IP address. They would look for the user agent. And a lot of times they can tell that it's a bot. So they'll just return a 404 response, for example, that will be like, "Oh, page not found." So Google would be like, "Oh, it looks like this page doesn't exist." But then if a regular user goes to the same page, then those conditions will be met. The actual website or the script behind the phishing will check and see, and be like, "Oh, this one is running Firefox or Chrome," and be like, okay. And then they'll look at the IP and be like, "Oh, he's in whatever, he's in United States somewhere." And he's like, "Oh, okay. That's good." And then once all of these conditions are met, then the actual script will serve them the actual phishing page. And it'll be like, "Oh, you need to fill out this to recover your account or whatever, or type in your credentials to log in here." Justin Channell: And so this is the type of thing we're really, a website owner is going to run into this more commonly when people are complaining about they're getting served bad content or whatever, and they can't seem to replicate it. It's likely probably these kind of redirects. Is that right? Krasimir Konov: Right, right. It could be something as specific as, for example, a range of IP addresses that correspond to an ISP or maybe let's say a country. It could be like, "Oh, were targeting only customers in the US," so if you're connecting from another country and you go to the same website or the same page, it would just say 404. It will give you a page not found. But then if you actually have an IP address from the United States, you're connecting from the United States, then it will actually show you the phishing page. Justin Channell: Now another type of malware I feel like we see a lot here is SEO spam. We hear people talking about that. What are some of the top SEO spam keywords that you see coming through? Krasimir Konov: Yeah. We get that a lot. We see a lot of spam on websites. A lot of times attackers will use SEO spam to gain ranking for their own website. Or they'll just try to include some kind of SEO spam in links to another website that they're currently running or something. I mean, these things change all the time. So a website might be up for a week and then it'll disappear, and then they'll start another campaign. But yeah, we see that a lot. We see all kinds of keywords they use. Most common ones will be something like Viagra. We'll have like jerseys for sale. A lot of times, they'll use name brands like Nike, Rolex, Prada. We've seen even some essay writing services for some reason. I'm not sure why, but that's common. We see, for example, pharmaceuticals a lot that will use specific medicine names. They'll use all kinds of replicas, like a replica bag of this, replica this, replica that. We'd see prescription, also payday loans. And obviously there's some adult related sites and things like that keywords. Justin Channell: So pretty much anything that people are going to be searching and clicking on are probably going to be targets for SEO spam? Krasimir Konov: Right. I think a lot of it commonly is pharma related because a lot of people are looking to buy medicine online, and a lot of times will require a prescription. So a lot of people are like, "Oh, let me see if I can find this medicine that I can buy it online somewhere." They don't need a prescription. They don't want to pay to visit a doctor and whatnot, and they'll look for it. And yeah. Justin Channell: Now, whenever somebody's website does get hacked with a SEO spam attack, what kind of effect can it have on the website beyond just being defaced? Krasimir Konov: Yeah. You can have a lot of things can happen, negative things. For example, the website can be blacklisted because of the keywords. And that usually represents a big red warning when you go on the website, depending on who blacklisted it. But if it's Google, for example, you'll see a big warning and it'll tell you this website contains malware or there's something wrong with this website. So, pretty much all the traffic on the website will be gone. And then you can also lose a lot of your reputation if there is a SEO spam on the website. For example, if you were ranked in say number five for certain keywords that represent your product on Google search engines, and then suddenly you get hit with SEO spam, then all these search engines then go and visit the website. And all of a sudden they're like, "Oh, there's all these weird key words on here, all this SEO spam that's causing a lot of mixed signals." And the search engines are like, "Oh, where do we rank this website now? Do we rank them with this product that's originally what the website is about? Or do we take into consideration all these other keywords that are mixed up that are SEO spam?" So, all of a sudden your website might go from being ranked number five on the first page to being on the 10th page. And then you rank for all these other keywords that you didn't intend to. And then people search for something completely different. They're searching for jerseys or something, or now they're searching for Prada products, and then suddenly your website pops up in there. So you're not really getting any good traffic, not targeted traffic. But, yeah. Justin Channell: Okay. So in a lot of ways, the effects of SEO spam would kind of be the same for defacements or any kind of malware with the blacklisting, but it does bring that kind of unique part to it where then it can also then bring traffic that you weren't expecting from somebody searching for jerseys, for example. I had not really ever thought about that. Krasimir Konov: Right, right. Yeah. It will definitely bring some traffic. I've seen a lot of times where websites will be connected. Let's say, there was 1,000 websites that were all infected with SEO spam, and it will kind of link each other to try to bring each other up into the rankings. And so you would see a lot of strange traffic from some random websites that were, for example, that were previously infected, even if they might not be anymore. But yeah, they'll be sending traffic to you or there'll be usually search engines sending you traffic, but for the wrong keywords. People are looking for something else, so obviously they're not going to be interested in your website. They're not going to buy anything because they're not looking for that. Justin Channell: And now, so thinking of the way websites get infected, a very common way it seems to be is through phishing campaigns. What are some recommendations you have for the best ways to avoid becoming a phishing victim? Krasimir Konov: Yeah. There is some ways. I mean, it depends really on the type of attack. Obviously, a lot of people, when they think of phishing, they think, "Oh, it's just like a PayPal phishing page and it just looks like the original," but it could be more subtle. If it's just a regular page where you're just going and you get redirected to another website, obviously the first thing to look is if you have the security padlocks, make sure that traffic is encrypted. A lot of these websites don't really have any encryption nowadays. More are starting to get that with pre SSLs being issued and whatnot. But that's the first thing to look and see, make sure. Anywhere you're typing your sensitive information, you want to make sure you have the padlock to make sure everything is encrypted. Krasimir Konov: But also you want to look at the URL of the actual website you're visiting. A lot of times they'll try to hide it. So you might have to be careful and look closely. Something that might be an I will be an L or something like that. And a capital I and L might look kind of similar into your IRL, so you might miss something like that. Say, if you're looking for PayPal and it might replace the L with an I, and if you don't look closely, it might look exactly the same. And you're like, "Oh, okay, it's paypal.com," but not really. So yeah. Just pay attention to the URL, make sure it is the actual website. There's no paypal.com dot something, dot something else, dot com. Yeah. You want it to just say paypal.com, and then it'll have forward slash and something else. But yeah, it gets more complicated when you have, for example, a phishing page that's injected into a regular page. For example, you have a checkout page on a website that you're buying things from and you go through the checkout page and you're looking at where you type in your credit card information and whatnot. And you might have a phishing page that actually looks exactly like a little box that gives you where you put in your credit card number, or your name, your address, and all that. So that will be more subtle. For example, that could be also an I-frame that's just coming from another page. And it will look exactly like it's part of the website. You're on the legitimate website, but only that portion of the website is actually the phishing page. And you look at it and you're like, "Oh, okay. It looks fine. I'm just putting my credentials." So that one could be a lot harder to figure it out. Usually, if it's something like that, I look for something that looks kind of out of place. Maybe they didn't get the right font. It might not be the same as the original website or there might be something out of place, some fields that are missing or some fields that are squished into the left or the right. It looks kind of awkward. It's like, why would this be like this? The whole website looks professional. There's a pink background or something, for example, and then suddenly there's this white box in the middle. It's like, ah, it looks kind of weird, out of place. Justin Channell: So pretty much if anything looks slightly out of place, you really should double check everything at that point. Krasimir Konov: Right. Right. Yeah. Obviously there's more ways that you can check, but I wouldn't get into more technical, like inspecting elements and looking at stuff, but yeah. Justin Channell: And now another type of malware that's kind of, and it kind of plays in with whatever the other infection is, is backdoors. Can you give us some examples of what backdoors can be? It's mainly just when a hacker can get back into the site to reinfect it, but I know there are a ton of different methods. And what are some of the more common ones and then maybe some that really interesting that you've seen? Krasimir Konov: Yeah, there is a lot. They'll probably be one of the first things the hacker would do is if they compromise a website, obviously they'll try to spread backdoors and just inject code everywhere so they can get back in, even if the owner of the website or webmaster cleans it. They want to try and hide some malicious code somewhere so they can always get back in. There's many variations. A backdoor could be something as simple as a single line of code to just [inaudible 00:20:19] argument, some kind of string or something via get or post. Krasimir Konov: And then it runs into an eval, so it evaluates the code and executes it. And some backdoors are very complex and they can be included in, let's say you have a WordPress site and you have a specific login page where all the login credentials are being processed and everything else. They could even inject code into that to basically bypass the whole login mechanism so that they can just bypass everything. They don't even have to know any user. They don't have to know the password, nothing. They'll just include some lines in there, and every time they'll be just able to log in. Yeah. It gets pretty crazy. Yeah. I mean, there's all kinds of malware. There is always a malware, for example, that just targets credit cards and will just target the eCommerce websites. And they'll just try to steal the login credentials, I mean, the credit cards. They'll try to get your address, your credit card information, any kind of CVV code or whatever you typed into the billing address, everything. And then there's also malware like the backdoors that are just trying to keep the attacker in control and trying to get them back into the website. There's just so many variations of what a malicious user might want to do on a website. Some can be something as simple as just reinfecting the website. They don't want to keep control. They just want to keep reinfecting it with some kind of malware. So even if you clean it, it would just get reinfected. Some of them in the database, otherwise might be in the files. We've seen some added into a [inaudible 00:22:14] job that just keeps running on the server. There could be malware that is just a giant to, for example, attack out of websites. Like for example, a distributed denial service where they put the same malware on thousands of websites. And then they try to send traffic to one website to try to bring it down. Yeah. People try to do all kinds of stuff with websites. We've seen even some cryptocurrency mining malware that you go onto a website and suddenly your PC starts running like crazy. And you're like, what the hell is going on? Your fans turn on and the PC is 100% CPU. And it turns out that the website has some malware that's just by mining Bitcoins with your CPU and it's using all of it. Justin Channell: Wow. Okay. So one question now, the last question I have is of all the malware that you've seen, what do you think is the coolest piece of malware that you've ever seen? Krasimir Konov: I think the coolest would be the ones that are so subtle that you don't even know that it's there. For example, we've seen some that were pretty innovative. It will be just a one liner code that's just one line. And for example, it will be let's say 40-50 characters, something like that. And that's all it is. And they'll hide it somewhere in between the legitimate code. And if you don't know what you're looking for, you would never see it. It doesn't look suspicious. There is no links to some other website. There's no some kind of encrypted code or anything like that. It's just a simple one line. And then if you're just scrolling through the file looking for something, you would never see it. It just looks like all the other code. And then if you look closely, you're like, "Oh, there's this..." Look closely, and you're like, "Oh wow, this is not supposed to be there." And then you keep looking at it and you're like, "This looks really weird." And then you see that it's actually doing some malicious things and trying to evaluate some code or taking output from the outside, I mean, some input from outside, you can call it and give it code to run. Justin Channell: Well, Krasimir, thanks for coming on and talking to us for today. Krasimir Konov: Yeah. Thank you. Thank you. I'm so happy. I'm glad I was able to do this podcast and I can't wait to do another one. Justin Channell: Yeah, we'll have you on again. Thanks. Krasimir Konov: Thank you. Justin Channell: Thanks again to Krasimir for joining us here on the Sit Down. We'll be back with another episode next month. So be sure to subscribe on Apple podcasts, Spotify, Stitcher, or any podcasting platform. Also, be sure to follow us on social media at Sucuri Security and check us out at sucuri.net. That's S-U-C-U-R-I.net. I'm Justin Channell, And this has been the Sucuri Sit Down. Stay safe out there.](https://blog.sucuri.net/wp-content/uploads/2020/05/20-sucuri-podcast-blog-post_blog_image-390x183.jpg)
27 comments
I was affected on Sunday too. Happily I discovered it quickly and made a fix based on my experience a few weeks ago when I was affected with the zettapetta malware. Otherwise I might not have even known.
I suspect a lot of users are affected without even realising it.
If Bluehost are aware of a problem, then I would have appreciated some sort of acknowledgement or notification.
Hello David, you happen to have a quick fix, my site was affected also.
well…I am one of the microscopic minority of BlueHost sites having issues with this. Looking at the forums over there on BlueHost, it is evidently the "smaller sites owned by individuals and small companies without an IT department", who are too stupid to maintain their sites properly, that are being affected…I really do not appreciate arrogant comments. I keep my sites up to date and use BlueHost's SimpleScripts, etc. Is it really helpful to put people down when they are having issues like this?
If it weren't for you guys at Sucuri, I would not have even known this was on my site in the first place. Now I am trying to figure out what to do to keep it from happening again, and I guess there's really no point asking anyone over there at BlueHost for any help…
Sucuri, keep up the good work. If it were not for you guys I wouldn’t have known about the incident.
Hi there,
I am affected too, at least from Monday 28June. All my sites under BLUEHOST are currently hacked by the script you reported.
Unfortunately BLUEHOST response this time has been totally unsatisfying. The usually have reasonable service but in this opportunity, all I am getting is standard copy/paste answers that I can probably Google myself.
I’ve been exchanging emails with those guys since yesterday and still no one offers real help.
It’s really disappointing.
regards,
Luis
dre:
Though I agree with you that the way bh is handling it is not the best, you have to admit that when you say something like "a good number of sites at hosting company x" is very ambiguous–Maybe next time you could give an actual estimate, from what you guys have seen: ie "At least 350 websites at hosting company x"
Just my two cents.
-Anapologetos
We said a good number because it is very hard for an external entity to fully determine the scope of an attack. We during our initial assessment, found around 150 sites hacked (but we checked only around 1.5k sites hosted in there). It would mean 1% of sites if we extrapolated, but we didn’t want to give hard numbers to avoid misinforming.
Now we have found a lot more sites affected than that, but but haven’t check the 240k sites that they host, so it is a lot more… Even if it were only 200 or 300, it is still a good number for us, specially if the attack happened due to their fault (considering that even their CEO blog got hacked).
Seems like you are trying too hard. You have no actual numbers and can only provide guesses on the issue.
That's probably because Bluehost gives false (guessed) numbers and doesn't have any solid numbers or facts before they start shutting people down.
Considering when you call bluehost tech support they ask for your account password. It does surprise me at all.
Ouch. I run several bluehost sites. I’m going to call them right now.
@David Dede
150 sites in 1.5K is not 1%, it is 10%
I was trying to investigate how this happened (before I discovered it was a Bluehost-wide exploit), and discovered that my raw access logs for June 1 – 29 were gone. I contacted them and they simply said sorry for the inconvenience — is anyone else noticing this issue?
Further, when I contacted them about it, they just gave me a generic response about securing php scripts, and that they can’t determine which script is malicious since it’s 3rd party code so they don’t know what is supposed to be on my site and what’s not. It’s difficult for me to determine which php script to secure without the access logs, which is what I was expecting them to do.
Bluehost support: "Sir, we haven't had a security incident in two years. If you didn't read it on our official website, it's most likely hearsay [that we can't verify]."
Why do you guys even use Bluehost? I always expect them to have problems and lie about shit. Used them for 2 years, but I wouldn’t do it again if they offered me free hosting for the rest of my life.
My recent post “Don’t taze my granny-”
If they’re smart, Bluehost should pay attention carefully and learn from all the mistakes that GoDaddy has made…
Bluehost is nothing like GoDaddy and their business practices are nothing alike so why would they care what GoDaddy has done?
I was hacked too, very odd. I don't have lots of experience dealing with these issues. Any suggestions appreciated? What files are usually compromised to cause the redirect?
VERY angry with Bluehost right now. My sites are hit and I’m redirecting right now to a page on mobileme. Anyone have any suggestions on a new host provider?
BH is the New BP. Why can they just come clean so people know what to expect and take proper action? Thanks Sucuri for exposing this.
Bluehost needs to just be up front and not make up statistics that 75% of their client base won't understand. Yes, I do think they make things up to butter it up for customers…why? Because I've been where they are and that's just what a company will do to try to cover up a deeper issue. I don't think the issue is because Bluehost is necessarily insecure – it's because they're not taking responsibility for the compromises and getting it fixed by providing their customers with more detailed and researched information by covering it up with dirt and putting daisies around it…it's stupid and everyone has a right to be upset. The responses are mostly canned and their CEOs or management think of the most appropriate way for their tech support to relay it to you. But don't expect the tech support to actually know what is going on. The interdepartmental communication sucks at Bluehost.
But please also understand that they are only providing an easy solution for application software download. They're not securing your scrips and typically exploits on medium to large networks like Bluehost are seen more frequently than on smaller networks. If you all know your stuff, Bluehost is comprised of 3 different companies (what they call sister companies including Fastdomain and Hostmonster).
So, if you do not keep your scripts up-to-date you'll be compromised. If you're using 3rd party plug-ins and themes, you could be compromised by means of those as well. Are you checking your file permissions? It sounds all very paranoid but if you're a web dev like me you know it's possible for even the smallest exploit to turn into a huge mess of things.
If it were a server wide compromise due to a server being rooted maliciously, and if it were in fact Bluehost on the side of negligence, the entire server would be exploited.
The fact is, it's a shared host and this happens more frequently than you think on other hosts as well. Also, and this is just by biased 2 cents, if you're running a PHP based application software for your web site, you're just asking for it.
Hello, We have been on Bluehost for probably 5 years now… In the past 5 weeks, we have been hacked SEVERAL times, and the last being just yesterday at 14:35 EDT. The problem is that we have to log into the control panel hourly to see if there is security updates. We logged in yesterday morning, no updates, hacked at 14:35, logged into our control panel and there was an update for word press.
I run two BlueHost sites. How would I check to see if I was hacked? Kinda new still to this whole thing.
Thanks Sucuri for exposing this flaw in Bluehost.
It seems typical of Bluehost to lie to its customers about a problem rather than admit it and fix it.
Comments are closed.