Requirements
Before configuring the freeMalware Detection module, ensure the application environment meets the following baseline technical prerequisites.
Core Integration
The freeMalware Detection module operates as an extension of the core security suite and cannot function standalone. You must complete the standard integration for your framework before proceeding.
Version Requirement
To utilize the V2 configuration API (SuspiciousAppDetectionConfig) and its advanced heuristic controls, the project must be updated to the following minimum SDK versions:
Android: 18.1.0 | Flutter: 8.0.0 | React Native: 5.0.0 |
Capacitor: 3.0.0 | Cordova: 9.0.0 | KMP: 2.0.0
Application Visibility
By default, the detection engine successfully evaluates all standard, executable applications (packages with a MAIN launcher activity) without requiring broad visibility permissions on Android 11 (API level 30) and higher.
Deep Scanning (Optional)
If the specific threat model requires auditing "headless" packages (e.g., background services, daemons, or UI-less plugins), the application must explicitly request broad package visibility.
To enable this deep scanning capability, add the following to your AndroidManifest.xml:
<uses-permission android:name="android.permission.QUERY_ALL_PACKAGES" />Play Store Policy Constraint
Google classifies QUERY_ALL_PACKAGES as a highly sensitive permission. Including this permission subjects the application to an extended Google Play Policy Review. A valid justification explaining why the application requires visibility into all installed device packages must be provided to the review team.
Detection Configuration
The freeMalware Detection module is inactive by default. It activates only when at least one detection parameter is explicitly provided — either via the V2 SuspiciousAppDetectionConfig API or the legacy V1 configuration fields.
Without a valid detection configuration, no scan is performed and no threat callback is triggered.
Last updated