Singlejump.K is Symbian SIS file trojan that replaces system files and some third party applications with corrupted binaries from other symbian trojans. These components cause the device to reboot if executed and prevent the phone from booting, so if your phone is infected with Singlejump.K, it is critical not to reboot the phone. Singlejump.K also sends SymbOS/Mabir.A to the first device it finds over Bluetooth.
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.
Spreading in: Security+-+Application.SIS
Singlejump.K replaces built in and third party applications with components that cause the device to reboot if executed. The device will then fail to boot at that point.
Singlejump.K uses modified Cabir to spread other trojans. Instead of sending a copy of itself it loads SIS files installed by Singlejump.K and sends it to the first phone it finds within range of Bluetooth.
The above is the combined result of the different malware components dropped by Singlejump.K. These components are from following Trojans and viruses: