Menu

Individual skill

reverse-eng-js

0upvotes

Reverse front-end JavaScript end to end: trace which script fires a given request, capture a signing/encryption function's real inputs at runtime, then rebuild the algorithm locally in Node.js with evidence-driven environment shims until it reproduces the target parameter. Load when you need the *mechanism* behind client-computed params (sign, signature, _signature, X-Sign, token, encrypted bodies, anti-bot / risk-control fields), when webpack-minified or obfuscated JS hides the logic, or when you must trace an XHR/fetch/WebSocket trigger point.

skills/reverse-engineering/reverse-eng-js/SKILL.md

Read pinned source

Source commit ee0e0c50d2f6d941a14b73dd85a2b470d0ab976e

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 7, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
27
Repository last updated
Oct 14, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Front-end JavaScript reverse engineering

## When it applies
An in-scope web app computes something in JavaScript that you need to understand or reproduce:
a request signature, an encrypted body, anti-bot / risk-control fields, or a hidden WebSocket
protocol. `web-client-side-signing-bypass` covers the fast attack-side path (prove the guard is
client-side, get one replayable request); load *this* skill when you need the full algorithm
recovered and running locally in Node — for sustained fuzzing, logic audit, or documentation.
Target must be in `scope.txt` (`tradecraft-scope-roe`); observe only your own session.

## Why it works
The page must run the algorithm in the browser before the request leaves, so both the code and
every input to it are observable at runtime — minification only slows you down, it can't hide
execution. Break on the outgoing request, walk the call stack to the signing function, lift it
Back to top