At least one step of the analysis has failed, we have been notified. Don't worry, the devil is in the details.
Something seems to be broken? Contact us!
1/59
Threat
com.amaze.filemanager
Amaze
Analyzed on 2021-11-09T19:37:43.306134
11
permissions
9
activities
10
services
1
receivers
194
domains
File sums
| MD5 | 83c68a27d921efcbb509097b7721b506 | |
| SHA1 | 200f7401daef7bc81acf31846ee09ebcb61012c5 | |
| SHA256 | 72547546841778ba28763058399aa34eaf20289adfc10aa06ddf39aca6a67500 | |
| Size | 8.7MB |
APKiD
Information computed with APKiD.
| /tmp/tmpkwzezp7f!classes.dex | |
| anti_vm |
|
| anti_debug |
|
| compiler |
|
SSdeep
Information computed with ssdeep.
| APK file | 196608:AdOwZtrLnJNkEGXINNaTgjIUlBL/VOyzyLTAtG4:1EqINqwDLolYtZ | |
| Manifest | 384:GRwKu5niG6pyOZ/pUQt9funOefAty1gwgRyCe4FkCpmVBVZSSxktC6i8SU:Wu5iG6… | |
| classes.dex | 49152:y8G7ZXtZGygHYI5EjXEpSNhDdUzZgadKbDBmAomzk2eI2VpT1WZzB9uv0wbmS/U… |
Dexofuzzy
Information computed with Dexofuzzy.
| APK file | 6144:g0GruceD4gBCNCNXPqYC/IijXrb8bH7k9S0sUkKsgHJns5xPCXqYlNYsRLr/JuJ:… | |
| classes.dex | 6144:g0GruceD4gBCNCNXPqYC/IijXrb8bH7k9S0sUkKsgHJns5xPCXqYlNYsRLr/JuJ:… |
APK details
Information computed with AndroGuard and Pithus.
Certificate details
Information computed with AndroGuard.
File Analysis
Information computed with MobSF.
| Findings | Files |
|---|---|
| Hardcoded Keystore found. |
res/2K.bks |
Manifest analysis
Information computed with MobSF.
| Medium | Application Data can be Backed up[android:allowBackup=true] This flag allows anyone to backup your application data via adb. It allows users who have enabled USB debugging to copy application data off of the device. |
| High | Launch Mode of Activity (com.amaze.filemanager.ui.activities.MainActivity) is not standard. An Activity should not be having the launch mode attribute set to "singleTask/singleInstance" as it becomes root Activity and it is possible for other applications to read the contents of the calling Intent. So it is required to use the "standard" launch mode attribute when sensitive information is included in an Intent. |
| High | Activity (com.amaze.filemanager.ui.activities.PreferencesActivity) is not Protected.An intent-filter exists. An Activity is found to be shared with other apps on the device therefore leaving it accessible to any other application on the device. The presence of intent-filter indicates that the Activity is explicitly exported. |
| High | Activity (com.amaze.filemanager.ui.activities.TextEditorActivity) is not Protected.An intent-filter exists. An Activity is found to be shared with other apps on the device therefore leaving it accessible to any other application on the device. The presence of intent-filter indicates that the Activity is explicitly exported. |
| High | Activity (com.amaze.filemanager.ui.activities.DatabaseViewerActivity) is not Protected.An intent-filter exists. An Activity is found to be shared with other apps on the device therefore leaving it accessible to any other application on the device. The presence of intent-filter indicates that the Activity is explicitly exported. |
| High | Service (com.amaze.filemanager.asynchronous.services.ftp.FtpService) is Protected by a permission, but the protection level of the permission should be checked.Permission: com.amaze.filemanager.permission.CONTROL_FTP_SERVERprotectionLevel: dangerous [android:exported=true] A Service is found to be shared with other apps on the device therefore leaving it accessible to any other application on the device. It is protected by a permission. However, the protection level of the permission is set to dangerous. This means that a malicious application can request and obtain the permission and interact with the component. If it was set to signature, only applications signed with the same certificate could obtain the permission. |
| High | Service (com.amaze.filemanager.asynchronous.services.ftp.FtpTileService) is Protected by a permission, but the protection level of the permission should be checked.Permission: android.permission.BIND_QUICK_SETTINGS_TILE [android:exported=true] A Service is found to be shared with other apps on the device therefore leaving it accessible to any other application on the device. It is protected by a permission which is not defined in the analysed application. As a result, the protection level of the permission should be checked where it is defined. If it is set to normal or dangerous, a malicious application can request and obtain the permission and interact with the component. If it is set to signature, only applications signed with the same certificate can obtain the permission. |
| High | Broadcast Receiver (com.amaze.filemanager.asynchronous.services.ftp.FtpReceiver) is Protected by a permission, but the protection level of the permission should be checked.Permission: com.amaze.filemanager.permission.CONTROL_FTP_SERVERprotectionLevel: dangerous [android:exported=true] A Broadcast Receiver is found to be shared with other apps on the device therefore leaving it accessible to any other application on the device. It is protected by a permission. However, the protection level of the permission is set to dangerous. This means that a malicious application can request and obtain the permission and interact with the component. If it was set to signature, only applications signed with the same certificate could obtain the permission. |
Browsable activities
Information computed with MobSF.
| com.amaze.filemanager.ui.activities.MainActivity |
Schemes: com.amaze.filemanager:// Mime types: */* application/zip application/rar application/x-gzip application/x-rar-compressed application/x-bzip2 application/x-xz application/x-7z-compressed resource/folder |
Main Activity
Information computed with AndroGuard.
|
Activities
Information computed with AndroGuard.
|
Receivers
Information computed with AndroGuard.
|
Services
Information computed with AndroGuard.
|
Sample timeline
| Oldest file found in APK | Jan. 1, 1981, 1:01 a.m. |
| Latest file found in APK | Jan. 1, 1981, 1:01 a.m. |
| Certificate valid not before | Nov. 11, 2014, 9:41 p.m. |
| First submission on VT | Nov. 9, 2021, 6:27 p.m. |
| Last submission on VT | Nov. 9, 2021, 6:27 p.m. |
| Upload on Pithus | Nov. 9, 2021, 7:37 p.m. |
| Certificate valid not after | Nov. 5, 2039, 9:41 p.m. |
VirusTotal
| Score | 1/59 |
| Report | https://www.virustotal.com/gui/file/72547546841778ba28763058399aa34eaf20289adfc10aa06ddf39aca6a67500/detection |
NIAP analysis
Information computed with MobSF.
| FCS_RBG_EXT.1.1 | The application invoke platform-provided DRBG functionality for its cryptographic operations. Random Bit Generation Services |
| FCS_STO_EXT.1.1 | The application does not store any credentials to non-volatile memory. Storage of Credentials |
| FCS_CKM_EXT.1.1 | The application implement asymmetric key generation. Cryptographic Key Generation Services |
| FDP_DEC_EXT.1.1 | The application has access to ['network connectivity']. Access to Platform Resources |
| FDP_DEC_EXT.1.2 | The application has access to no sensitive information repositories. Access to Platform Resources |
| FDP_NET_EXT.1.1 | The application has user/application initiated network communications. Network Communications |
| FDP_DAR_EXT.1.1 | The application implement functionality to encrypt sensitive data in non-volatile memory. Encryption Of Sensitive Application Data |
| FMT_MEC_EXT.1.1 | The application invoke the mechanisms recommended by the platform vendor for storing and setting configuration options. Supported Configuration Mechanism |
| FTP_DIT_EXT.1.1 | The application does encrypt some transmitted data with HTTPS/TLS/SSH between itself and another trusted IT product. Protection of Data in Transit |
| FCS_RBG_EXT.2.1 FCS_RBG_EXT.2.2 |
The application perform all deterministic random bit generation (DRBG) services in accordance with NIST Special Publication 800-90A using Hash_DRBG. The deterministic RBG is seeded by an entropy source that accumulates entropy from a platform-based DRBG and a software-based noise source, with a minimum of 256 bits of entropy at least equal to the greatest security strength (according to NIST SP 800-57) of the keys and hashes that it will generate. Random Bit Generation from Application |
| FCS_CKM.1.1(1) | The application generate asymmetric cryptographic keys in accordance with a specified cryptographic key generation algorithm RSA schemes using cryptographic key sizes of 2048-bit or greater. Cryptographic Asymmetric Key Generation |
| FCS_CKM.1.1(3) FCS_CKM.1.2(3) |
A password/passphrase shall perform [Password-based Key Derivation Functions] in accordance with a specified cryptographic algorithm.. Password Conditioning |
| FCS_COP.1.1(1) | The application perform encryption/decryption in accordance with a specified cryptographic algorithm AES-CBC (as defined in NIST SP 800-38A) mode or AES-GCM (as defined in NIST SP 800-38D) and cryptographic key sizes 256-bit/128-bit. Cryptographic Operation - Encryption/Decryption |
| FCS_COP.1.1(2) | The application perform cryptographic hashing services not in accordance with FCS_COP.1.1(2) and uses the cryptographic algorithm RC2/RC4/MD4/MD5. Cryptographic Operation - Hashing |
| FCS_COP.1.1(3) | The application perform cryptographic signature services (generation and verification) in accordance with a specified cryptographic algorithm RSA schemes using cryptographic key sizes of 2048-bit or greater. Cryptographic Operation - Signing |
| FCS_COP.1.1(4) | The application perform keyed-hash message authentication with cryptographic algorithm ['HMAC-SHA-256', 'HMAC-SHA1'] . Cryptographic Operation - Keyed-Hash Message Authentication |
| FCS_HTTPS_EXT.1.1 | The application implement the HTTPS protocol that complies with RFC 2818. HTTPS Protocol |
| FCS_HTTPS_EXT.1.2 | The application implement HTTPS using TLS. HTTPS Protocol |
| FCS_HTTPS_EXT.1.3 | The application notify the user and not establish the connection or request application authorization to establish the connection if the peer certificate is deemed invalid. HTTPS Protocol |
| FIA_X509_EXT.1.1 | The application invoked platform-provided functionality to validate certificates in accordance with the following rules: ['The application validate a certificate path by ensuring the presence of the basicConstraints extension and that the CA flag is set to TRUE for all CA certificates', 'The application validate the revocation status of the certificate using the Online Certificate Status Protocol (OCSP) as specified in RFC 2560 or a Certificate Revocation List (CRL) as specified in RFC 5759 or an OCSP TLS Status Request Extension (i.e., OCSP stapling) as specified in RFC 6066']. X.509 Certificate Validation |
| FIA_X509_EXT.1.2 | The application treat a certificate as a CA certificate only if the basicConstraints extension is present and the CA flag is set to TRUE. X.509 Certificate Validation |
| FIA_X509_EXT.2.1 | The application use X.509v3 certificates as defined by RFC 5280 to support authentication for HTTPS , TLS. X.509 Certificate Authentication |
| FIA_X509_EXT.2.2 | When the application cannot establish a connection to determine the validity of a certificate, the application allow the administrator to choose whether to accept the certificate in these cases or accept the certificate ,or not accept the certificate. X.509 Certificate Authentication |
| FCS_CKM.1.1(2) | The application shall generate symmetric cryptographic keys using a Random Bit Generator as specified in FCS_RBG_EXT.1 and specified cryptographic key sizes 128 bit or 256 bit. Cryptographic Symmetric Key Generation |
Code analysis
Information computed with MobSF.
Map computed by Pithus.
Domains analysis
Information computed with MobSF.