PAGES
← all tools
◆ Reverse Engineering

Runtime Mobile Security

1.5.24 open-source

Web interface powered by Frida for manipulating Android and iOS apps at runtime, enabling class dumping, method hooking, and script injection.

source ↗ rss ↗ What is a cyber toolchain?

Summary

Runtime Mobile Security is an open-source web interface, built on Frida, that lets you manipulate Android and iOS apps at runtime, dumping loaded classes and methods, hooking calls, tracing arguments and return values, and loading custom scripts. It runs as a local Node.js application: you install Frida's CLI tools, get a Frida server running on the target device, then launch RMS from the command line and drive it through the browser. This is a fit for mobile app pentesters and reverse engineers rather than automated pipelines, since it's built around interactive, on-the-fly exploration of a running app. It sits in the same space as other Frida-based instrumentation front-ends, giving that toolkit a GUIGUIA graphical user interface, controls such as windows, buttons and menus. It lets people use software visually rather than entering commands. instead of raw scripting. Started in 2020 and still active, with 15 contributors and a release 51 days ago.

Web interface powered by Frida for manipulating Android and iOS apps at runtime, enabling class dumping, method hooking, and script injection.

How Runtime Mobile Security helps

Can you change how an app behaves without rebuilding or repatching it?

attaches to the running process through Frida and lets you hook calls or load a custom script on the fly, so behavior changes for that session only

Are the same classes and hooks available on both platforms you are testing?

drives both Android and iOS apps through the same web interface and hooking workflow once a Frida server is reachable on the device

all 5 features, with the evidence for each →

Languages

Not documented

Features

5 capabilities

Built from Runtime Mobile Security's releases, docs, README and our own runs. “Seen” marks the month we first spotted a release the vendor didn't date.

Compare with peers →

All capabilities 5 capabilities
Frida runtime compatibility shipped Provides runtime analysis capabilities for Android and iOS apps via Frida integration, including class dumping, method hooking, and script injection. 20 releases · 11 other sources · first seen Apr 2020

release 20 total

  • Enables runtime analysis compatibility with Frida 17 and later versions. 1.5.24 · Nov 2025 · source · release history
  • Adds support for Frida version 16.* 1.5.12 · Nov 2022 · source · release history
  • Adds Frida script to bypass OkHttp3 SSL pinning on Android devices 1.5.9 · Aug 2021 · source · release history
  • Adds npm install -g rms-runtime-mobile-security to install RMS as a CLI app 1.5.0 · Dec 2020 · source · release history
  • Adds web interface available at http://127.0.0.1:5000/ in the new NodeJS version 1.5.0 · Dec 2020 · source · release history
  • Adds rms (or RMS-Runtime-Mobile-Security) as the new entry point for launching the tool 1.5.0 · Dec 2020 · source · release history

docs

  • Web interface powered by Frida for manipulating Android and iOS apps at runtime, enabling class dumping, method hooking, and script injection.

example 10 total

  • Install the new CLI version globally. npm install -g rms-runtime-mobile-security 1.5.0 · Dec 2020 · source
  • Launch the RMS service to begin runtime mobile security analysis. rms 1.5.0 · Dec 2020 · source
  • Generate a hook template for a specific method in Hook Lab. In Hook Lab, select the target method and choose 'Generate Template'. 1.3.1 · Jun 2020 · source
  • Isolate native method hooks during a deep scan to reduce noise from standard Java/Kotlin calls. In the dump page, select 'native' from the loaded methods quick filters. 1.3 · Jun 2020 · source
  • Filter loaded classes to a specific vendor or internal package for targeted review. Enter the target 'package name' in the class filter button field. 1.3 · Jun 2020 · source
  • Launch RMS on custom port rms --port 9000
Service port configuration shipped Allows the service to be started on a user-defined network port to prevent conflicts with other local services. 2 releases · 1 other source · first seen Aug 2023

release

  • Adds --port CLI argument to specify a custom launch port for the RMS service 1.5.19 · Aug 2023 · source · release history
  • Changes the default listening port from 5000 to 5491 1.5.19 · Aug 2023 · source · release history

example

  • Launch RMS on a non-standard port to avoid conflicts with other local services. rms --port 8080 1.5.19 · Aug 2023 · source
iOS runtime analysis shipped Extends runtime mobile security capabilities to iOS devices. 2 releases · first seen Jul 2020

release

  • Adds Frida script to detect and check support for custom keyboards on iOS 1.5.9 · Aug 2021 · source · release history
  • Adds comprehensive support for running Runtime Mobile Security on iOS devices 1.4 · Jul 2020 · source · release history
API monitoring shipped Monitors specific Android APIs organized by category during runtime analysis, including permissions and system interfaces like Bluetooth, JSON, and Clipboard. 2 releases · first seen Jun 2020

release

  • Accessibility, Clicks, Clipboard, Compression, Bluetooth, and JSON APIs are now monitored in Android applications. 1.4.1 · Aug 2020 · source · release history
  • Adds new monitor API for Permissions to track runtime permission checks. 1.2 · Jun 2020 · source · release history
Docker container deployment shipped Enables runtime deployment of the tool within a Docker container environment. 1 release · first seen Dec 2023

release

  • Adds Docker container support for runtime deployment via PR #127 1.5.20 · Dec 2023 · source · release history

Lines in monospace are the tool's own words: help text parsed from its source, or an endpoint from its API document. Under release, a line is our summary of a dated release. Under docs, it is quoted from the tool's own documentation or website. Each links back to the source it came from.

Score card

  1. Shipping velocity releases a month, last 12 months
  2. Documentation quality release-notes rubric, 0–100
  3. Breaking-change discipline how rarely a release breaks users, and notice given
  4. Maintenance risk quiet time against its own cadence, maintainers
  5. Innovation & surface new capabilities, API and MCP surface
  6. Community health
  7. Contributor trend distinct committers, this year against last
  8. Maintainer concentration bus factor now against a year ago
  9. Issue backlog trend issues closed per issue opened, 12 months
  10. Responsiveness median time to a maintainer’s first reply

Nine scores for Runtime Mobile Security, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.

Score cards are part of every paid plan.

See plans →

Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.

How this is scored
  • Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
  • Documentation quality — the release-notes rubric published on the analytics page, unchanged.
  • Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
  • Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
  • Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
  • Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
  • Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
  • Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.

Release-note detail over time

See how much detail Runtime Mobile Security puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.

Checking release-note history…

Explore the full chart →

Releases

16 entries

  1. November 20251
  3. December 20231
  5. August 20231
  7. November 20221
  9. August 20211
  11. December 20201
  13. September 20201
  15. August 20201
  17. July 20201
  19. June 20204
  24. May 20201
  26. April 20202

    16 entries

    1. 1.5.24 Nov 15, 2025 · release notes

      Adds Frida 17+ support for Runtime Mobile Security

      └──▷ GET THIS VERSION 
      $ git clone --branch 1.5.24 https://github.com/m0bilesecurity/RMS-Runtime-Mobile-Security.git
# already have the repo? check out this version:
$ git checkout 1.5.24
      • Enables runtime analysis compatibility with Frida 17 and later versions.

      1 detail in Everything

    2. 1.5.20 Dec 26, 2023 · release notes

      Runtime Mobile Security v1.5.20 adds Docker support and NodeJS 20.10 compatibility.

      └──▷ GET THIS VERSION 
      $ git clone --branch 1.5.20 https://github.com/m0bilesecurity/RMS-Runtime-Mobile-Security.git
# already have the repo? check out this version:
$ git checkout 1.5.20
      • Adds Docker container support for runtime deployment via PR #127
      • Adds support for NodeJS 20.10.0 to address Issue #122

      2 details in Everything

    3. 1.5.19 Aug 30, 2023 · release notes

      Runtime Mobile Security v1.5.19 adds --port flag and changes default port to 5491

      └──▷ GET THIS VERSION 
      $ git clone --branch 1.5.19 https://github.com/m0bilesecurity/RMS-Runtime-Mobile-Security.git
# already have the repo? check out this version:
$ git checkout 1.5.19
      └──▷ TRY IT
      Launch RMS on a non-standard port to avoid conflicts with other local services.
      $ rms --port 8080
      • Adds --port CLI argument to specify a custom launch port for the RMS service
      • Changes the default listening port from 5000 to 5491

      2 details in Everything

    4. 1.5.12 Nov 20, 2022 · release notes

      Runtime Mobile Security v1.5.12 adds support for Frida version 16

      └──▷ GET THIS VERSION 
      $ git clone --branch 1.5.12 https://github.com/m0bilesecurity/RMS-Runtime-Mobile-Security.git
# already have the repo? check out this version:
$ git checkout 1.5.12
    5. 1.5.9 Aug 10, 2021 · release notes

      Adds Frida-based SSLSSLA cryptographic protocol for encrypting network connections, now deprecated in favor of TLS but whose name persists colloquially. Cyber tools reference it when handling HTTPS or other encrypted-channel inspection and termination. pinning bypass for Android (OkHttp3) and custom keyboard check for iOS

      └──▷ GET THIS VERSION 
      $ git clone --branch 1.5.9 https://github.com/m0bilesecurity/RMS-Runtime-Mobile-Security.git
# already have the repo? check out this version:
$ git checkout 1.5.9
      • Adds Frida script to bypass OkHttp3 SSL pinning on Android devices
      • Adds Frida script to detect and check support for custom keyboards on iOS

      2 details in Everything

    6. 1.5.0 Dec 4, 2020 · release notes

      RMS v1.5 adds npm CLI installation and rms command for Frida-powered runtime analysis.

      └──▷ GET THIS VERSION 
      $ git clone --branch 1.5.0 https://github.com/m0bilesecurity/RMS-Runtime-Mobile-Security.git
# already have the repo? check out this version:
$ git checkout 1.5.0
      └──▷ USE IT
      Install the new CLI version globally.
      shell 
      npm install -g rms-runtime-mobile-security
      Launch the RMS service to begin runtime mobile security analysis.
      shell 
      rms
      • Adds npm install -g rms-runtime-mobile-security to install RMS as a CLI app
      • Adds rms (or RMS-Runtime-Mobile-Security) as the new entry point for launching the tool
      • Adds web interface available at http://127.0.0.1:5000/ in the new NodeJS version

      3 details in Everything

    7. 1.4.2 Sep 8, 2020 · release notes

      RMS v1.4.2 adds save/reset console outputs and new FRIDA bypass scripts for SSLSSLA cryptographic protocol for encrypting network connections, now deprecated in favor of TLS but whose name persists colloquially. Cyber tools reference it when handling HTTPS or other encrypted-channel inspection and termination. pinning and System.exit()

      └──▷ GET THIS VERSION 
      $ git clone --branch 1.4.2 https://github.com/m0bilesecurity/RMS-Runtime-Mobile-Security.git
# already have the repo? check out this version:
$ git checkout 1.4.2
      • Adds a new option to save the APIs Monitor Console output
      • Adds a new option to reset the Console Logs Output
      • Adds Bypass for iOS 13 SSL Pinning and Android System.exit() as default FRIDA custom scripts

      3 details in Everything

    8. 1.4.1 Aug 5, 2020 · release notes

      Runtime Mobile Security 1.4.1 adds six new Android API monitors and improved gadget support

      └──▷ GET THIS VERSION 
      $ git clone --branch 1.4.1 https://github.com/m0bilesecurity/RMS-Runtime-Mobile-Security.git
# already have the repo? check out this version:
$ git checkout 1.4.1
      • Accessibility, Clicks, Clipboard, Compression, Bluetooth, and JSON APIs are now monitored in Android applications.
      • Gadget detection and support capabilities have been improved.

      2 details in Everything

    9. 1.4 Jul 20, 2020 · release notes

      Runtime Mobile Security v1.4 adds full port of features to iOS devices

      └──▷ GET THIS VERSION 
      $ git clone --branch 1.4 https://github.com/m0bilesecurity/RMS-Runtime-Mobile-Security.git
# already have the repo? check out this version:
$ git checkout 1.4
    10. 1.3.2 Jun 28, 2020 · release notes

      RMS 1.3.2 adds custom Frida script injection, console log modal, and beta file manager

      └──▷ GET THIS VERSION 
      $ git clone --branch 1.3.2 https://github.com/m0bilesecurity/RMS-Runtime-Mobile-Security.git
# already have the repo? check out this version:
$ git checkout 1.3.2
      • Enables loading New Custom Frida Scripts via contributions from @FSecureLABS, Mediaservice, @iddoeldor, @dzonerzy and @akabe1

      1 detail in Everything

    11. 1.3.1 Jun 13, 2020 · release notes

      RMS 1.3.1 adds method-specific hook templates in Hook Lab and a new Heap Search algorithm

      └──▷ GET THIS VERSION 
      $ git clone --branch 1.3.1 https://github.com/m0bilesecurity/RMS-Runtime-Mobile-Security.git
# already have the repo? check out this version:
$ git checkout 1.3.1
      └──▷ HOW TO FIND IT
      Generate a hook template for a specific method in Hook Lab.
      📍In Hook Lab, select the target method and choose Generate Template.
      • Adds the ability to generate a hook template for a specific method directly within the Hook Lab interface
      • Introduces a new heap search algorithm accessible via the redesigned Heap Search page

      2 details in Everything

    12. 1.3 Jun 10, 2020 · release notes

      Version 1.3 adds filtered views for loaded methods/classes and direct logging capabilities in the Runtime Mobile Security dump page.

      └──▷ GET THIS VERSION 
      $ git clone --branch 1.3 https://github.com/m0bilesecurity/RMS-Runtime-Mobile-Security.git
# already have the repo? check out this version:
$ git checkout 1.3
      └──▷ HOW TO FIND IT
      Isolate native method hooks during a deep scan to reduce noise from standard Java/Kotlin calls.
      📍In the dump page, select native from the loaded methods quick filters.
      Save active console logs to a local file for offline analysis of dynamic library loading sequences.
      📍Click the save console logs button on the dump page.
      Filter loaded classes to a specific vendor or internal package for targeted review.
      📍Enter the target package name in the class filter button field.
      • Adds executed, native, and boolean quick filters to narrow down the list of loaded methods
      • Adds a new button on the dump page to save console logs directly to a text file
      • Enables filtering loaded classes by package name with a dedicated UI button

      3 details in Everything

    13. 1.2 Jun 5, 2020 · release notes

      RMS 1.2 adds Frida script support, Permissions monitoring, and class filtering

      └──▷ GET THIS VERSION 
      $ git clone --branch 1.2 https://github.com/m0bilesecurity/RMS-Runtime-Mobile-Security.git
# already have the repo? check out this version:
$ git checkout 1.2
      • Adds bypass_flag_secure.js, hook_JNI_by_address.js, and get_ANDROID_ID.js custom Frida scripts.
      • Adds new monitor API for Permissions to track runtime permission checks.
      • Adds class filter for AndroidX components to reduce noise in class-related outputs.
      • Enables detection of FRIDA crashes within the monitored process.

      4 details in Everything

    14. 1.1 May 21, 2020 · release notes

      Adds API Monitor TAB for monitoring Android APIs and configurable extension via api_monitor.json

      └──▷ GET THIS VERSION 
      $ git clone --branch 1.1 https://github.com/m0bilesecurity/RMS-Runtime-Mobile-Security.git
# already have the repo? check out this version:
$ git checkout 1.1
      └──▷ HOW TO FIND IT
      Navigate the new monitoring interface to view API calls during runtime analysis.
      📍In the UI, go to the API Monitor TAB.
      • Adds the API Monitor TAB (accessible via UI navigation) to monitor Android APIs organized in 19 categories.
      • Enables external configuration of monitored APIs by adding classes/methods to the api_monitor.json file.

      2 details in Everything

    15. 1.0.3 Apr 19, 2020 · release notes

      New Config panel and socket-managed console output in v1.0.3

      └──▷ GET THIS VERSION 
      $ git clone --branch 1.0.3 https://github.com/m0bilesecurity/RMS-Runtime-Mobile-Security.git
# already have the repo? check out this version:
$ git checkout 1.0.3
      • Adds a new Config panel to the UI for managing tool settings
      • Changes console output transport to use a socket connection instead of standard streams
      • Introduces a new Console Output interface for displaying runtime results

      3 details in Everything

    16. v1.0.1 Apr 4, 2020 · release notes

      v1.0.1 adds experimental Heap Search, Docker support, package auto-complete, and remote device config

      └──▷ GET THIS VERSION 
      $ git clone --branch v1.0.1 https://github.com/m0bilesecurity/RMS-Runtime-Mobile-Security.git
# already have the repo? check out this version:
$ git checkout v1.0.1
      • Adds Heap Search (experimental) for finding objects in the heap
      • Adds Docker support to containerize the service
      • Adds Package Auto Complete to assist with library references
      • Adds Remote Device Config to configure devices remotely

      4 details in Everything

    Project health

    Issue, contributor and maintainer activity in m0bilesecurity/RMS-Runtime-Mobile-Security, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.

    1. Contributors 4 +3 vs prior 12 months
    2. Maintainers 1 +1 joined · −0 left, last 12 months
    3. Bus factor 1 committers behind half the commits
    4. Community-filed 100% of issues opened, last 12 months
    5. Median time to close 99 days first maintainer reply 47 days
    6. Open backlog 2 of 100 issues ever filed
    1. Issues opened / month 0 · 0 communitymaintainers
    2. Open backlog 2
    3. Contributors / month 0
    4. Commits / month 0
    5. Stars 3,091
    Issue themes, last 12 months
    • other 100%

    Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this

    Libraries its release ships

    What its latest release locks, checked against known advisories.

    None of its release's images build from a lockfile we can read.

    Add the badge to your README

    Maintain this project? The badge links readers straight to this page, so they can follow every release here.

    Tracked by Cyber Toolchain Choose a badge style and copy the code →
    compare.md

      Free the public facts, no sign-in Any paid plan all other sections Researcher & Business pricing history and category rank

      my-toolchain — 0 tools

        Betas, release candidates and previews. Turn it off to see final releases only. It also applies to changes you ask for over MCP when you're signed in.
        browse all tools → score card for your toolchain →
        cyber-toolchain / feedback

        Send us feedback