Beware, i was hacked
Armo
Mr. Nice Guy Is Dead,Only Aqua Remains Member
my machine was hijacked by 1 if not 2 people ranging from
83.67.86.196
83.196.74.94
both of which originate from Amsterdam
they installed a remote administration tool as well as ServUFTP and ServUDaemon. on 2/2/2006 @ approx 2:48AM east.
they hijacked my RealVNC service when i was using my machine one day. as i saw my cursor move on its own to browse one of my drives properties. I have since done a system restore to remove all inlaid DLL callers and EXE's from the registries, as well as the services that run on the machine. I also locked down my machine.
is there any sort of action i can take against these people knowing the DNS servers they used as IP addresses, i also have audit logs of when they connected. also can a linksys router block subnets?
83.67.86.196
83.196.74.94
both of which originate from Amsterdam
they installed a remote administration tool as well as ServUFTP and ServUDaemon. on 2/2/2006 @ approx 2:48AM east.
they hijacked my RealVNC service when i was using my machine one day. as i saw my cursor move on its own to browse one of my drives properties. I have since done a system restore to remove all inlaid DLL callers and EXE's from the registries, as well as the services that run on the machine. I also locked down my machine.
is there any sort of action i can take against these people knowing the DNS servers they used as IP addresses, i also have audit logs of when they connected. also can a linksys router block subnets?
0
Comments
EDIT: If the problem persists, i'l tell the user to do a system restore like you did.
I also found out what they did with the FTP, from 2AM till about 9 PM, when i got home from work, they had uploaded 14 gigs of french movies. see now had they been good movies in english i would have let them keep going, lol
Funny thing, they never got to guess any passwords because they couldn't guess the login name. I find it odd that they tried every variation of "admin" under the sun and varieties of common names but never tried the most obvious one: root.
-drasnor
Its a very bad idea to leave ssh on the default port unless you have ssh login as root disabled and your box is urber secure.
Edit:Also the best way to ban anyone is to do a reverse dns on anyone who connects to your server then ban anyone using the targets dns server.
-drasnor