Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
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.

··Feeds·Contact·Privacy·© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
reverse-engineering-browser — Local-first macOS research browser built on a custom Brave build that captures network traffic, fingerprints, scripts, and runtime evidence for reverse engineering web apps. | Kitploit
Tools/GitHubGitHub/sunghoojung/reverse-engineering-browser
Packet Sniffing & AnalysisDynamic Analysis (Sandboxing)Web Proxies & InterceptionCode AnalysisDynamic Code Analysis (DAST)Reverse EngineeringDebuggersInformation Gathering
Web Security
Privacy
Utilities & Frameworks
Fingerprint Spoofing
GitHubsunghoojung/reverse-engineering-browser

reverse-engineering-browser

Local-first macOS research browser built on a custom Brave build that captures network traffic, fingerprints, scripts, and runtime evidence for reverse engineering web apps.

View Repository
581 day agoNot yet reviewed

Most Popular

View all →

Discover the most used tools by our community.

Explore all tools

Browse our collection of tools

View all tools →
Share

Reverse Engineering Browser

See the browser evidence behind fingerprints, requests, scripts, and runtime behavior.

CI status Latest release Platform: macOS on Apple silicon

A local-first research browser and macOS workspace for inspecting authorized web applications.

v0.2.1 released

Origin Trace Traffic now has a full-width, DevTools-style request table. Paths and hosts are easier to read, with separate status, type, method, and timing columns. Live requests follow the bottom of the list; scrolling up preserves your place and offers a jump to new requests. Selecting a request shows its complete URL with a Copy URL action. The v0.2.0 session privacy and launch improvements remain available.

Download Origin Trace v0.2.1 · Release notes ·

Full changelog

Feature changelog

  • v0.2.1: redesigned live Traffic as a readable full-width request table with path and host hierarchy, compact request metadata, follow-to-bottom updates, a new-request jump, and full-URL inspection and copying.
  • v0.2.0: added per-session metadata or bounded-content capture controls, prompt-free isolated profiles with explicit Keychain opt-in, verified browser readiness and retry/relaunch flows, private Brave diagnostics, a semantic deobfuscation benchmark corpus, and automated developer-tool bootstrap.
  • v0.1.10: fixed the launch-time WebKit cancellation race that could show NSURLErrorDomain error -999 while Origin Trace switched from its offline shell to the newly started live workspace.
  • v0.1.9: made normal app launch start the broker, artifact receiver, debugger, analyzers, loopback UI, and instrumented custom Brave session automatically; packaged the required helpers and added explicit startup failure reporting and owned cleanup.
  • v0.1.8: added bounded Rust/Oxc deobfuscation inside Sources, original-byte provenance, nesting protection, proxy and custom decoder evaluation, explicit JSFuck coercion assumptions, and bounded loop/switch dispatcher recovery.
  • v0.1.7: refreshed the research interface and reorganized advanced tools, source inspection, request details, fingerprinting, memory, and experiments.
  • v0.1.6: added stronger source, memory, request-signal, and analyst workflows with native application packaging and validation updates.
  • v0.1.5: expanded the native research workflow and macOS distribution.
  • v0.1.4: expanded native fingerprint probes, added per-tab newest-first activity and live tab counts, opt-in Canvas image capture, clearer queue-gap reporting, and controls to stop probes or clear the current session's events.
  • v0.1.3: removed sample requests, events, and Canvas output from the production app bundle so every session starts with real captured evidence.
  • v0.1.2: added the Fingerprinting workspace with Canvas image output, a local replay preview, captured drawing functions, fingerprint activity, event details, filters, and request correlation.

Features

  • Live network traffic: inspect requests in a full-width table with readable paths, hosts, methods, status codes, and timing; select one to inspect its full URL, headers, request body, and response body captured through CDP.
  • Tab and domain organization: separate traffic by browser tab, then narrow a tab to a specific destination domain or resource type.
  • Native browser evidence: record calls and property reads across Canvas, WebGL, Web Audio, device and layout APIs, Permissions, Storage, WebRTC, and JavaScript runtime fingerprinting, plus request lifecycle metadata from a custom Brave build.
  • Origin tracing: follow a request backward through the observed events, scripts, frames, execution contexts, and captured artifacts that contributed to it.
  • Source inspection and debugging: browse page sources, set breakpoints, pause and step through JavaScript, inspect scopes, evaluate watches, and use a live console.
  • Artifact capture: retain bounded copies of network-delivered and runtime-generated JavaScript and WebAssembly with hashes and provenance, plus explicitly authorized Canvas image output.
  • Memory and backtrace tools: inspect heap snapshots, live objects, decoded stack frames, and VM-related findings.
  • Research workflows: save requests to collections, replay isolated requests, run controlled experiments, and keep local analyst notes.
  • Local and bounded capture: evidence remains on the machine. Sensitive request headers are redacted, bodies are capped at 128 KiB in CDP capture, and native queues and artifact transfers have explicit limits.
  • Native quiet mode: run native evidence capture without attaching DevTools when request and response content is not required.

How to use it

Download the compiled macOS apps

  1. Download Origin Trace v0.2.1 and the Brave Browser Development preview.
  2. Unzip both files and place the applications beside each other, or install Brave Browser Development in /Applications.
  3. Open Origin Trace. It starts the capture services and an isolated custom Brave session automatically.

The compiled apps are for Apple silicon Macs. The linked Brave Browser Development preview predates current probe support. Build the pinned Brave integration from this release's source to use every native probe; the downloaded preview cannot demonstrate them. Origin Trace contains no bundled sample evidence. The applications are ad-hoc signed but not Apple-notarized, so the first launch may require Control-clicking the app and choosing Open. The v0.2.1 GitHub release tag is unsigned; its merge commit is GitHub-verified.

Downloading the compiled Brave app does not require a 100+ GiB source checkout. Allow about 1 GiB to download and extract both apps, plus whatever space you want to retain for browser profiles and captured sessions.

Run a live capture with an existing custom Brave build

From the repository root:

root@kitploit:~
REB_CDP_NETWORK_CAPTURE=1 \
REB_BRAVE_BINARY="/path/to/Brave Browser Development.app/Contents/MacOS/Brave Browser Development" \
make live

Origin Trace and the custom Brave browser open together. Browse in that Brave window and select requests in the Traffic tab. Close Brave to end the session. Captured evidence is stored under build/sessions/live/.

CDP content capture is explicit because it can retain page content. It redacts authorization, cookie, proxy-authorization, and set-cookie headers. Streaming, cached, internal, or already-evicted response bodies may be unavailable.

Fingerprint operation names are captured by default. To also retain the exact image returned by HTMLCanvasElement.toDataURL() for this one session, add REB_CAPTURE_CANVAS_IMAGES=1. Canvas image output can contain page content, so it is disabled by default, kept only in the local session store, and limited to 2 MiB per image.

Build the custom Brave browser for the first time

These requirements apply only when compiling Brave from source. They do not apply when using the downloadable compiled Brave app.

Source-build requirements:

  • macOS with full Xcode installed;
  • Node.js and pnpm;
  • Python 3, a C++20 compiler, zlib, and Make;
  • at least 150 GiB free, with 200 to 250 GiB recommended.

Prepare the pinned checkout, apply the integration, verify it, and build Brave:

root@kitploit:~
./scripts/bootstrap-brave.sh --init
./scripts/sync-browser-integration.sh
make brave-doctor
make brave-probe-check
./scripts/brave-toolchain.sh build

The first full build can take several hours. Later builds are incremental and normally reuse the existing checkout and compiled objects. After it completes, start live capture with the command from the previous section.

Run without CDP content capture

For native metadata and artifact capture without a live DevTools attachment:

root@kitploit:~
REB_NATIVE_QUIET_MODE=1 \
REB_BRAVE_BINARY="/path/to/Brave Browser Development.app/Contents/MacOS/Brave Browser Development" \
make live

Sources, breakpoints, stepping, watches, the console, full URLs, headers, and bodies are unavailable in native quiet mode.

Use this project only on systems you own or are explicitly authorized to inspect.

Download Tool