> For the complete documentation index, see [llms.txt](https://docs.talsec.app/freerasp/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.talsec.app/freerasp/freemalwaredetection/requirements.md).

# Requirements

Before starting the integration, please ensure the following steps are completed.

{% stepper %}
{% step %}

## Integrate the freeRASP SDK

Integrating [**freeRASP**](https://docs.talsec.app/freerasp) into your project is essential, as it provides the foundation for all malware detection functionalities. For detailed instructions, refer to the [freeRASP Integration Guide](https://docs.talsec.app/freerasp/integration). 

If you have already integrated the SDK, you can skip this step and proceed to the next section.

{% hint style="info" %}
Malware Detection is available starting from: 

* **freeRASP 12.0.0 on Android**
* **freeRASP 6.8.0 on Flutter**
* **freeRASP 3.10.0 on React Native**
* **freeRASP 1.6.0 on Capacitor**
* **freeRASP 6.4.0 on Cordova**
  {% endhint %}
  {% endstep %}

{% step %}

## (Optionally) Allow Permission for Querying All Packages

This step is **optional**, depending on the level of detection you wish to implement. The Malware Detection feature can scan all executable applications (with the [**MAIN**](https://developer.android.com/reference/android/content/Intent#ACTION_MAIN) entry point defined) without any additional permissions.

If you want to extend the detection capabilities to all packages (services, daemons, ...), you have to require the [**android.permission.QUERY\_ALL\_PACKAGES**](https://developer.android.com/reference/android/Manifest.permission#QUERY_ALL_PACKAGES) in your application's Manifest file. 

{% hint style="warning" %}
Be aware that this permission is a special subject to the [Google Play Review process](https://support.google.com/googleplay/android-developer/answer/10158779?hl=en).
{% endhint %}
{% endstep %}
{% endstepper %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.talsec.app/freerasp/freemalwaredetection/requirements.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.