Trojan:Android/FakeToken

Classification

Category :

Malware

Type :

Trojan

Platform :

Android

Aliases :

Trojan:Android/FakeToken, Trojan:Android/FakeToken.A

Summary

Trojan:Android/FakeToken steals SMS messages containing mTAN numbers generated by banks to validate online transactions.

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

FakeToken.A pretends to be a mobile token generator, but actually intercepts and steals SMS messages containingM obile Transaction Authentication Numbers (mTANs), which are automatically generated by a bank and sent to a user's mobile device to validate an online transaction.

On execution, FakeToken intercepts SMS messages containing mTANs and forwards them to a remote location or to a user. Details of where the SMS messages are sent are stored in an XML configuration file. In addition, the malware may also forward details of the compromised device to a remote location.

More

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