Closey, thanks..
1 As you said, The rpcbind daemon is not running.
when using the command
# rpcinfo -p hostname
got the error below :
rpcinfo: can't contact portmapper: RPC: Rpcbind failure - RPC: Failed
(unspecified error)
I tried to start it by running /etc/init.d/rpc start
nothing happened. :(
2
unfortunately ....
# ls -la srload
total 29500
-rwxr-xr-x 1 root dba 259832 Jul 12 20:15 srload
and fortunately there is the directory /usr/lib/libX.a
I would like to try RootKit, want to know how to use it...
Thank you very much.
Main Topics
Browse All Topics





by: colsey79Posted on 2003-07-23 at 01:20:33ID: 8984132
Hmmm, looks like two problems here:
1. the svc_create and svc_tp_create errors:
Sounds like you rpcbind daemon isn't running. Start it by running /etc/init.d/rpc start
Why this didn't start up when your system booted is up to you to find out. I suspect it may be something like the rc script has been removed (/etc/rc2.d/S71rpc on Sol 9)
2. Init command respawning
You're not gonna like this, but it looks like you may have a hacked system... :-(
/usr/bin/srload is NOT a Sun binary, and isn't on any supplied version of Solaris. I suspect you have a RootKit installed on your system. Probably the X-Org SunOS RootKit, this is the most common one for Solaris. You can try downloading "chkrootkit" from the net, but this isn't 100% reliable. Another way to confirm this is if you have the directory "/usr/lib/libX.a". If you do, then you definately have a rootkit on your system. This directory hasn't existed on Solaris since SunOS 4.x
The best solution.... blow away you machine and rebuild it and patch it to the teeth. There is no point restoring from backup and it will be very hard to determine how far back this rootkit was installed or what vulnerability they used to enter your system.