Forum Moderators: Robert Charlton & goodroi
Anyway, the email gave a snippet of hidden links, he definatly didn't put them there as they all point to p1ll sites, he has no php or mysql only 6 .html pages, all had a massive chunk of junk at the bottom just before the closing body/html tags
many lines like this
example.com/upload_files/documents/plain_text.php?sql_error=1&page=2593">low cost p1ll name
My question is, how do the spammers do this and what does he, or his host, need to do to prevent this in the future, he has changed his password.
These criminals (Danny sullivan called them "crap hats") will exploit any security hole that they can in order to get into a server. That can mean any application that is not up to date with the latest patches. It might be cpanel or vdeck, it might be database or scripting software, there are loads of possibilities for "how" and there's a network of these shady folks that spreads the latest discoveries.
What the the web host needs to do is stay up-to-date on patches and upgrades to any app they are running. The more commonly used an application is that runs on the server, the more it is a target for parasite hosting.
[edited by: tedster at 7:42 am (utc) on Mar. 3, 2009]
It's interesting google gave a heads up
The email states (in different words) it looks like a 3rd party has modified your pages, so they seem to know it's not the site owner to blame, further down it also says google would like to keep his site in the index.
He has spoken to his host and of course they say they had no issues and their systems are up to date.
The email states (in different words) it looks like a 3rd party has modified your pages, so they seem to know it's not the site owner to blame, further down it also says google would like to keep his site in the index.
He has emailed his customer support desk, he also said he forgot to mention he has one mysql database, he doesn't edit it through the browser though, he works in phpmyadmin so he's only pulling data to display not pushing it, he has checked the structure and says all looks normal, is there any way it can't be the host?
More: WebmasterWorld site search [google.com]
Jim
You fix what you *can* fix, then pound on the host to fix the rest... :)
If the site has been subject to SQL injection, you will find requests with some or all of those keywords in the query strings of requested URLs in the raw server access log file. Since you state that you know the time that the files were cracked/modified, it should be relatively easy to find these particular requests (if they exist).
However, note that blocking these queryies unconditionally may 'break' the CMS/database functions. Again, look at the raw log files to see if legitimate requests can be discerned from illegitimate ones... by REMOTE_ADDRess, by HTTP_USER_AGENT, etc. If so, add RewriteConds to the rule so that only legitimate requests are allowed. (Note that I didn't say, "so that illegitimate requests are blocked... It's a mind-set thing, and an important one, to approach security from the standpoint of what you want to allow, not what you want to block; The ramifications are quite different for errors of omission in these two approaches.)
Jim
I never did find exactly how it happened: I know it wasn't SQLI, there was no cpanel and it's not commercial CMS. Infection did recur a couple of times until I did some serious server-cleaning - taking off a lot of very dodgy stuff that LOOKED like genuine DLLs (MS/IIS server) plus a few that were probably genuine.
I THINK the original backdoor was uploaded by FTP - there was an exploit in the server I used at that time that may have let someone in without a password (all accounts were login, not anonymous).
I changed FTP server and now force almost all my clients to use SSL access, giving them 12+ character passwords. Whether FTP is an exploit vector or not I strongly recommend this if possible.