Skip to content
KitploitKITPLOIT
ToolsBlog
Log in
Submit
ToolsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

FeedsContactPrivacy© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
rasp — Packs a runtime into built APK, AAB or IPA files to detect root, jailbreak, debuggers, Frida hooks, emulators, VPN/proxy interception and repackaging at runtime. | Kitploit
Tools/GitHubGitHub/ostorlab/rasp
Android SecurityDefensive ToolsiOS SecurityMobile App PentestingReverse EngineeringPenetration TestingMobile SecurityBinary AnalysisAnti-Bot
GitHubostorlab/rasp

rasp

Packs a runtime into built APK, AAB or IPA files to detect root, jailbreak, debuggers, Frida hooks, emulators, VPN/proxy interception and repackaging at runtime.

410h 54m agoNot yet reviewed
Share
View Repository

RASP

Packer Runtime License

Runtime application self-protection (RASP) for Android and iOS apps.

rasp protects an app you have already built. It adds a small runtime to the APK, AAB or IPA, and the protected app checks the device it runs on and itself while it is in use. No change to the app's source code is needed.

https://github.com/user-attachments/assets/a43d48ed-75ec-43b1-ad76-77fc08826493

Features

  • Android and iOS: APK, AAB and IPA.
  • No source code changes: protect the build you already ship.
  • Choose the checks: turn on only the check groups that fit your users.
  • Detects: root and jailbreak, debuggers, Frida and other hooking, emulators, app virtualizers, network interception (VPN tunnels and proxies), tampering with the runtime's code, and repackaged copies.
  • Runs all the time: the checks run when the app starts, then every 30 to 90 seconds, with the wait between runs randomized, until the app exits.
  • Events on the Ostorlab platform: protect apps and see their events in Mobile ADR (Mobile Application Detection & Response).

How it works

your app (APK / AAB / IPA)
        │
        ▼
  rasp pack --checks …        adds the runtime and writes the chosen checks into its config
        │
        ▼
protected app (unsigned)  ──▶  you sign it and ship it
        │
        ▼
on the device                  the runtime runs the chosen checks and hands the observations
                               to its plugins; a development build also logs them

A plugin is code compiled into the runtime (API, example). It can add its own checks, and it receives the observations of each run, for example to send them somewhere. A runtime built without plugins keeps the observations to itself, and a release build doesn't log them.

  • The packer (packer/, Python) adds the runtime to the app and returns it unsigned.
  • The runtime (runtime/, C++) runs inside the protected app and runs the checks.

Quick start

  1. Build the runtime for your platform (details):

    cd runtime
    cmake --preset android
    cmake --build --preset android
    

    Put the built files where the packer looks for them: see the READMEs in packer/src/rasp_packer/android/resources/ and packer/src/rasp_packer/ios/resources/.

  2. Install the packer:

    cd packer
    uv sync --locked
    
  3. Protect an app:

    uv run rasp pack app.apk --platform android --build-id my-build-1 --checks root,debugger,hooks --output app-protected.apk
    
  4. Sign app-protected.apk with your release key, then ship it.

The packer is also a Python library:

import pathlib

from rasp_packer import packer
from rasp_packer import platforms

result = packer.pack(
    app=pathlib.Path("app.ipa"),
    platform=platforms.Platform.IOS,
    output=pathlib.Path("app-protected.ipa"),
    build_id="my-build-1",
    checks=["jailbreak", "debugger", "hooks"],
)

Checks

GroupAndroidiOSDetects
root✓Root files, writable system partitions, SELinux and build properties
jailbreak✓Jailbreak files, sandbox escape and process spawning
debugger✓✓A debugger attached to the app
hooks✓✓Frida and other libraries injected into the app
integrity✓The runtime's code changed in memory
mitm✓✓VPN tunnels, and proxies on iOS
identity✓✓A repackaged copy of the app (always on)
emulator✓✓An emulator or the iOS Simulator
virtualizer✓The app running inside another app's container
  • Pass the groups with --checks (or checks= in Python). identity is always added.
  • An unknown group is skipped with a warning, so a list written for an older version still packs.
  • Without --checks, only identity runs.

Each check and the signals it reports are described in runtime/README.md.

Requirements

Protected Android appAndroid 12 (API 31) or later. The packer raises a lower minimum SDK to 31.
Protected iOS appiOS 12.0 or later
PackerPython 3.14, uv
Runtime buildCMake 4.4, Clang from LLVM 23; the Android NDK, SDK and a JDK for Android; Xcode on a Mac for iOS

Documentation

  • packer/README.md: the packer, its options, build ids and checks.
  • runtime/README.md: the runtime, each check, building and logs.
  • TODO.md: known work that isn't done yet.

Use ADR on the Ostorlab platform

Don't want to build the runtime yourself, or want to see what your protected apps find on real devices? Mobile ADR (Mobile Application Detection & Response) on the Ostorlab platform protects your apps with rasp and shows their events:

  1. Create an account on the Ostorlab platform and open Mobile ADR.

  2. Upload your APK or IPA, choose the checks, and download the protected app (Protect an app).

    Protect an app: choose the checks

  3. Sign it and ship it as usual.

  4. See the events in the Events tab: each check run on a device, what it found (root files, Frida, a VPN tunnel…), and whether the check could run (Events).

    The events of the protected apps

  5. Find every protected version of your app, with its checks and RASP release (Applications and builds).

    An app and its protected builds

Contributing

Contributions are welcome: open an issue or a pull request. Every change goes through a pull request.

  • Packer: run the checks listed in packer/README.md (format, lint, types, tests).
  • Runtime: read runtime/CONTRIBUTING.md first. It lists the rules the build enforces and the ones reviewers check.

Security

Please don't report a vulnerability in a public issue. See SECURITY.md.

License

Apache-2.0

Download Tool

Most Popular

View all →

Discover the most used tools by our community.

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 The ultimate OSINT toolkit: investigation graph, confidence scoring, alias families, map, timeline and reports. 49 modules, 400+ sites, no API keys required.

    491
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    GhostLock One-Tap Execution App (CVE-2026-43499)

    462
  • 3

    opencti

    opencti-platform/opencti

    Open Cyber Threat Intelligence Platform

    345
  • 4

    ARTEX

    baarai/artex

    LLM multi-agent autonomous penetration testing platform with planner/worker agents, asset and exploration graphs, MITM traffic recording, and vulnerability retesting.

    340
  • 5

    redforge

    cybersecurity91/redforge

    Browser-side red team toolkit with 102 offline tools for recon, payload generation, credential attacks, crypto, encoding and engagement reporting.

    306
  • 6

    estorides

    grisuno/estorides

    Aggregates 99+ free OSINT sources in parallel, resolves entities into a knowledge graph, and exports STIX 2.1, MISP, or GraphML with LLM-assisted analysis.

    292

Explore all tools

Browse our collection of tools

View all tools →