Small_comp.100

Printer Friendly Page

Discovered: May 26, 1995
Updated: February 13, 2007 12:15:15 PM
Also Known As: Baby.cmp.b [McAfee], Baby.100.a, Baby.100.c, Baby.100.e [Kaspersky]
Type: Virus
Systems Affected: DOS


Small_comp.100 is a small companion virus. It infects the .com and .exe files.

Antivirus Protection Dates

  • Initial Rapid Release version January 31, 1996
  • Latest Rapid Release version January 31, 1996
  • Initial Daily Certified version January 31, 1996
  • Latest Daily Certified version January 31, 1996
  • Initial Weekly Certified release date January 31, 1996

Click here for a more detailed description of Rapid Release and Daily Certified virus definitions.

Writeup By: Yuhui Huang

Discovered: May 26, 1995
Updated: February 13, 2007 12:15:15 PM
Also Known As: Baby.cmp.b [McAfee], Baby.100.a, Baby.100.c, Baby.100.e [Kaspersky]
Type: Virus
Systems Affected: DOS


When Small_comp.100virus is executed, it does the following.

  1. Loads itself into memory and stays memory-resident.

  2. Hooks the "load or execute" DOS function (INT 21h, Function 48h).

Once this happens, when you execute a .com or .exe file, the virus does the following:
  1. Takes control of the executed file.

  2. Renames the executed file to <File name>.ex? or <File name>.co?.

  3. Writes the virus itself into a hidden file, <File name>.exe or <File name>.com, and then executes the original program.


Note: <File name> is the original file name without the extension.

"?" is a special character. Different variants of the same virus could use different characters. The following characters have been seen:

 \0xDB
V



Recommendations

Symantec Security Response encourages all users and administrators to adhere to the following basic security "best practices":

  • Use a firewall to block all incoming connections from the Internet to services that should not be publicly available. By default, you should deny all incoming connections and only allow services you explicitly want to offer to the outside world.
  • Enforce a password policy. Complex passwords make it difficult to crack password files on compromised computers. This helps to prevent or limit damage when a computer is compromised.
  • Ensure that programs and users of the computer use the lowest level of privileges necessary to complete a task. When prompted for a root or UAC password, ensure that the program asking for administration-level access is a legitimate application.
  • Disable AutoPlay to prevent the automatic launching of executable files on network and removable drives, and disconnect the drives when not required. If write access is not required, enable read-only mode if the option is available.
  • Turn off file sharing if not needed. If file sharing is required, use ACLs and password protection to limit access. Disable anonymous access to shared folders. Grant access only to user accounts with strong passwords to folders that must be shared.
  • Turn off and remove unnecessary services. By default, many operating systems install auxiliary services that are not critical. These services are avenues of attack. If they are removed, threats have less avenues of attack.
  • If a threat exploits one or more network services, disable, or block access to, those services until a patch is applied.
  • Always keep your patch levels up-to-date, especially on computers that host public services and are accessible through the firewall, such as HTTP, FTP, mail, and DNS services.
  • Configure your email server to block or remove email that contains file attachments that are commonly used to spread threats, such as .vbs, .bat, .exe, .pif and .scr files.
  • Isolate compromised computers quickly to prevent threats from spreading further. Perform a forensic analysis and restore the computers using trusted media.
  • Train employees not to open attachments unless they are expecting them. Also, do not execute software that is downloaded from the Internet unless it has been scanned for viruses. Simply visiting a compromised Web site can cause infection if certain browser vulnerabilities are not patched.
  • If Bluetooth is not required for mobile devices, it should be turned off. If you require its use, ensure that the device's visibility is set to "Hidden" so that it cannot be scanned by other Bluetooth devices. If device pairing must be used, ensure that all devices are set to "Unauthorized", requiring authorization for each connection request. Do not accept applications that are unsigned or sent from unknown sources.
  • For further information on the terms used in this document, please refer to the Security Response glossary.

Writeup By: Yuhui Huang

Discovered: May 26, 1995
Updated: February 13, 2007 12:15:15 PM
Also Known As: Baby.cmp.b [McAfee], Baby.100.a, Baby.100.c, Baby.100.e [Kaspersky]
Type: Virus
Systems Affected: DOS


  1. Restart the computer using a clean system disk.
  2. Use the Norton AntiVirus DOS scanner to run a full system scan and delete all the files detected as Small_comp.100.
  3. Rename all the affected files to their original name, or restore or re-install them.

1. Restarting with a clean system disk
Because this DOS virus is memory-resident, restart the computer using a clean boot disk.

2. Running the Norton AntiVirus DOS scanner
  1. At the C:\> prompt, type the following command:

    dir /s /b \navdx.exe

    Then press Enter.

    This displays the path to the Norton AntiVirus DOS scanner. If Norton AntiVirus is installed to a different drive, first change to the root of that particular drive. The default is C:\Program Files\Norton AntiVirus.

  2. Change to the folder that contains Navdx.exe. Use short file names. For example, if Norton AntiVirus is installed in C:\Program Files\Norton AntiVirus, type:

    cd program~1\norton~1

  3. Type one of the following commands:

    CAUTION: This could take several hours or more on some computers. Do not stop the scan once it has started.

    NOTE: The DOS-based scanner can perform one of the following actions when it detects a virus:
    • To be prompted for any file detected as infected, type the following:

      navdx /a /doallfiles /prompt [Enter]

      Press R)epair, D)elete, or C)ontinue for each infected file. If you choose this option and Norton AntiVirus cannot repair an infected file, you will see the message, "Unable to repair the file," followed by the same three choices. In most cases, you should choose D)elete, unless you are sure that the file is not actually infected.

    • To delete any file detected as infected, type the following:

      navdx /a /doallfiles /delete [Enter]

      The disadvantage of doing this is that the repairable files will be deleted.

    • To repair any file detected as infected, type the following:

      navdx /a /doallfiles /repair [Enter]

      CAUTION: If Norton AntiVirus cannot repair a file and you choose this option, the file will be skipped. That is, the infected files will remain on your system. If you choose this option, then run Navdx again, but this time use the /delete switch, as aforementioned.

3. Renaming or replacing the files
Depending on how many .exe or .com files were affected, either rename the files back to the original file names, replace them from a clean backup, or re-install them.

Writeup By: Yuhui Huang