Your review is Submitted Successfully. ×
Pranav Sayta@techwizard
Sep 08, 2005 04:54 PM, 4426 Views
(Updated Sep 08, 2005)
How to get out from Caribe Virus

SymbOS.Caribe is a proof-of-concept worm that replicates on Series 60 phones.


This 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.


Also Known As:


EPOC.Cabir, Worm.Symbian.Cabir.a, Cabir, EPOC/Cabir.A, Symb/Cabir-A, EPOC_CABIR.A


Type:


Worm


Infection Length:


15104 (caribe.sis), 11944 (caribe.app), 11498 (flo.mdl), 44 (caribe.rsc)


Systems Affected:


EPOC


Systems Not Affected:


DOS, Linux, Macintosh, Novell Netware, OS/2, UNIX, Windows 2000, Windows 3.x, Windows 95, Windows 98, Windows Me, Windows NT, Windows Server 2003, Windows XP


Damage :


Large scale e-mailing: n/a


Deletes files: n/a


Modifies files: n/a


Degrades performance: Scanning for Bluetooth devices may impact the overall performance of the device.


Causes system instability: n/a


Releases confidential info: n/a


Compromises security settings: n/a


Distribution :


Subject of email: n/a


Name of attachment: n/a


Size of attachment: n/a


Time stamp of attachment: n/a


Ports: n/a


Shared drives: n/a


Target of infection: n/a


Technical Details :-


SymbOS.Cabir 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 caribe?


If the user chooses Install, SymbOS.Cabir is installed and executed, displaying the message:


Caribe-VZ/29a


The worm creates the following files on the phone:


\SYSTEM\APPS\CARIBE\CARIBE.APP


\SYSTEM\APPS\CARIBE\CARIBE.RSC


\SYSTEM\APPS\CARIBE\FLO.MDL


C:\SYSTEM\SYMBIANSECUREDATA\CARIBESECURITYMANAGER\CARIBE.APP


C:\SYSTEM\SYMBIANSECUREDATA\CARIBESECURITYMANAGER\CARIBE.RSC


C:\SYSTEM\SYMBIANSECUREDATA\CARIBESECURITYMANAGER\CARIBE.SIS


C:\SYSTEM\RECOGS\FLO.MDL


C:\SYSTEM\INSTALLS\CARIBE.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.


Removal Instructions :


To remove SymbOS.Cabir:


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\CARIBE directory.


Delete the files CARIBE.APP, CARIBE.RSC, and FLO.MDL from the \CARIBE directory.


Go to the C:\SYSTEM\SYMBIANSECUREDATA\CARIBESECURITYMANAGER directory.


Delete the files CARIBE.APP, CARIBE.RSC, and CARIBE.SIS.


Go to the C:\SYSTEM\RECOGS directory.


Delete the file, FLO.MDL.


Go to the C:\SYSTEM\INSTALLS directory.


Delete the file, CARIBE.SIS.


Note: You cannot delete the file CARIBE.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 CARIBE.RSC file.


Additional information:


I recommend the following to protect against this threat:


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.

(1)
Please fill in a comment to justify your rating for this review.
Post
Question & Answer