Trojan:Android/Saiva

Classification

Category :

Malware

Type :

Trojan

Platform :

Android

Aliases :

Trojan:Android/Saiva, Trojan:Android/Saiva.A

Summary

Trojan:Android/Saiva silently sends an SMS message to a specified phone number.

Removal

Once the scan is complete, the F-Secure security product will ask if you want to uninstall the file, move it to the quarantine or keep it installed on your device.

A False Positive is when a file is incorrectly detected as harmful, usually because its code or behavior resembles known harmful programs. A False Positive will usually be fixed in a subsequent database update without any action needed on your part. If you wish, you may also:

  • Check for the latest database updates

    First check if your F-Secure security program is using the latest updates, then try scanning the file again.

  • Submit a sample

    After checking, if you still believe the file is incorrectly detected, you can submit a sample of it for re-analysis.

    Note: If the file was moved to quarantine, you need to collect the file from quarantine before you can submit it.

  • Exclude a file from further scanning

    If you are certain that the file is safe and want to continue using it, you can exclude it from further scanning by the F-Secure security product.

    Note: You need administrative rights to change the settings.

Technical Details

Trojan:Android/Saiva was discovered around Valentine.s Day in 2011 and is another malware that derives profit from SMS-sending activities.

Upon execution, it displays a fake progress bar and pretends to be performing a download; however it silently sends out SMS messages containing the text "rb9816" to a specified phone number.

It then displays a notification message in Russian for a supposed system failure. When translated to English, the message is as follows:

  • "Unfortunately there was a system failure. Restart the application again and you would find out the name of the person sending you the Valentine"

More

This malware is discussed in further detail in: Q1 2012 Mobile Threat Report (PDF).