From: urgrue <urgrue@tumsan.fi>
To: admin <linux-admin@vger.kernel.org>
Subject: hacked
Date: Wed, 12 Jun 2002 14:51:41 +0300 [thread overview]
Message-ID: <20020612115141.GA1599@fede2.tumsan.fi> (raw)
hi,
a hacker has planted trojans and messed around with one of my boxes.
its off the network, but i want to know what he did.
i replaced netstat, ps, lsof (and others) with originals, but nmap
shows that ports 1130 and 53228 are open on the box. i can even telnet
to these ports and get what definitely looks like backdoors.
but netstat and lsof cant find anything on these ports.
and ps of course doesnt show anything unusual.
since ive replaced the binary commands with originals, but these ports
are still open, presumably some networking related library has been
trojaned?
anyone know which one/ones, or how to find out?
next reply other threads:[~2002-06-12 11:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-12 11:51 urgrue [this message]
2002-06-12 13:36 ` hacked Glynn Clements
2002-06-12 13:40 ` hacked urgrue
2002-06-12 15:20 ` hacked Bruce Ferrell
2002-06-12 16:41 ` hacked Glynn Clements
2002-06-12 20:28 ` hacked fred orispaa
2002-06-13 2:09 ` hacked Bruce Ferrell
2002-06-13 2:19 ` hacked Gary E. Miller
2002-06-13 11:46 ` hacked Glynn Clements
2002-06-13 19:06 ` hacked Gary E. Miller
2002-06-17 21:26 ` hacked Ionut Murgoci
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=20020612115141.GA1599@fede2.tumsan.fi \
--to=urgrue@tumsan.fi \
--cc=linux-admin@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;
as well as URLs for NNTP newsgroup(s).