SymbOS.Commwarrior.A

SymbOS.Cabir.O is a proof-of-concept worm that replicates on Series 60 phones. The worm is a minor variant of SymbOS.Cabir.

The only differences are:

• The worm spreads as mobile.SIS.
• The worm displays the following message after infection:
  
  mobile

The worm repeatedly sends itself to the first Bluetooth-enabled device that it can find, regardless of the type of device. For example, even a Bluetooth-enabled printer will be attacked if it is within range.

The worm spreads as a .SIS file, which is installed into the APPS directory. There is no payload, apart from the vastly shortened battery life caused by the constant scanning for Bluetooth-enabled devices.

Technical Details

SymbOS.Cabir.O is transmitted through Bluetooth as a .SIS file.

When the worm arrives at a target device the following may happen:

The device displays a message similar to the following, asking the user to accept a message from a particular device:

Receive message via Bluetooth from [device name]?

The user will be notified that they have received a new message.

The user will be prompted with a message similar to the following:

Application is untrusted and may have problems. Install only if you trust provider.

If the user chooses Yes, the user will be prompted to install the worm.

Install mobile?

If the user chooses Install, the worm is installed, executed, and then displays the following message:

mobile

The worm creates the following files on the phone:

\SYSTEM\APPS\mobile\mobile.APP
\SYSTEM\APPS\mobile\mobile.RSC
\SYSTEM\APPS\mobile\FLO.MDL
C:\SYSTEM\SYMBIANSECUREDATA\mobileSECURITYMANAGER\mobile.APP
C:\SYSTEM\SYMBIANSECUREDATA\mobileSECURITYMANAGER\mobile.RSC
C:\SYSTEM\SYMBIANSECUREDATA\mobileSECURITYMANAGER\mobile.SIS
C:\SYSTEM\RECOGS\FLO.MDL
C:\SYSTEM\INSTALLS\mobile.SIS

The worm attempts to send itself to other Bluetooth-enabled device that it finds, regardless of the type of device.

The worm executes every time the device is turned on

Recommendations

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

Turn off and remove unneeded services. By default, many operating systems install auxiliary services that are not critical, such as an FTP server, telnet, and a Web server. These services are avenues of attack. If they are removed, blended threats have less avenues of attack and you have fewer services to maintain through patch updates.
If a blended 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 (for example, all Windows-based computers should have the current Service Pack installed.). Additionally, please apply any security updates that are mentioned in this writeup, in trusted Security Bulletins, or on vendor Web sites.
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.
Configure your email server to block or remove email that contains file attachments that are commonly used to spread viruses, such as .vbs, .bat, .exe, .pif and .scr files.
Isolate infected computers quickly to prevent further compromising your organization. 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.

Removal Instructions :

To remove SymbOS.Cabir.O:

Install a file manager program on the phone.
Enable the option to view the files in the system directory.
Search the drives, A through Y, for the \SYSTEM\APPS\mobile directory.
Delete the files mobile.app, mobile.rsc, and FLO.MDL from the \mobile directory.
Go to the C:\SYSTEM\SYMBIANSECUREDATA\mobileSECURITYMANAGER directory.
Delete the files mobile.app, mobile.rsc, and mobile.SIS.
Go to the C:\SYSTEM\RECOGS directory.
Delete the file, FLO.MDL.
Go to the C:\SYSTEM\INSTALLS directory.
Delete the file, mobile.SIS.

Note: You cannot delete the file mobile.rsc when the program is running.

If you cannot delete this file in steps 4 and 6, delete all the files that you can, restart the phone, and then delete the mobile.rsc file.

Additional information

If Bluetooth is not required, it should be turned off.
If you require the use of Bluetooth, ensure that the device's visibility setting is set to "Hidden" so that it can not be scanned by other Bluetooth devices.
Avoid use of device pairing. If it must be used, ensure that all paired devices are set to "Unauthorized". This requires each connection request to be authorized by the user.
Do not accept unsigned applications (no digital signature) or applications sent from unknown sources. Be absolutely sure of the origin of the application before accepting it.

More info visite http://securityresponse.symantec.com/avcenter/venc/data/symbos.cabir.o.html

Caution : we dont take any resposbilty if your phone is damamged, Experiment at your own risk.