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.

FeedsContactPrivacy© 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
711371 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

Build organization

Run make from the repository root. The root Makefile defines the default goal and includes these files in order:

FileResponsibility
config.mkCompiler flags, build directories, source lists for lint, platform defaults
native.mkExplicit native link dependencies, compilation, generated header dependencies
workflows.mkProduct launch, evidence fixtures, local services, Brave integration commands
quality.mkBuild regression check, linters, sanitizers, cleanup

Existing command names and executable paths remain the public interface. Implementation objects mirror source paths inside BUILD_DIR; compiler-generated .d files track direct and transitive project headers. Only the decoder executable adds zlib to its link command. make native-probe-compile compiles the tracked browser queue without a separate test source.

make bootstrap-dev-tools installs the same pinned clang-format and Ruff versions used by CI into ~/.local/share/reb-tools, and installs missing shellcheck and actionlint formulae with Homebrew. Make prefers those pinned local tools automatically. make deob-benchmark builds the Rust worker and runs the bounded semantic corpus with timing, memory, transformation, and changed-source coverage evidence.

make lint checks formatting and Clippy warnings for both Rust manifests. The deobfuscation worker includes all targets so its regression-test code is checked along with the production executable.

Use a separate build directory for a different compiler or set of flags:

make BUILD_DIR=build/debug OPT_CXXFLAGS='-O0 -g' all

Make does not detect changes to command-line flag values in an existing build directory. Changes to the native rules or compiler configuration files do invalidate native objects. make sanitize uses its own clean build directory.

make native-build-test runs scripts/check-native-build.sh, which builds and runs two independent executables in a temporary directory, checks that a repeat build does no work, and verifies that an artifact header change invalidates its consumer without rebuilding the event demo. make check includes this regression check, the deobfuscation semantic benchmark, and the backend and deobfuscator worker's Rust test suites. It also runs the source-facts HTTP/CLI integration test against the built Rust/Oxc worker; CARGO_TARGET_DIR is honored when locating that helper.

make native-proxy-policy-check compiles and runs the preparation-only native proxy/container policy suite without Chromium, Cargo, sockets, or a browser. It is included in make check and make sanitize; it does not establish real browser routing or isolation. See the versioned native proxy-container contract.

origin-trace-backend builds the Rust HTTP service, VM analyzer, and API CLI. ui starts that service after deterministic evidence generation. backend-e2e uses a disposable Chromium-compatible profile and synthetic localhost fixtures; set ORIGIN_TRACE_TEST_BROWSER for a nonstandard browser executable. App builds bundle Rust executables and static UI assets, with no Python runtime dependency.

Download Tool