If you try to protect your server in 100 ways..Hackers try to find a 101 way to intrude into the server...Its a race that will stay on till the end.... As of now the hack attemp carried out on your site cab be achieved by .
1.WebDev ( Http compromise)
2. Trojen through compromised CSS files in your server.
3. Weak Passwords ( If you notice in depth sites that were hacked should have got very weak passwords in that server..We have seen that sites in same server with strong passwords escaped from this kind of attack)
4. Scripts and Executables enabled with backdoor trojan atack...
5. NO FIREWALL IN YOUR SERVER.
6. Sites or Users having permissionover "CMD"
7. EXE file execution Allowed.
8. Make sure to scan your server throughlly ...Most Trojan's or virus files are hidden or attached in zip files and CSS scripts...check them .....
9. Have very Strong Password..
Last but not at all the least.... Have Firewall installed in your server and spo the Attackers IP from the HTTP request used to upload the files ( using PUT method) from IIS logs and block them imdtly...
You can very well trace the IP location and ISP from their IP and Block a whole IP range for safty...
I would not like to recomend any firewall..But I have personally used Visnetic Firewall (3) when 5 of our servers came into attack.... The best part is that I had a chance to chat with the hacker as and when he was uploading the files in our server and I could not stop him finally till I banned his IP in FW .... So be carefull USE FIREWALL FIREWALL and scan server with latest security and AV updates...
Main Topics
Browse All Topics





by: NeoDiffusionPosted on 2009-01-06 at 00:20:23ID: 23302609
Hello,
The hack source is probably:
"This site was hacked previously, and I changed the password to a new one that contained upper case, lower case, numbers and symbols. "
--> at which level have you modified password(s)? (ftp? backend? htaccess?, ...)
the previous hackers probably left more than an index.html file, namely one or more backdoors. My recommendation:
- sanity: make an file snapshot (zip whole site) and copy locally. Bitwise compare with a copy you know as safe (far before first attack). This is a huge work and requiring a reliable archive, an alternative is to run an antivirus software on your snapshot (and possibility on a database dump). Norton Antivirus for instance used to know several web backdoors.
- curative: the only way to make sure you do not leave any backdoor is to re-install the whole site from scratch. This is however a huge work to get the copy site at the same level as the original one. This is how I proceed: create from an empty repository a mirror of the site. If based on a CMS, download again the files, don't trust local files. Use as few archive files as possible, and check them for unexpected content before use. Once the mirror is at the level of the original, swap them. Depending on your hosting plan, it can be as simple as 2 mv commands...
Last time I've worked on an infected site, there were over 10 backdoors/spam engines on the website, and still not sure to have catched all of them.Of course, it is also possible that you simply have an unfixed vulnerability. If using a CMS, look at http://secunia.com/advisor
In all case, look at the raw server logs around the time the file got modified (few hours before/after). Seek for strange formed URL (GET or POST). If your site hadn't a index.html before the attack, look at the first mention of "index.html" to see the attack point...
Good Luck,
Werner.