server compromised?

[Paul Mooring]

It's likely that if he left that key in there with a valid e-mail address then whoever compromised the server wasn't trying to be discrete.  I would check my auth logs to see when/if someone was logging in from somewhere suspect.  Next if the server was compromised, it's done, you can never trust it again, no amount of clean up or post-mortem investigation can ever give reasonable confidence that there's no back door on it.  Move the services and data and make a new server/clean install, then look very carefully at what attack vector was exploited and close it (like if it was brute force you should have ssh for root turned off, more restrictive firewall rules and ssh guard).

Having a server compromised can be a huge headache, good luck.
--
Paul Mooring
Systems Engineer and Customer Advocate

www.opscode.com

From: Vimal Shah <vimals at sokikom.com<mailto:vimals at sokikom.com>>
Reply-To: Main PLUG discussion list <plug-discuss at lists.phxlinux.org<mailto:plug-discuss at lists.phxlinux.org>>
Date: Thursday, March 7, 2013 4:49 PM
To: Main PLUG discussion list <plug-discuss at lists.phxlinux.org<mailto:plug-discuss at lists.phxlinux.org>>
Subject: server compromised?

Hello all,

While randomly looking into the .ssh/authorized_keys file, I noticed a line that shouldn't have been there. This was concluded based on the last portion of the line. This portion was in the form of user at domain.com<mailto:user at domain.com>, where the domain was one of a likely competitor. Does this automatically mean that this server has been compromised? The line has been removed.

Thanking everyone in advance.

--
Vimal
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.phxlinux.org/pipermail/plug-discuss/attachments/20130308/93d43bc6/attachment.html>