Perl.Santy.C

Printer Friendly Page

Discovered: December 25, 2004
Updated: February 13, 2007 12:31:17 PM
Also Known As: WORM_SANTY.F [Trend Micro]
Type: Worm
Systems Affected: UNIX



Perl.Santy.C is a worm written in Perl script that attempts to spread to Web servers running versions of the phpBB 2.x bulletin board software prior to 2.0.11, which are vulnerable to the PHPBB Viewtopic.PHP PHP Script Injection Vulnerability (BID 10701 ). It uses Google search to find potential new infection targets.

Antivirus Protection Dates

  • Initial Rapid Release version December 26, 2004
  • Latest Rapid Release version September 28, 2010 revision 054
  • Initial Daily Certified version December 26, 2004
  • Latest Daily Certified version September 28, 2010 revision 036
  • Initial Weekly Certified release date December 29, 2004

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


Technical Description


When Perl.Santy.C is executed, it does the following:

  1. Tries to obtain scripts from other compromised forums.

    Possible filenames of the script include:

    • spy.gif
    • spybot.txt
    • php.txt
    • adfkgnnodfijg
    • bot
    • bot.txt
    • bot.txt.1
    • dry.scp
    • ssh.a
    • terrorbot.txt
    • terrorbot.txt.1
    • unbot.txt
    • unbot.txt.1
    • unbot.txt.2
    • unbot.txt.3
    • unworm.txt
    • unworm.txt.1
    • unworm.txt.2
    • unworm.txt.3
    • worm1.txt
    • worm.txt
    • worm.txt.1
    • ownz.txt
    • zone.txt

      NOTE: At the time of creating this writeup, the Name Server of the specified domain has been updated and the aforementioned files are not avialbe on the new server.

  2. Searches for "viewtopic.php" using the Google search engine to generate a list of possible infection targets.

  3. Saves the search result into a file, the filename is a random number between 0 to 9999.

  4. Attempts to start an IRC bot to connect to a specified server on TCP port 6667 and gives unauthorized access to the remote hacker.

    Scans the following ports:

    • 44464
    • 4444
    • 14589
    • 666
    • 6666
    • 6968
    • 26092
    • 530
    • 46256
    • 31337
    • 2222
    • 3879
    • 30464
    • 40193
    • 36864
    • 33270
    • 36864
    • 40193
    • 30464
    • 8008
    • 1234
    • 6969
    • 7788
    • 1524
    • 10000
    • 12321
    • 43690
    • 3333
    • 9999
    • 8975
    • 16705
    • 2313
    • 21317
    • 36864
    • 13330
    • 58821
    • 6682
    • 5678
    • 45295
    • 65535
    • 26112
    • 7512
    • 24876
    • 9191
    • 5321
    • 50766
    • 1492
    • 12345
    • 12346
    • 6969
    • 6970
    • 12666
    • 1666
    • 80
    • 21
    • 23
    • 25
    • 110
    • 5252
    • 9988
    • 41254
    • 5074
    • 139
    • 44123

      Note: If any of the aforementioned ports are opened, the worm will send a message to the remote hacker, which may cause another attack later.

  5. Attempts to exploit the PHPBB Viewtopic.PHP PHP Script Injection Vulnerability (BID 10701) to obtain access to the remote Web server.


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.


Removal


The following instructions pertain to all current and recent Symantec antivirus products, including the Symantec AntiVirus and Norton AntiVirus product lines.

  1. Update the virus definitions.
  2. Run a full system scan and delete all the files detected as Perl.Santy.C.
  3. If necessary, update phpBB to 2.0.11 or above.

For specific details on each of these steps, read the following instructions.

1. To update the virus definitions
Symantec Security Response fully tests all the virus definitions for quality assurance before they are posted to our servers. There are two ways to obtain the most recent virus definitions:
  • Running LiveUpdate, which is the easiest way to obtain virus definitions: These virus definitions are posted to the LiveUpdate servers once each week (usually on Wednesdays), unless there is a major virus outbreak. To determine whether definitions for this threat are available by LiveUpdate, refer to the Virus Definitions (LiveUpdate).
  • Downloading the definitions using the Intelligent Updater: The Intelligent Updater virus definitions are posted daily. You should download the definitions from the Symantec Security Response Web site and manually install them. To determine whether definitions for this threat are available by the Intelligent Updater, refer to the Virus Definitions (Intelligent Updater).

    The Intelligent Updater virus definitions are available: Read "How to update virus definition files using the Intelligent Updater" for detailed instructions.

2. To scan for and delete the infected files
  1. Start your Symantec antivirus program and make sure that it is configured to scan all the files.
  2. Run a full system scan.
  3. If any files are detected as infected with Perl.Santy.C, click Delete.