Help!

Home of discussion, generally. If it doesn't go in any of the other forums, post it in here.
Post Reply
User avatar
boywoos
Elite Wanderer
Elite Wanderer
Posts: 641
Joined: Wed May 15, 2002 4:05 am

Help!

Post by boywoos »

Have to be quick... basically I keep getting this message about a RDC server being halted, consequently my comp keeps shutting down I also get this message just before "Generic Host Process for Win32 Services has encountered a problem and needs to close." I run XP home edition. Any help would be greatly appreciated.

EDIT: Sorry that was RPC.
User avatar
Sol Invictus
Wanderer of the Wastes
Wanderer of the Wastes
Posts: 579
Joined: Fri Apr 19, 2002 2:59 am
Location: Imperium
Contact:

Post by Sol Invictus »

Try not to fuck up your Remote Procedure Calls or you'll never be able to run your computer ever again.
Administrator

Circle of Eight - Hellgate: London Resource Center
www.co8.org
User avatar
SuperH
Hero of the Wastes
Hero of the Wastes
Posts: 1752
Joined: Wed Jul 03, 2002 9:31 am

Post by SuperH »

If i'm not mistaken, isn't that exactly what the dreaded worm thingy does to your computer? Install a firewall or nab the patch off windowsupdate.com man, it'll stop it quick as butter. Unless you're doing something really really wrong and it's not the worm.
jerman999
Vault Scion
Vault Scion
Posts: 242
Joined: Sun May 26, 2002 7:17 am
Location: Connecticut

Post by jerman999 »

1.) Login as an administrator
2.) Press CTRL-ALT-DEL and click on the processes tab
3.) Click on msblast.exe and click "End Process"
4.) Disable system restore (it might mess up the removal)
5.) Download the patch from windowsupdate.microsoft.com
6.) Download the Symantec Removal Tool
7.) Remove MsBlaster
8.) Do a complete virus and spyware scan.

If the tool doesn't work, start up in safe-mode and try again. The worst case scenario is that an attacker has completely compromised your system (trojans, viruses, etc.) and you have to do a complete re-install.

Of course I give no guarentees that this will work, I got all the info here.
User avatar
boywoos
Elite Wanderer
Elite Wanderer
Posts: 641
Joined: Wed May 15, 2002 4:05 am

Post by boywoos »

Everything is fine now, thanks peeps.
User avatar
Zbyram
Vault Scion
Vault Scion
Posts: 216
Joined: Fri Jun 07, 2002 11:00 pm

Post by Zbyram »

I had the thing before it was even popular. :D Caught it on the 11th.
User avatar
spyder07
Vault Elite
Vault Elite
Posts: 379
Joined: Sun Jun 02, 2002 10:59 am
Location: Looking for my freaking computer parts

Post by spyder07 »

What exactly does that worm do, becuase last week my good computer stop detecting the processor leaving me with a big box of fans and lights.
jerman999
Vault Scion
Vault Scion
Posts: 242
Joined: Sun May 26, 2002 7:17 am
Location: Connecticut

Post by jerman999 »

Taken from Symantec.

Symantec wrote:When W32.Blaster.Worm is executed, it does the following:

1. Checks to see whether a computer is already infected and whether the worm is running. If so, the worm will not infect the computer a second time.

2. Adds the value:

"windows auto update"="msblast.exe"

to the registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run

so that the worm runs when you start Windows.

3. Generates an IP address and attempts to infect the computer that has that address. The IP address is generated according to the following algorithms:
* For 40% of the time, the generated IP address is of the form A.B.C.0, where A and B are equal to the first two parts of the infected computer's IP address.

C is also calculated by the third part of the infected system's IP address; however, for 40% of the time the worm checks whether C is greater than 20. If so, a random value less than 20 is subtracted from C. Once the IP address is calculated, the worm will attempt to find and exploit a computer with the IP address A.B.C.0.

The worm will then increment the 0 part of the IP address by 1, attempting to find and exploit other computers based on the new IP address, until it reaches 254.

* With a probability of 60%, the generated IP address is completely random.

4. Sends data on TCP port 135 that may exploit the DCOM RPC vulnerability. The worm sends one of two types of data: either to exploit Windows XP or Windows 2000.

For 80% of the time, Windows XP data will be sent; and for 20% of the time, the Windows 2000 data will be sent.

NOTES:
* The local subnet will become saturated with port 135 requests.
* While W32.Blaster.Worm cannot spread to the Windows NT or Windows Server 2003, unpatched computers running these operating systems may crash as a result of the worm's attempts to exploit them. However, if the worm is manually placed and executed on a computer running these operating systems, it can run and spread.
* Due to the random nature of how the worm constructs the exploit data, this may cause the RPC service to crash if it receives incorrect data. This may manifest as svchost.exe, generating errors as a result of the incorrect data.
* If the RPC service crashes, the default procedure under Windows XP and Windows Server 2003 is to restart the computer. To disable this feature, see step one of the Removal Instructions below.

5. Uses Cmd.exe to create a hidden remote shell process that will listen on TCP port 4444, allowing an attacker to issue remote commands on an infected system.

6. Listens on UDP port 69. When the worm receives a request from a computer to which it was able to connect using the DCOM RPC exploit, it will send msblast.exe to that computer and tell it to execute the worm.

7. If the current date is the 16th through the end of the month for the months of January to August, or if the current month is September through December, the worm will attempt to perform a DoS on Windows Update. However, the attempt to perform the DoS will succeed only if one the following conditions is true:
* The worm runs on a Windows XP computer that was either infected or restarted during the payload period.
* The worm runs on a Windows 2000 computer that was infected during the payload period and has not been restarted since it was infected.
* The worm runs on a Windows 2000 computer that has been restarted since it was infected, during the payload period, and the currently logged in user is Administrator.

8. The DoS traffic has the following characteristics:
* Is a SYN flood on port 80 of windowsupdate.com.
* Tries to send 50 HTTP packets every second.
* Each packet is 40 bytes in length.
* If the worm cannot find a DNS entry for windowsupdate.com, it uses a destination address of 255.255.255.255.
spyder: You might've had a script kiddie run some crap on your computer. That would explain the loss of the processor.
User avatar
bloodbathmaster2
Vault Elite
Vault Elite
Posts: 366
Joined: Thu Apr 18, 2002 6:29 am
Location: The Outskirts of Insanity

Post by bloodbathmaster2 »

/me grins and hugs his windows 98 and firewall
One day...
User avatar
OnTheBounce
TANSTAAFL
TANSTAAFL
Posts: 2257
Joined: Thu Apr 18, 2002 8:39 am
Location: Grafenwoehr, Oberpfalz, Bayern, Deutschland
Contact:

Post by OnTheBounce »

bloodbathmaster2 wrote:/me grins and hugs his windows 98 and firewall
Y'know, this is the fist time I've been glad that I was running Windows ME, although I'd still rather have 98 SE.

OTB
"On the bounce, you apes! Do you wanna live forever?!"
User avatar
Strap
Hero of the Desert
Hero of the Desert
Posts: 1641
Joined: Tue Jun 11, 2002 2:59 am
Location: a cave

Post by Strap »

OnTheBounce wrote:
bloodbathmaster2 wrote:/me grins and hugs his windows 98 and firewall
Y'know, this is the fist time I've been glad that I was running Windows ME, although I'd still rather have 98 SE.

OTB
primitive bastard (again)

At least I've got a fire wall, so I'm safe in my cozy little basement.
User avatar
spyder07
Vault Elite
Vault Elite
Posts: 379
Joined: Sun Jun 02, 2002 10:59 am
Location: Looking for my freaking computer parts

Post by spyder07 »

I see. It wouldn't be so bad if I could get through to the freaking company to get some freaking replacement parts.
Post Reply