Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Hacked

1 view
Skip to first unread message

SuperSlueth

unread,
Sep 10, 2007, 6:14:01 AM9/10/07
to
I'm running exchange 2003 on server 2003 with all the latest patches and
fixes applied. I have the latest version of norton corperate antivirus with
all the updates.
I've done a full scan and the server is clean.
Yet every 2 or 3 days I see that a new user has been added "hello5" and
programs have been installed.
I can delete the programs and the user I've disabled remote desktop and
changed the admin password, but still this person still gets to the server.
does anyone have any idea how to find out where he comes in from and how to
block it

Newell White

unread,
Sep 10, 2007, 10:40:02 AM9/10/07
to
Record the modified and created dates on the installed files and their
containing folders. This will give you some clue as to the time window you
should search in the Security log using Event Viewer - should give you IP of
computer originating any login request.

What is your network topology?
Anti-virus software won't help.
Do you have hardware firewall between server and the wicked outside world?
If so, and it is configured correctly, this is most likely an inside job.
--
Newell White

James Matthews

unread,
Sep 10, 2007, 3:03:54 PM9/10/07
to
Not always does someone hack using an exploit! Sometimes they crack the
passwords etc... You have to consider every and any point of intrusion

--

http://www.goldwatches.com/
http://www.jewelerslounge.com/
"Newell White" <Newel...@discussions.microsoft.com> wrote in message
news:D35907B2-F92A-4CBA...@microsoft.com...

Nex6

unread,
Sep 11, 2007, 3:31:22 PM9/11/07
to

You really need to look hard and every possible point of entry. form
existing users to an outside attacker. here are some basic questions to
ask yourself:

*is there a hardware firewall between you and the internet? eg are you on
a private address space?


*audit every account and group membership.
*audit every possbile place to hide startup scripts and excutables, both
in the registry and start menu

*increase event logging to FULL, eg: in secpol.msc check both boxes on all
audit policys


*run both nbtstat and netstat and investigate all conntections.


*consider, having every user reset his/her passwords, and reset all
service accounts. and old or temp accounts reset or disable

That should give you a pretty good start.


-Nex6

Nex6

unread,
Sep 11, 2007, 3:31:07 PM9/11/07
to

You really need to look hard and every possible point of entry. form
existing users to an outside attacker. here are some basic questions to
ask yourself:

*is there a hardware firewall between you and the internet? eg are you on
a private address space?


*audit every account and group membership.
*audit every possbile place to hide startup scripts and excutables, both
in the registry and start menu

*increase event logging to FULL, eg: in secpol.msc check both boxes on all
audit policys


*run both nbtstat and netstat and investigate all conntections.


*consider, having every user reset his/her passwords, and reset all
service accounts. and old or temp accounts reset or disable

That should give you a pretty good start.


-Nex6

On Mon, 10 Sep 2007, James Matthews wrote:

Nex6

unread,
Sep 11, 2007, 3:31:45 PM9/11/07
to

You really need to look hard and every possible point of entry. form
existing users to an outside attacker. here are some basic questions to
ask yourself:

*is there a hardware firewall between you and the internet? eg are you on
a private address space?


*audit every account and group membership.
*audit every possbile place to hide startup scripts and excutables, both
in the registry and start menu

*increase event logging to FULL, eg: in secpol.msc check both boxes on all
audit policys


*run both nbtstat and netstat and investigate all conntections.


*consider, having every user reset his/her passwords, and reset all
service accounts. and old or temp accounts reset or disable

That should give you a pretty good start.


-Nex6

On Mon, 10 Sep 2007, James Matthews wrote:

Nex6

unread,
Sep 11, 2007, 3:32:04 PM9/11/07
to

You really need to look hard and every possible point of entry. form
existing users to an outside attacker. here are some basic questions to
ask yourself:

*is there a hardware firewall between you and the internet? eg are you on
a private address space?


*audit every account and group membership.
*audit every possbile place to hide startup scripts and excutables, both
in the registry and start menu

*increase event logging to FULL, eg: in secpol.msc check both boxes on all
audit policys


*run both nbtstat and netstat and investigate all conntections.


*consider, having every user reset his/her passwords, and reset all
service accounts. and old or temp accounts reset or disable

That should give you a pretty good start.


-Nex6

On Mon, 10 Sep 2007, James Matthews wrote:

Nex6

unread,
Sep 11, 2007, 3:32:27 PM9/11/07
to

You really need to look hard and every possible point of entry. form
existing users to an outside attacker. here are some basic questions to
ask yourself:

*is there a hardware firewall between you and the internet? eg are you on
a private address space?


*audit every account and group membership.
*audit every possbile place to hide startup scripts and excutables, both
in the registry and start menu

*increase event logging to FULL, eg: in secpol.msc check both boxes on all
audit policys


*run both nbtstat and netstat and investigate all conntections.


*consider, having every user reset his/her passwords, and reset all
service accounts. and old or temp accounts reset or disable

That should give you a pretty good start.


-Nex6

On Mon, 10 Sep 2007, James Matthews wrote:

Nex6

unread,
Sep 11, 2007, 3:34:27 PM9/11/07
to

You really need to look hard and every possible point of entry. form
existing users to an outside attacker. here are some basic questions to
ask yourself:

*is there a hardware firewall between you and the internet? eg are you on
a private address space?


*audit every account and group membership.
*audit every possbile place to hide startup scripts and excutables, both
in the registry and start menu

*increase event logging to FULL, eg: in secpol.msc check both boxes on all
audit policys


*run both nbtstat and netstat and investigate all conntections.


*consider, having every user reset his/her passwords, and reset all
service accounts. and old or temp accounts reset or disable

That should give you a pretty good start.


-Nex6

On Mon, 10 Sep 2007, James Matthews wrote:

Nex6

unread,
Sep 11, 2007, 3:36:30 PM9/11/07
to

You really need to look hard and every possible point of entry. form
existing users to an outside attacker. here are some basic questions to
ask yourself:

*is there a hardware firewall between you and the internet? eg are you on
a private address space?


*audit every account and group membership.
*audit every possbile place to hide startup scripts and excutables, both
in the registry and start menu

*increase event logging to FULL, eg: in secpol.msc check both boxes on all
audit policys


*run both nbtstat and netstat and investigate all conntections.


*consider, having every user reset his/her passwords, and reset all
service accounts. and old or temp accounts reset or disable

That should give you a pretty good start.


-Nex6

On Mon, 10 Sep 2007, James Matthews wrote:

Shenan Stanley

unread,
Sep 11, 2007, 5:05:17 PM9/11/07
to
Nex6 wrote:
> You really need to look hard and every possible point of entry. form
> existing users to an outside attacker. here are some basic
> questions to ask yourself:
>
> *is there a hardware firewall between you and the internet? eg are
> you on a private address space?
>
>
> *audit every account and group membership.
> *audit every possbile place to hide startup scripts and excutables,
> both in the registry and start menu
>
> *increase event logging to FULL, eg: in secpol.msc check both boxes
> on all audit policys
>
>
> *run both nbtstat and netstat and investigate all conntections.
>
>
> *consider, having every user reset his/her passwords, and reset all
> service accounts. and old or temp accounts reset or disable
>
> That should give you a pretty good start.

Nex6,

You have definitely replied.

http://groups.google.com/group/microsoft.public.security/browse_thread/thread/666afb8a166b3ba7/6f8ccac2a10d451c?lnk=st&q=group%3Amicrosoft.public.security+insubject%3AHacked&rnum=1#6f8ccac2a10d451c

--
Shenan Stanley
MS-MVP
--
How To Ask Questions The Smart Way
http://www.catb.org/~esr/faqs/smart-questions.html


Message has been deleted
0 new messages