public inbox for linux-newbie@vger.kernel.org
 help / color / mirror / Atom feed
From: Anshuman Singh Rawat <asr245@nyu.edu>
To: linux-newbie@vger.kernel.org
Subject: linux box hacked ?
Date: Mon, 20 Sep 2004 19:42:51 -0400	[thread overview]
Message-ID: <9765ac97d150.97d1509765ac@nyu.edu> (raw)

Hi,
I want to know how one can know for sure if a linux box has been hacked. This morning a linux box in our lab was behaving funny. More clearly, i was executing some commands and on doing a 'grep', 'grep' threw a segmentation fault!! Also, I saw (with a 'ps -A') there were several processes running with names like'xscan', 'pscan'. There were several 'cat' commands running; some of them were dead (if that's  what defunct means). Also, I noticed that the executables for 'cat', 'grep' and a few others showed a modification date of today. I tried to reboot the system, but that never happenned. The boot loader complained about /etc/fstab being corrupted or missing, and ofcourse as booting procedure uses the 'grep' command (which was throwing segmentation faults), the machine couldn't boot.

We really couldn't figure out for sure what happenned but do any of these symptoms indicate that somebody could have hacked into it?

Thanks,
Anshuman

PS: We had Apache web server running on this machine and we didn't have a firewall installed (other than linux's basic firewall install).


-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

             reply	other threads:[~2004-09-20 23:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-20 23:42 Anshuman Singh Rawat [this message]
2004-09-21  1:11 ` linux box hacked ? simon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9765ac97d150.97d1509765ac@nyu.edu \
    --to=asr245@nyu.edu \
    --cc=linux-newbie@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox