cannot replace binaries after being rootkitted
From: don quixada (xanthus@NOSPAM.iname.com)
Date: 04/24/03
- Next message: Bit Twister: "Re: cannot replace binaries after being rootkitted"
- Previous message: Julio Cesar Hernandez Castro: "CFP:Special Session on Evolutionary Computation in Computer Security and Cryptology at the CEC2003"
- Next in thread: Bit Twister: "Re: cannot replace binaries after being rootkitted"
- Reply: Bit Twister: "Re: cannot replace binaries after being rootkitted"
- Reply: Bill Unruh: "Re: cannot replace binaries after being rootkitted"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: don quixada <xanthus@NOSPAM.iname.com> Date: Wed, 23 Apr 2003 16:25:20 -0700
Hi, I've been rootkitted with `suckit'. And I have two dilemmas
(dilemmae?). First, I cannot replace the affected binaries, i.e. I get
the permission denied message. I used `chkrootkit' and it says that
`ifconfig', `pstree' and `login' are infected; however, I cannot delete
them or replace them even using RPM. I noticed that the files are owned
by a non-root user and they cannot be changed back to root.
My second issue is that I think more files than the three indicated by
`chkrootkit' are infected. My main reason for suspecting this is that
`init' was affected (i.e. the cracker replaced my init with one that
didn't work (I _was_ able to fix that one)). I also noticed other files
that are owned by the same user as the infected files (that, I think,
should be owned by root) such as `ps', `ls', `md5' (which seems
especially bad) and `find' (`grep' does not seem to be affected). I
can't remember offhand, but I think `rpm' may be infected as well.
Anyway, my questions are these:
How can I replace/delete the infected files (short of reformatting)?
How can find out, for sure, which files are infected?
My system vital-statistics are:
RH 7.2, kernel 2.4.20, my machine is a desktop computer where I am the
sole user (although I have several login names-- the files in question
that aren't root-owned are owned by one of these users), I was running a
very insecure FTP server and Samba (for no reason other than I was lazy
to unintall it) so either one of those was probably how the cracker got in.
Please note that I am a newbie when it comes to Linux security (yes I
did read the FAQ)-- I guess I had that "It'll never happen to me!"
mentality.
Thanks in advance for your help.
dq
- Next message: Bit Twister: "Re: cannot replace binaries after being rootkitted"
- Previous message: Julio Cesar Hernandez Castro: "CFP:Special Session on Evolutionary Computation in Computer Security and Cryptology at the CEC2003"
- Next in thread: Bit Twister: "Re: cannot replace binaries after being rootkitted"
- Reply: Bit Twister: "Re: cannot replace binaries after being rootkitted"
- Reply: Bill Unruh: "Re: cannot replace binaries after being rootkitted"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|