At K7 Labs, we recently found four malicious apps on Google Play Store that masquerade themselves as camera apps. While the “Arthur Camera” ( app had 50,000+ downloads; the “Apple Camera” ( app had 1,000+ downloads; the “Fire Camera” ( app had 10,000+ downloads and the “Remarkable Camera” ( app had 1000+ downloads. At the time of publishing, all the above mentioned apps had been removed from the Google Play Store.

Figure 1: Malicious Camera Apps from Google Play Store

Deeper analysis revealed that all these four apps were using the same evasion technique; they were using an encrypted payload from the app’s ”assets” folder as shown in Figure 2.

In this blog, we will be analyzing the sample

Figure 2: Encrypted dex

The “Fire Camera” app decrypts the malicious payload “36290” from the app’s “assets” folder to an executable dex format and loads the decrypted dex using DexClassLoader from within the classes.dex file – a clear attempt to complicate reversing the application. The code for decrypting the malicious payload (passed as an argument to the DexClassLoader function) and loading the decrypted dex can be seen in the image below.

Figure 3: DexClassLoader loading decrypted dex

Figure 4 shows that the encrypted data file name has been assigned to a variable. The hex equivalent of this variable is used as the decryption key, “36290” which is “0x8DC2” in case of

Figure 4: Code showing the file name being assigned to a variable
Figure 5: Code that decrypts the malicious payload

At run time, the decrypted and loaded dex, 36290.dex in this case, gets prepended with the letter “o” in the file name as shown in the logcat image below.

Figure 6: logcat image showing the dex file name prepended with “o”

This might have been done to avoid being identified based on the file name from the app’s “assets” folder and also for persistence. Let’s inspect the newly added “o36290.dex” file.

On installation, this app verifies whether the Wi-Fi connection is enabled, as seen in the image below, which is quite unusual for these types of apps. If Wi-Fi is enabled, this app automatically disables Wi-Fi on the user’s phone, thereby forcing the user to manually activate mobile data for connectivity as shown in Figure 8.

Figure 7: IDA Pro screenshot showing the enabling of Wi-Fi
Figure 8: IDA Pro screenshot showing Wi-Fi being turned off

When the app is run, it makes a request to allow the app to read all the “Notifications” and continuously keeps prompting until the user says “ALLOW” as shown in Figure 9. 

Figure 9: Notification Access

Normally, malicious apps initiate their malicious behaviour immediately after installation without waiting for user interaction. But “Fire Camera” app is a little more evasive and unleashes its maliciousness only when the user begins to use the app. For instance, we noticed that whenever the user opens an image through the app and uses the crop functionality, the app collects device information in the background and sends it to the server –hxxp://

Figure 10: Network Packet containing the URL

The device information collected are as follows:

  • Phone model
  • Network operator
  • App ID
  • Wi-Fi status

The connection is then redirected to hxxp://

Figure 11: Network Packets containing exfiltrated data

This server then responds to the device by sending a list of URLs.





The final objective of the app is to get the user to subscribe to its service which it does by mimicking the user’s activity without the user’s knowledge. Many users have complained about the same in the review section as shown below.

Figure 12: User reviews from Google Play Store


  • Carefully read the user reviews before installing the apps.
  • Do not install the apps from unknown sources.
  • Ensure you scan the downloaded apps, irrespective of the source, with a reputable security product like K7 Mobile Security so as to protect your device and data. Ensure you always keep it up-to-date. 




Indicators of Compromise (IOCs)

App NameHashDetection Name A1E7A2FF2790023ED3E66E3BC7FB41EC Trojan ( 00556e411 ) B346990512B0A86B5CE2B0AB60462373 Trojan ( 00556fb61 ) 0B5FF079E11980A3C7A5B5FFB012A626 Trojan ( 0001140e1 ) 5CD36399C4039AF85848C6F05C7F5C79 Trojan ( 00556fb61 )

Payload IOC’s

File NameHash Detection Name
54452.dex CD78F68C6A9714B42D5F12941CF5B167 Trojan ( 005584d21 )
36290.dex F8E13CC7D3968FCABF7D1938826B0B45 Trojan ( 005046f51 )
43702.dex 0B688C60A894839069C272CE77F72A5C Trojan ( 005584d21 )
59138.dex 97BDE0AD69EB9C8582083D5C6EDA515E Trojan ( 005584d21 )

Like what you're reading? Subscribe to our top stories.

If you want to subscribe to our monthly newsletter, please submit the form below.