Jump to content
Posted 23 July 2009 - 11:04 AM
Posted 23 July 2009 - 11:36 AM
McAfee Risk Assessment and Overview of W32/Virut
The virus has a number of bugs in its code, and as a result it may misinfect a proportion of executable files....some W32/Virut.h infections are corrupted beyond repair.
AVG Overview of W32/Virutcontracted and spread by visiting remote, crack and keygen sites. These type of sites are infested with a smörgåsbord of malware and an increasing source of system infection. However, the CA Security Advisor Research Blog says they have found MySpace user pages carrying the malicious Virut URL. Either way you can end up with a computer system so badly damaged that recovery is not possible and it cannot be repaired. When that happens there is nothing you can do besides reformatting and reinstalling the OS.
There are bugs in the viral code. When the virus produces infected files, it also creates non-functional files that also contain the virus...Due to the damaged caused to files by virut it's possible to find repaired but corrupted files. They became corrupted by the incorrect writing of the viral code during the process of infection. undetected, corrupted files (possibly still containing part of the viral code) can also be found. this is caused by incorrectly written and non-function viral code present in these files.
Keygen and Crack Sites Distribute VIRUX and FakeAV
...warez and crack web pages are being used by cybercriminals as download sites for malware related to VIRUT and VIRUX. Searches for serial numbers, cracks, and even antivirus products like Trend Micro yield malcodes that come in the form of executables or self-extracting files...quick links in these sites also lead to malicious files. Ads and banners are also infection vectors...
Posted 23 July 2009 - 11:59 AM
Posted 23 July 2009 - 12:04 PM
Posted 23 July 2009 - 06:42 PM
Posted 23 July 2009 - 11:21 PM
Posted 11 October 2009 - 12:46 PM
Posted 14 October 2009 - 01:42 PM
Posted 02 November 2009 - 04:01 PM
Posted 12 November 2009 - 07:10 AM
I have seen this problem arise on a few computers lately and although there are quite a lot of posts about it on the Internet, I hadn't had any luck finding a solution.
Hopefully this might help people having this problem who do not wish to carry out a full re-installation.
The antivirus removes/quarantines the infected NDIS.sys and once you replace it with a known good copy the operating system fails with a blue screen during normal startup.
I compared the relevent registry entries on a working machine with a problem machine (previously infected with the Virut virus).
On the machine with the problem, the following registry key was not present:
Once this key was restored along with its data, the machine booted up fine again.
The data for the key is given below (.reg format). It was taken from an XP Pro SP2 machine and isn't necessarily correct for all other verisions of Windows:
Windows Registry Editor Version 5.00
"DisplayName"="NDIS System Driver"
Posted 14 June 2010 - 12:34 AM
Posted 29 June 2010 - 09:45 AM
Posted 30 June 2010 - 06:12 AM
0 members, 0 guests, 0 anonymous users