
Originally Posted by
Spiral
Logicsupport and gariben, scanning for just "iframe" is a bad idea as you'll probably get a huge number of hits to sort through which have nothing to do with the attacks!
I wrote a basic cron script for this posted in one of my other posts somewhere on here if anyone wants to go back through my posts and post the link.
Basically in a nutshell though, you should be searching for ":8080" or ".ru" as those are the things that seem to be pretty consistent in the hacked iframe insertions calling to a remote proxy out of several Russian based URLs.
I have also been prototyping another script where I've basically indexed all my client's normal incoming FTP connection IPs to a database and I check the CIDR ranges of all new FTP connections against that database of their previously known connections when they connect and notify administrators if a connection is made for that client different from their normal known connections. This won't help with a stage I attack as they proxy off of the infected victim but it will more quickly identify possible follow up attacks as we are alerted immediately if anyone that is potentially someone other than the client connects to the client's FTP account.
For those clients who have dedicated IPs at home, we have taken things a step further and have setup Cpanel and FTP to drop and ban the connections of anyone who logs in to our client's accounts that doesn't originate from their known IP address. This is done by way of a cron job that monitors log files and issues an IPTABLES drop when a connection is made to login to a specific user's account that doesn't originate from that user's known home dedicated IP address.
These are a few ideas that you could do as well which might help this situation.