1. /
  2. Security Response/
  3. W32.Rinbot.A

W32.Rinbot.A

Risk Level 2: Low

Discovered:
February 16, 2007
Updated:
February 23, 2007 11:04:08 PM
Type:
Worm
Infection Length:
211,968 bytes or 206,848 bytes
Systems Affected:
Windows 98, Windows 95, Windows XP, Windows Me, Windows NT, Windows 2000
CVE References:
CVE-2002-1123, CVE-2006-2630, CVE-2006-3439
When the worm executes, it creates a copy of itself on the compromised computer including, but not limited to one of the following:
%System%\jwmngr.exe
%System%\secsvc.exe
%System%\devenv.exe

Next, the worm creates registry entries including, but not limited to the following registry entries, so that it runs whenever Windows starts:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run\"JW Manager" = "%System%\jwmngr.exe"
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run\"Security Service" = "%System%\secsvc.exe"
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run\"Development Environment" = "%System%\devenv.exe"

The worm then attempts to copy itself to the IPC$ network share. If this is password protected, it tries to gain access using user names and passwords from the following list:
  • 007
  • 123
  • 1234
  • 2000
  • 2001
  • 2002
  • 2003
  • 2004
  • 12345
  • 123456
  • 1234567
  • 12345678
  • 123456789
  • 1234567890
  • access
  • accounting
  • accounts
  • administrador
  • administrateur
  • administrat
  • adm
  • admins
  • admin
  • administrator
  • asd
  • backup
  • bill
  • bitch
  • blank
  • bob
  • brian
  • changeme
  • chris
  • cisco
  • compaq
  • control
  • databasepass
  • data
  • databasepassword
  • database
  • db1
  • db1234
  • db2
  • dbpassword
  • dbpass
  • default
  • dell
  • demo
  • domain
  • domainpass
  • domainpassword
  • eric
  • exchange
  • fred
  • fuck
  • george
  • god
  • guest
  • hell
  • hello
  • home
  • homeuser
  • ian
  • ibm
  • internet
  • intranet
  • jen
  • joe
  • john
  • kate
  • katie
  • lan
  • lee
  • linux
  • loginpass
  • login
  • luke
  • mail
  • main
  • mary
  • mike
  • neil
  • nokia
  • none
  • null
  • oem
  • oeminstall
  • oemuser
  • office
  • oracle
  • orainstall
  • outlook
  • pass1234
  • password1
  • passwd
  • pass
  • password
  • peter
  • pwd
  • qaz
  • qwe
  • qwerty
  • root
  • sam
  • server
  • sex
  • siemens
  • slut
  • sqlpassoainstall
  • sql
  • staff
  • student
  • sue
  • susan
  • system
  • teacher
  • technical
  • test
  • unix
  • user
  • web
  • win2000
  • win2k
  • win98
  • windows
  • winnt
  • winpass
  • winxp
  • www
  • zxc

Note: This list is not limited to the above passwords.

The worm then opens a back door and attempts to connect to a predetermined set of IRC servers, including but not limited to any of the following IRC servers using TCP port 8080:
  • z3n.phatcamp.org
  • x.xerro.net
  • x.pennysheet.com
  • x.sans-security.org

The worm allows an attacker to perform the following actions on the compromised computer:
  • Gather system information
  • Scan local network for machines to infect
  • Run a socks4 proxy
  • Perform a DDoS attack on a specified host
  • Download and execute a specified file
  • Run an HTTP or FTP server
  • Update itself
  • Steal CD keys for certain games

The worm then attempts to spread by exploiting the following vulnerabilities:
Symantec Client Security and Symantec AntiVirus Elevation of Privilege (BID 18107)
Microsoft Windows Server Service Remote Buffer Overflow Vulnerability (BID 19409)
Microsoft SQL Server User Authentication Remote Buffer Overflow Vulnerability (BID 5411)

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: Stephen Doherty
Summary| Technical Details| Removal

Search Threats

Search by name
Example: W32.Beagle.AG@mm
STAR Antimalware Protection Technologies
Internet Security Threat Report
Symantec DeepSight Screensaver