App Blocklists
The App Blocklists layer evaluates installed applications against a locally cached list of malicious identifiers. This deterministic check matches either the exact Package Name or the SHA-256 Hash of the installed application.
You can configure both types of identifiers simultaneously, or use only one by omitting the unused parameter.
Package-Name Blocklist
This check extracts the application's unique package identifier (e.g., com.malicious.stealer) and compares it against a predefined list.
Execution: Performs a direct string comparison against the OS package manager's inventory.
Detection Constraint: This evaluation strictly matches the exact package name string. It does not detect malicious applications that have been repackaged or distributed under a different package identifier.
Result Flag: A positive match triggers the
blocklistreason. This flag takes absolute precedence: it overrides any permission or installation source heuristics and immediately halts further evaluation for that specific application.
→ View how to configure package name blocklists
Hash-Based Blocklist
This check calculates the SHA-256 hash of the target application's entire APK file and compares it against a predefined list.
Cryptographic Fingerprint
The SHA-256 hash serves as a unique cryptographic fingerprint of the entire APK file. While a package name can be easily spoofed or duplicated by different apps, the hash identifies a specific, verified malicious binary. Any internal modification to the application—such as repackaging to change its package name or resources—will result in a completely different hash.
Need broader coverage? Premium Malware Detection extends this with real-time APK reputation lookups against a continuously updated global threat database.
Execution: Reads the application's APK file from the device's storage to compute the cryptographic hash.
Result Flag: A positive match triggers the
blocklistreason and immediately halts further evaluation for that specific application.
Performance Consideration
Defining at least one hash in your configuration increases the total duration of the background scanning process, as the SDK must perform read operations on the binary files of installed applications.
Last updated