I saw THIS in my Apache log -

**************************************************
218.144.121.165 - - [10/Sep/2004:16:19:01 +0300] "GET http__soem_strange_url
218.144.121.165 - - [10/Sep/2004:16:19:01 +0300] "GET http__soem_strange_url
218.144.121.165 - - [10/Sep/2004:16:19:01 +0300] "GET http__soem_strange_
.............
.............

**************************************************

My www-pages on Apache CANNOT make these queries.
I think i'm hacked. 8-(((
I saw in logs - it was downloaded about 2 Gigs(!) from other sites!


What is it ???

Please HELP!!!!!!!!!!
What I have to fix ?????

My system -
Apache-AdvancedExtranetServer/2.0.47 (Mandrake Linux/6mdk) mod_perl/1.99_09 Perl/v5.8.1 mod_ssl/2.0.47 OpenSSL/0.9.7b PHP/4.3.2

i dont know about your specific problem... but the general steps you want to take are......

1) Run netstat.... make a note of any network programs that are running, but shouldnt be... make a note of any IP addressed connected to any ports that they shouldnt be.

2) Take the machine off the network, make any notes of anything usefull that may be lost after a re-boot. for example, are any porgrams running that shouldnt be,,, (ftp servers or http servers or telnet / ssh server ? especially on strange ports... Any changes made to your firewall ?

3) Shutdown...

4) Dont boot the machine, but boot a trusted OS like Knoppix (Live CD linux distro)
and use rkhunter or chrootkit to search for any root kits that may have been installed.

If you have been rooted, then the only cerain way to get rid of the problem is to do a format and clean install. (backup non executable and non config files)

when you get your machine back up, upgrade to the latest version of Apache...

Does your Server run Tripwire ? (if not then why not !!!)
from a knoppix session, chroot into the hacked hard drive and run "tripwire --check"

Does your server run Snort ? (if not then why not !!!)
is there anything interesting in the snort logs ?

I have been helped by another people!!

mod_proxy !!!!

Is that module vulnerable?

There was a recent mod_proxy vuln with Apache 1.3, but it required a non-standard configuration (Apache had to be specifically setup to allow proxy requests, which is not the default configuration).

What you're likely seeing is someone attempting to locate an open proxy. This is fairly common and likely isn't much to be concerned about unless you're seeing large numbers of proxy requests. Though you should make sure that you've updated Apache recently (there was a mod_ssl vuln release for Mandrake last week).