> 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/freerasp/wiki/threat-detection/multi-instance-detection-android-devices-only.md).

# Multi-Instance detection \[Android devices only]

Multi-instance refers to the ability to launch multiple instances of the same application—either intentionally (such as through app cloning or multi-user modes) or unintentionally (due to a malicious attack or system bug). Each instance may run in a separate process, which can lead to security, privacy, or data consistency issues—especially in sensitive applications like finance, messaging, or enterprise tools.

Currently, detection of multi-instance using [Parallel Space](https://play.google.com/store/apps/details?id=com.lbe.parallel.intl\&hl=en) is supported.

Below are code snippets demonstrating passcode detection across various platforms:

```dart
// Android multi instance check
override fun onMultiInstance() {
    TODO("Not yet implemented")
}

// Flutter multi instance detection
onMultiInstance: () => print("Multi instance detected")

// Cordova multi instance detection
multiInstance: () => {
    // Place your reaction here
}

// React Native multi instance detection
multiInstance: () => {
    // Place your reaction here
}

// Capacitor multi instance detection
multiInstance: () => {
    // Place your reaction here
}
```

{% hint style="info" %}
**Recommended action:** Log the event on your BE and optionally react to it.
{% endhint %}

### Read More <a href="#read-more" id="read-more"></a>

What is multi-instacing, why is it an issue and how to detect it?

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th data-hidden data-card-cover data-type="files"></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td>Introducing Multi-Instancing Detection for freeRASP</td><td><a href="https://3557356308-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQ2PxZTOjhquOxcxftTrm%2Fuploads%2FeP9FWzKmOs3mK0XG3Pf8%2Fimage.png?alt=media&amp;token=972d84a1-4f5e-4179-af18-991fc05b72ce">image.png</a></td><td><a href="https://docs.talsec.app/appsec-articles/articles/introducing-multi-instancing-detection-for-freerasp">Introducing Multi-Instancing Detection for freeRASP</a></td></tr></tbody></table>


---

# 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 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/freerasp/wiki/threat-detection/multi-instance-detection-android-devices-only.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 `automate deployments from our CI pipeline` 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.
