Skip to content

SIA-IOTechnology/KittyV8Debugger

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

2 Commits
 
 
 
 
 
 
 
 
 
 

Repository files navigation

KittyV8 Debugger

KittySploit extension providing a web UI for V8/Frida memory analysis and Chrome DevTools Protocol (CDP) integration.

Features

  • Inspect — memory map, read/write, pattern search
  • Workbench — hex editor and advanced memory operations
  • V8 — V8 engine-oriented helpers
  • Primitive — build and test exploit primitives
  • Modules — modules loaded in the target process
  • Frida Lab — interactive Frida scripts
  • Tracing — agent-side event log
  • Research — notes and research workflow
  • Page CDP — tab control via CDP (capture, DOM, JS execution)
  • Launch Chrome (CDP) — launch Chromium/Chrome with a remote debugging port

Requirements

  • kittysploit-framework ≥ 1.0.1
  • Python 3 with extension-approved dependencies: frida, websockets
  • A Chromium/Chrome browser (or a binary path set in the UI) for CDP mode
  • Frida installed and available when attaching to local processes

Installation

From kittysploit-framework, via the marketplace:

market install kittyv8debugger

Then enable the extension in the KittySploit UI (id = "kittyv8" in extension.toml).

Local development

To work on this repository without the market (repo clone, monorepo, or standalone mode):

python3 src/main.py
# or, if the canonical core lives in the framework:
python3 src/core.py

The UI is served on the configured HTTP port (default 8080); the real-time channel uses the WebSocket port (default 8081).

Configuration

Variable Default Description
KITTYV8_HTTP_PORT 8080 HTTP server port (static files + UI)
KITTYV8_WS_PORT 8081 WebSocket port (Frida / CDP actions)

Quick start

  1. Open the extension from KittySploit.
  2. Frida: click Refresh, pick a browser process, then Attach.
  3. CDP: launch Chrome via Launch Chrome (CDP) or attach to a browser already started with --remote-debugging-port, then use the Page CDP tab.

Manual Chrome launch example for CDP:

chromium --remote-debugging-port=9222 \
  --js-flags=--allow-natives-syntax \
  --remote-allow-origins=*

Project layout

.
├── extension.toml      # KittySploit extension metadata
├── src/
│   ├── main.py         # Entry point (delegates to framework or bundled core)
│   ├── core.py         # HTTP/WS server, Frida agents, Chrome launcher
│   ├── cdp_bridge.py   # Chrome DevTools Protocol helpers
│   └── static/         # Web UI (HTML, CSS, JS)
└── LICENSE

Extension permissions

Defined in extension.toml: network access, imports for frida / websockets / asyncio, standard sandbox.

License

MIT — see LICENSE.

About

No description, website, or topics provided.

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Contributors