- January 27, 2012
- January 30, 2012 12:44:30 PM
Android package files
The Trojan is available for download in the Android Market as an application package from the following publishers:
- iApps7 Inc.
- Ogre Games
Applications from these publishers include but are not limited to the following:
When the Trojan is being installed, it may request permissions to perform the following actions:
- Access information about networks
- Access information about the WiFi state
- Access location information, such as Cell-ID, GPS, or WiFi
- Allows access to install and uninstall shortcuts
- Allows access to read settings on the device
- Allows access to the list of accounts in the Accounts Service
- Check the phone's current state
- Make the phone vibrate
- Open network connections
- Prevent processor from sleeping or screen from dimming
- Read and write access of the user's browsing history and bookmarks
- Start once the device has finished booting
The listed apps all contain a similar package called com.apperhand which has functionality similar to com.plankton found in Android.Tonclank
and may perform the following actions on the compromised device:
- Copy bookmarks on the device
- Copy opt out details
- Copy push notifications
- Copy shortcuts
- Identify the last executed command
- Modify the browser's home page
- Steal build information (for example: brand, device, manufacturer, model, OS, etc.)
The Trojan may attempt to connect to the following remote locations:
Applications from Ogre Games have the additional functionality to retrieve the following information from the device:
- Android ID
- MAC address
- SIM serial number
Symantec Security Response encourages all users and administrators to adhere to the following basic security "best practices":
- Use a firewall to block all incoming connections from the Internet to services that should not be publicly available. By default, you should deny all incoming connections and only allow services you explicitly want to offer to the outside world.
- 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.
- Ensure that programs and users of the computer use the lowest level of privileges necessary to complete a task. When prompted for a root or UAC password, ensure that the program asking for administration-level access is a legitimate application.
- Disable AutoPlay to prevent the automatic launching of executable files on network and removable drives, and disconnect the drives when not required. If write access is not required, enable read-only mode if the option is available.
- Turn off file sharing if not needed. If file sharing is required, use ACLs and password protection to limit access. Disable anonymous access to shared folders. Grant access only to user accounts with strong passwords to folders that must be shared.
- Turn off and remove unnecessary services. By default, many operating systems install auxiliary services that are not critical. These services are avenues of attack. If they are removed, threats have less avenues of attack.
- If a 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.
- Configure your email server to block or remove email that contains file attachments that are commonly used to spread threats, such as .vbs, .bat, .exe, .pif and .scr files.
- Isolate compromised computers quickly to prevent threats from spreading further. 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.
- If Bluetooth is not required for mobile devices, it should be turned off. If you require its use, ensure that the device's visibility is set to "Hidden" so that it cannot be scanned by other Bluetooth devices. If device pairing must be used, ensure that all devices are set to "Unauthorized", requiring authorization for each connection request. Do not accept applications that are unsigned or sent from unknown sources.
- For further information on the terms used in this document, please refer to the Security Response glossary.
Note: On May 14, 2015, modifications will be made to the threat write-ups to streamline the content. The Threat Assessment section will no longer be published as this section is no longer relevant to today's threat landscape. The Risk Level will continue to be the main threat risk assessment indicator.
Writeup By: Nino Gutierrez and Asuka Yamamoto