Jump to content


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.

Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.


IFrame.Trojan virut.vitro Neeris.worm Partition problems MBR help

  • This topic is locked This topic is locked
4 replies to this topic

#1 winst0n


  • Members
  • 9 posts
  • Local time:09:02 AM

Posted 19 August 2009 - 06:21 AM

Scan is at 9% and it has found 6317 problems/viruses.
I already posted a bunch of stuff at Geekstogo.
They recommended I give up and format my hard drive.


I'll get the dds and rootrepeal logs up as soon as I have finished the non windows methods.
I've got Klam anti-virus running.
I'm gonna try to see if I can run the Avira rescue linux CD from a USB flash drive. (I'll resort to burning a CD if I must)
I'm gonna take a look at some Boot Record stuff with boot wizard and NTFS4dos.

I don't know if anyone has any ideas about partition weirdness,
but I have a flash boot of Ubuntu 9.04 live and when I took a look at the partition tables with fdisk in the terminal;
Both my flash drives had all 4 partition tables filled with incorrect info.
When I booted back off the hard drive and took another look the table info was ok.
Single partition entries as it should be.


winston@ubuntu-9-04:~$ sudo fdisk /dev/sdd

Command (m for help): p

Disk /dev/sdd: 8015 MB, 8015282176 bytes
255 heads, 63 sectors/track, 974 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x0000000a

Device Boot Start End Blocks Id System
/dev/sdd4 * 1 974 7823623+ 6 FAT16


winston@ubuntu-9-04:~$ sudo fdisk /dev/sde

Command (m for help): p

Disk /dev/sde: 4194 MB, 4194304000 bytes
255 heads, 63 sectors/track, 509 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000

Device Boot Start End Blocks Id System
/dev/sde4 * 1 509 4088511 6 FAT16


(copy and paste to apply a fixed width font of that didn't work)
I set the geometry up to match the old zip disk format as recommended on this page:


Did that make some voodoo occur?
Can someone explain the difference with a simple format and this:

mkdiskimage -4 /dev/sde 0 255 63


"-4" supposedly indicates zip geometry ... what does that mean?
Why did it have to take so long?

Try the following options if you want more information:

foo --help, foo -h, foo -?

info foo

whatis foo, apropos foo

dpkg --listfiles foo, dpkg --search foo

locate ’*foo*’

find / -name ’*foo*’

Additionally, check the directories /usr/share/doc/foo, /usr/lib/foo.

When do man pages start making sense?

winston@ubuntu-9-04:~$ mkdiskimage --help
Usage: /usr/bin/mkdiskimage [-doFMz4][-i id] file c h s (max: 1024 256 63)
-d add DOSEMU header
-o print filesystem offset to stdout
-F format partition as FAT32
-M "c" argument is megabytes, calculate cylinders
-z use zipdisk geometry (h=64 s=32)
-4 use partition entry 4 (standard for zipdisks)
-i specify the MBR ID

At one point I had the cryptic "boot error"
I have the buggy Award BIOS and I could very likely have a BOOT virus so I don't know what to make of it.
I'll try to take another look after booting back up off the live flash to see if the misbehaviour repeats itself.

PS anyone explain the difference between a GB & a GiB?
The same?
One 1024 MB ... other 1000MB?
Is a MB 1024KB or 1000KB?
If a KB is 1024 bytes, are there still 8 bits in a byte or are there 32 bits in a FAT32 byte?
Am I going to have to learn to translate the MBR from Hex to be sure I don't have a BOOT virus?

10% 9607 viruses ...

BC AdBot (Login to Remove)


#2 htv8


  • Members
  • 1,694 posts
  • Gender:Male
  • Location:The Netherlands
  • Local time:06:02 PM

Posted 20 August 2009 - 01:52 PM

Hello winst0n. I'm sorry to tell you this, but the people over at Geeks to Go! are right. I think no malware helper would bother cleaning this infection as trying to do so would be a waste of time. Please read the following.

Virut is a polymorphic file infector with IRCBot functionality which infects .exe, .scr files, downloads more malicious files to your system, and opens a back door that compromises your computer. According to this Norman White Paper Assessment of W32/Virut, some variants can infect the HOSTS file and block access to security related web sites. Virux is an even more complex file infector which can embed an iframe into the body of web-related files and infect script files (.php, .asp, and .html). When Virut creates infected files, it also creates non-functional files that are corrupted beyond repair. In many cases the infected files cannot be disinfected properly by your antivirus. When disinfection is attempted, the files become corrupted and the system may become irreparable.

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.

REFERENCE: McAfee Risk Assessment and Overview of W32/Virut

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.

REFERENCE: AVG Overview of W32/Virut

miekiemoes' Blog: Virut is back again - sigh

miekiemoes' Blog: Virut and other File infectors - Throwing in the Towel?
This kind of infection is contracted 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.

[..] 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 [..]

REFERENCE: Crack Sites Distribute VIRUX and FakeAV | Malware Blog | Trend Micro
I would counsel you to immediately disconnect this PC from the Internet and from your network if it is on a network. If you do any banking or other financial transactions on the PC or if it should contain any other sensitive information, please get to a known clean computer and change all passwords where applicable. All passwords should be changed immediately to include those used for banking, email, eBay, PayPal, online forums, etc.: you should consider them to be compromised. Do NOT change passwords or do any transactions while using the infected computer because the attacker may get the new passwords and transaction information! (If using a router, you need to reset it with a strong logon/password so the malware cannot gain control before connecting again.) Banking and credit card institutions should be notified to apprise them of your situation (possible security breach). To protect your information that may have been compromised, I recommend reading these references:
There is no guarantee this infection can be completely removed. In some instances it may have caused so much damage to your system that it cannot be completely cleaned or repaired. The malware may leave so many remnants behind that security tools cannot find them. Many experts in the security community believe that once infected with this type of malware, the best course of action is to wipe the drive clean, reformat and reinstall the OS. This is something I don't like to recommend normally, but in most cases it is the best solution for your safety. Reinstalling Windows without first wiping the entire hard drive with a repartition and/or format will not remove the infection. The reinstall will only overwrite the Windows files. Any malware on the system will still be there afterwards. For more information, please read these references very carefully:

If you insist on trying to fix this infection instead of following my advice to reformat and reinstall your Operating System, there are various rescue disks available from major antivirus vendors which you can try. Keep in mind, even the vendors like Kaspersky say there is no guarantee that some files will not get corrupted during the disinfection process. In the end most folks end up reformatting out of frustration after spending hours attempting to repair and remove infected files. In my opinion, the safest and easiest thing to do is just reformat and reinstall Windows.

BleepingComputer DOES NOT assume any responsibility for your attempt to repair this infection using any of the following tools. You do this at your own risk and against our advice.

These are links to antivirus vendors that offer free LiveCD or Rescue CD files that are used to boot from for repair of unbootable and damaged systems, rescue data, scan the system for virus infections. Burn it as an image to a disk to get a bootable CD. All (except Avira) are in the ISO Image file format. Avira uses an EXE that has built-in CD burning capability.If you are not sure how to burn an image, please read How to write a CD/DVD image or ISO. If you need a FREE utility to burn the ISO image, download and use ImgBurn.

My advice to you, , is to reformat and reinstall. Virut is a nasty and relatively new infection and no-one can promise that the fix will work completely. Again, BleepingComputer does NOT recommend that you attempt it.

I suggest you to start backup all of your valuable data/documents/pictures/movies/songs/etc.
Keep in mind, though, that with a Virut infection, there is always a chance of backed up data reinfecting your system! Do NOT backup any applications/installers and do NOT backup any executable files (*.exe), screensavers (*.scr), autorun (.ini) or script (.php, .asp, .html, .htm, .xml) files. Also avoid backing up compressed files (.zip, .cab, .rar) that have .exe or .scr files inside them as Virut can penetrate and infect these files within compressed files too.
NOTE: If you have to backup files, do so only for MS Office documents & any non-executable files. Burn them to CD/DVD. Do NOT copy files from the infected machine to your flash drive or external hard drive as they may become compromised in the process. You risk infecting the other machine!

Virut is not disinfectable. Your only option is to perform a full reformat. Do NOT attempt a repair install. It shall be a waste of time. If you do so, the infected executables remain on the machine & you shall likely trigger another bout of Virut.

If you do not know how to perform a fresh install, use these websites and read for instructions how to format and reinstall Windows:
  • MIT IS&T: Windows XP - Clean Install
  • [url="http://www.windowsreinstall.com/"]www.windowsreinstall.com

Sorry to be the bearer of bad news, but this really is your only option at this point. Should you have any questions, please feel free to ask.


If I have not posted back within 24 hours, feel free to send me a PM with your topic link.

Posted Image

#3 winst0n

  • Topic Starter

  • Members
  • 9 posts
  • Local time:09:02 AM

Posted 21 August 2009 - 09:43 PM

I won't be trying windows for a while ...

21265 was the final count.
I went and erased whole directories of HTML files.
Klam Anti-Virus has found 3 "broken executables" in the Linux File System that I am inclined to leave.
(it's libfglrx_ip.a.GCC4 that was updated twice).
Before I attempt another Windows distribution I would like to obtain BOOT SECTOR confidence.
I'm still a ways away from looking at raw Hex dumps.
I've ben fiddling with partitions a little and some unexpected things have been happening.
I've been getting Physical/Logical discrepancies.

Something that was infected is making me think a different win distro may be necessary:

Has anyone ever heard of a reason for a "USB" folder that does not correspond to an actual flash drive?
What I have COULD be legitimate but I am concerned that virus activity either independent from, or packaged with my Windows distribution may be the cause.

winston@ubuntu-9-04:/media$ ls
cdrom disk floppy ntfsdisk USB\040DISK
cdrom0 disk-1 floppy0 RED\0402GB WHITE-DT-8G

winston@ubuntu-9-04:/media$ cd USB\ DISK
bash: cd: USB DISK: No such file or directory
winston@ubuntu-9-04:/media$ cd USB*
winston@ubuntu-9-04:/media/USB\040DISK$ ls
boot.bin DOCS $OEM$ syslinux.cfg VALUEADD WIN51IP
boot.catalog I386 README.HTM ubnfilel.txt vesamenu.c32 win51ip.SP3
cmpnents OEM SUPPORT ubnpathl.txt WIN51
winston@ubuntu-9-04:/media/USB\040DISK$ cd \$OEM\$
winston@ubuntu-9-04:/media/USB\040DISK/$OEM$$ ls
$$ $Docs
winston@ubuntu-9-04:/media/USB\040DISK/$OEM$$ cd \$\$
winston@ubuntu-9-04:/media/USB\040DISK/$OEM$/$$$ ls
OEMDIR Resources system32 Web

At one point I was trying to make a bootable Flash from the distro so it may be some kind of buffer folder that I can erase.
I will cross-post in a Linux Forum.

Still only the 3 problems in Klam.

#4 winst0n

  • Topic Starter

  • Members
  • 9 posts
  • Local time:09:02 AM

Posted 22 August 2009 - 11:16 PM

Sorry about posting without the DDR or DDS or the other log.
But I ran the second scan and Klam said it's clean.
So I think I've got some Avira tools to run.
It's been a couple of days so these notes become notes to self for me to back-reference.

I know no matter what I do apart from wiping my drives is "certifiable" advice.
That being said does anyone have any recommendations for BOOT SECTOR tools?

I found a very technical document laying out the address particulars of FAT32.

Microsoft Extensible Firmware Initiative FAT32 File System Specification
FAT: General Overview of On-Disk Format

Version 1.03, December 6, 2000
Microsoft Corporation

The FAT (File Allocation Table) file system has its origins in the late 1970s and early1980s and was the file system supported by the Microsoft® MS-DOS® operating system.

slightly grokable bit here:

General Comments (Applicable to FAT File System All Types)
All of the FAT file systems were originally developed for the IBM PC machine architecture. The importance of this is that FAT file system on disk data structure is all “little endian.” If we look at one 32-bit FAT entry stored on disk as a series of four 8-bit bytes—the first being byte[0] and the last being byte[4]—here is where the 32 bits numbered 00 through 31 are (00 being the least significant bit):

byte[3] 3 3 2 2 2 2 2 2
________1 0 9 8 7 6 5 4

byte[2] 2 2 2 2 1 1 1 1
________3 2 1 0 9 8 7 6

byte[1] 1 1 1 1 1 1 0 0
________5 4 3 2 1 0 9 8

byte[0] 0 0 0 0 0 0 0 0
________7 6 5 4 3 2 1 0

This is important if your machine is a “big endian” machine, because you will have to translate between big and little endian as you move data to and from the disk.

A FAT file system volume is composed of four basic regions, which are laid out in this order on the volume:
0 – Reserved Region
1 – FAT Region
2 – Root Directory Region (doesn’t exist on FAT32 volumes)
3 – File and Directory Data Region

From here I'll need to get into Assembly unless I can find a good BOOT SECTOR tool.
Got some stuff on the Universal Boot CD.
Once again I'll cross post on a linux forum.

#5 htv8


  • Members
  • 1,694 posts
  • Gender:Male
  • Location:The Netherlands
  • Local time:06:02 PM

Posted 25 August 2009 - 04:22 AM

Hello again, winst0n.

Once again, please know that Virut is not disinfectable. Again, my advice to you is to reformat and reinstall. BleepingComputer does NOT recommend that you attempt to repair this infection and does NOT assume any responsibility for your attempt. You do this at your own risk and against our advice.

I'm sorry I can't advice you any further on this. That's why I am going to close this topic now. Hope you understand.

With kindest regards :thumbup2:,

If I have not posted back within 24 hours, feel free to send me a PM with your topic link.

Posted Image

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users