Skip to content
KitploitKITPLOIT
도구익스플로잇블로그
Log in
제출
도구익스플로잇블로그
제출

해킹, 침투 테스트 및 사이버 보안 도구를 당신의 보안 무기고에!

Kitploit은 해킹, 사이버 보안 및 침투 테스트 도구 디렉토리입니다. 최신 프로젝트 업데이트를 발견하여 취약점을 찾고, 시스템을 분석하고, 테스트를 자동화하고, 보안을 강화하세요.

피드문의개인정보© 2026 Kitploit

도구 디렉토리

카테고리

모든 카테고리 보기
Loading categories
도구/GitHubGitHub/ch0pin/medusa
Android SecurityDynamic Analysis (Sandboxing)iOS SecurityExploitationReverse EngineeringInformation GatheringFuzzingMalware AnalysisPenetration TestingMobile SecurityRed Teaming
GitHubch0pin/medusa

medusa

Mobile Edge-Dynamic Unified Security Analysis

저장소 보기웹사이트
2.3k3185310시간 2분 전Kitploit 검토 완료

인기

모두 보기 →

커뮤니티에서 가장 많이 사용되는 도구를 찾아보세요.

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 궁극의 OSINT 툴킷: 조사 그래프, 신뢰도 점수 산정, 별칭 패밀리, 지도, 타임라인 및 보고서. 49개 모듈, 400개 이상 사이트, API 키 불필요.

    927
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    # GhostLock 원탭 실행 앱 (CVE-2026-43499)

    555
  • 3

    redforge

    cybersecurity91/redforge

    브라우저 측 레드 팀 툴킷으로, 정찰, 페이로드 생성, 자격 증명 공격, 암호화, 인코딩 및 참여 보고를 위한 102개의 오프라인 도구를 제공합니다.

    360
  • 4

    ARTEX

    baarai/artex

    LLM 멀티 에이전트 자율 침투 테스트 플랫폼으로, 플래너/워커 에이전트, 자산 및 탐색 그래프, MITM 트래픽 기록, 취약점 재테스트 기능을 제공합니다.

    357
  • 5

    looking-glass

    anonghosty/looking-glass

    Shadowserver 보고서를 MongoDB로 수집하고 이를 대화형 지도, 분석, 발견 사항, 권고 및 경영진 대시보드로 재생하는 CSIRT 플랫폼입니다.

    324
  • 6

    CyberStrikeAI

    ed1s0nz/cyberstrikeai

    AI 네이티브 사이버보안을 위한 행동 체계—의도가 통제된 실행이 되고, 증거가 운영 메모리가 되며, 모든 운영이 다음 운영을 개선하는 곳.

    289

모든 도구 탐색

도구 컬렉션을 둘러보세요

모든 도구 보기 →
공유
요청한 언어로 콘텐츠를 사용할 수 없습니다. 영어 버전을 표시합니다.

Sponsored by:


Sponsor logo

MEDUSA

A modular automation framework and script repository for runtime testing and investigating Android and iOS apps, designed for penetration testers and malware analysts. It lets you plug in modules to bypass protections (like SSL pinning), inspect network/WebView activity, trace API calls, examine memory/crypto, and monitor malware behavior — all from a single coordinated script. It runs on FRIDA under the hood and ships with 100+ reusable modules so tests scale and repeat easily.

Installation

System requirements:

  • Linux or macOS (limited functionality available on Windows)
  • Python 3.12 or newer
  • Node.js and npm (for building the Java and ObjC bridges)
  • adb and a Frida-compatible Android or iOS device
  • FRIDA server (running on the mobile device)

Installing from github:

  1. Clone this repository.
  2. CD into the medusa directory.
  3. Install dependencies:

For the unified development version, use the dev branch. Replace /path/to/medusa below with the absolute path to your checkout.

python3 -m venv /path/to/medusa/.venv
/path/to/medusa/.venv/bin/python -m pip install -r /path/to/medusa/requirements.txt 
# Or for mcp support
/path/to/medusa/.venv/bin/python -m pip install -r /path/to/medusa/requirements-mcp.txt 
npm --prefix /path/to/medusa ci
npm --prefix /path/to/medusa run build:bridges

The bridge build produces the Java and ObjC agents used with Frida 17. Rebuild them after changing their npm dependencies. The Python runtime and development lockfiles record the tested dependency sets.

Or download the latest stable version from here

Usage

Medusa consists of two modules: medusa and mango. What follows is a description about their usage.

MEDUSA

Use the unified launcher for Android and iOS:

/path/to/medusa/medusa

After start, MEDUSA will enumerate available devices and let you pick one.

Device OS detection selects the Android or iOS commands. Use loaddevice to switch platforms within the same process, retaining each platform's staged work. An explicit override is available through --platform android or --platform ios.

Development checks

/path/to/medusa/.venv/bin/python -m pip install -r /path/to/medusa/requirements-dev.lock.txt
/path/to/medusa/.venv/bin/python -B -m unittest discover -s /path/to/medusa/tests

Ruff and mypy are configured in the project metadata with an incremental scope for the new CLI/core code. Tests cover original command definitions, startup output, platform switching, generated-agent retention, compilation output, and script lifecycle behavior. Device-specific runtime coverage remains separate from these host tests.

Common interactive workflow

# list available commands or get help about a specific command
medusa> help      # or help <command-name>

# list available modules
medusa> show all 

# get quick help/details about a module
medusa> info http_communications/ssl-pinning-bypass

# add a module (Tab completes module paths)
medusa> use http_communications/      # press [Tab] to autocomplete

# list installed packages on the device
medusa> list

# instrument a package (by package name)
medusa> run -f com.my.app

# show available devices and select one
medusa> loaddevice

MANGO

Medusa’s lightweight companion CLI for static prep and automation — manifest parsing, attack-surface enumeration, app tracking, and simple device/proxy automation.

Run python3 mango.py <database-name> to create or load a database for storing Mango’s results.

# show available devices and select one
mango> loaddevice

# pull an app (by package name)
mango> pull com.my.app 

# import an app for analysis
mango> import /path/to/apk

Mango can also create verified debuggable APK copies with patch, validate/sign split sets with patchmultiple, and inject Frida Gadget with patch gadget. Run patch --help or patch gadget --help for options. Signing options are optional; the bundled test key remains the default. See the APK patching guide for requirements, verification, and installation considerations.

Mango report commands support file redirection, append, and shell pipes:

show exposure > /path/to/reports/exposure.txt
show exposure >> /path/to/reports/exposure.txt
show exposure | grep exported

Reports retain their terminal formatting and use plain text without terminal colour escapes when redirected. Prompts, progress messages, and diagnostics remain on the console. Use quotes around output filenames containing spaces.

MCP Server Support

This is optional and not required for the standard Medusa CLI workflow.

To use the Android MCP server (medusa_android_mcp.py), install the MCP requirements and run:

MEDUSA_MCP_TRANSPORT=streamable-http python medusa_android_mcp.py

Configuration:

"medusa-android": {
   "type": "http",
   "url": "http://127.0.0.1:8000/mcp"
}

For advanced usage and examples, see our wiki. For quick tips and introductory workflows, check the demos below:

  • MEDUSA | Android Penetration tool (credits @ByteTheories)
  • MEDUSA | Android Malware Analysis 101 (credits @ByteTheories)
  • Unpacking Android malware with Medusa (credits @cryptax)
  • Unpacking Android APKs with Medusa (credits @LaurieWired)
  • #Medusa - Extensible binary instrumentation framework based on #FRIDA for Android applications (credits @AndroidAppSec)
  • Memory inspection with Medusa
  • Bypassing root detection

How to Contribute:

You can contribute to this project by:

  • Becoming a sponsor
  • Creating a medusa module (see how to)
  • Making a pull request
  • Reporting an error/issue
  • Suggesting an improvement
  • Making this project more popular by sharing it or giving a star

Screenshots

  • SSL Unpinning

ssl unpinning

  • Intent Monitoring

Intent monitoring

  • Webview Monitoring

Webview monitoring

  • File/Content provider monitoring

File and content providers

  • Native Libraries Enumeration
도구 다운로드