Discussion Locked

Would Nimda Virus cause this problem?

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

We have a client who found the Nimda.A virus on there server (during a chance virus scan). During the scan, 99 infected files were found and automatically deleted. After the scan was completed, I went down there with some information about this virus which I had found on the Internet.

I looked at everything and anything that this piece of document mentioned and found that it looked as though this virus hadn't done anything yet. It looked like it was deleted before it could do any damage.There was also a file I could have run which was meant to undo any damage Nimda had done, but since it appeared as though it hadn't done any damage, i didn't run this file.

A week later, this client rings me to say they can't get on the internet. I find that in the Internet Management Console, FTP, Gopher, WWW and web proxy aren't running. So I try to start them all but they all come up with an error that 'the specified module could not be found'. I then find out that the client had done another virus scan that previous morning and found the Nimda virus again and it was auto deleted (yet again). But it was from this time that after the server was rebooted that these services wouldn't start again. I am now wondering if the Nimda virus could have done this or if it is something entirely different and just purley a coincidence.

Either way, does anyone have any suggestions. Thanks for your help.

5 replies

by dmiles

The Nimda virus multiplies itself to a number of files that are diguised as program files (load.exe,mep*.files) that the anti-virus thinks are good files possibly attached to (*.eml and *nws)it attaches to file transfer or email software that you are using to transport itself when executed
Tech Republic had a great article on the virus and also a mention of how to manually use tool to get all files
Check your anti-virus for the tool also.

by xanderoth

I can tell you that in addition to what the other reply said, that the Nimda will forcefully attack open shares on your network and copy itself there, and it can lie dormant for 10 days before attacking again. Also- it attacks IIS and web server vehemently and kiss your winsocks apps goodbye. If you find Nimda on a machine after it has been cleaned, disconnect it from your network and internet, and all machines that are connected via the network, and run Nimda fix tools on each of them beforeconnecting them again. Nimda likes to run and hide when you delete it by jumping from machine to machine. Ensure you have no (zero) Windows9x shares without read only and full access passwords attached. Make sure you have IE 6.0 or sp2 for IE5.5,and get the IIS patches at www.microsoft.com to protect against further infection from the outside world.

This discussion is closed to new replies.