Re: Apache hacks (./atac, d0s.txt)

From: Chris Umphress (umphress_at_gmail.com)
Date: 04/30/05

  • Next message: Sagiko: "Re: Apache hacks (./atac, d0s.txt)"
    Date: Sat, 30 Apr 2005 00:46:37 -0700
    To: Andrew Y Ng <ayn@andrewng.com>
    
    

    > Looks like it ignores all the `kill` signals, not sure how I can actually
    > kill it...

    SIGKILL (Signal 9) cannot be blocked, so try:

    kill -s SIGKILL <pid>
    -or-
    killall -KILL atac

    > my @canais=("#bots ddos");
    > my $nick='b0t';
    > my $ircname = 'b0t';
    > $servidor='irc.gigachat.net' unless $servidor;

    It's an IRC bot, should be obvious, but just commenting...

    > $SIG{'INT'} = 'IGNORE';
    > $SIG{'HUP'} = 'IGNORE';
    > $SIG{'TERM'} = 'IGNORE';
    > $SIG{'CHLD'} = 'IGNORE';
    > $SIG{'PS'} = 'IGNORE';

    Again, there is no way to block SIGKILL (signal 9) for any program

    > # DCC
    > package DCC;

    This is where things get really scary for you. DCC is the ability to
    send files over IRC. The bot could have sent almost anything (within
    certain permission ranges, we hope). Now is a very good time to
    disconnect the server from the internet if you have not already done
    so.

    > notice("$pn", "\001Bot powered by DDOS TEAM\001");

    This line seems to indicate that this bot is only designed to be part
    of a larger "bot-net" to DoS someone, but those DCC capabilities are
    worrysome. So, in addition to investigating how this got into your
    server, it would also be a good idea to check what might have gotten
    out.

    Good luck, and apologies if you already knew all of this.

    -- 
    Chris Umphress <http://daga.dyndns.org/>
    

  • Next message: Sagiko: "Re: Apache hacks (./atac, d0s.txt)"

    Relevant Pages

    • Re: NETWORK Administration
      ... > You check which process the shell they use has and then kill it. ... to send the process a SIGHUP - SIGnal HangUP: connection has been lost ... Both these signals can be caught and allow the terminated programto die ... Using SIGKILL should be a last resort as it ...
      (alt.linux)
    • Re: How to dump the locked up program
      ... a simple Google search for "How do I kill a process in Linux?" ... "kill -l" gives a list of possible signals. ... Sometimes a process cannot be killed even with SIGKILL (because it's ... waiting in the kernel on some event that will never happen) and a reboot ...
      (Fedora)
    • Re: How to dump the locked up program
      ... a simple Google search for "How do I kill a process in Linux?" ... "kill -l" gives a list of possible signals. ... Sometimes a process cannot be killed even with SIGKILL (because it's ... waiting in the kernel on some event that will never happen) and a reboot ...
      (Fedora)
    • Re: anyway to ignore a kill signal?
      ... 2005-05-17, 10:04, elw: ... there needs to be signals that can't be trapped. ... SIGKILL is ... kill -9 is to be called when there's no other alternative. ...
      (comp.unix.shell)
    • Re: [PATCH] ptrace/coredump/exit_group deadlock
      ... by segfaulting the task and triggering a core dump while some other ... stopped task can't wakeup because it has SIGNAL_GROUP_EXIT set, ... in which a SIGKILL is left pending before the thread stops. ... be selected from the queue in preference to any stop signals. ...
      (Linux-Kernel)