recon-js-analysis
Mine JavaScript for endpoints, params, secrets, and hidden functionality. Load on SPAs, heavy JS apps, after crawling, or "analyze the JS". Signals: bundled JS (webpack/main.*.js), API calls in JS, source maps, /static/js, front-end frameworks.
v2026.10.14-ee0e0c53 installs+3 in 7 days27 StarsMITsynced 22 hours ago
Install
No NotHoly CLI yet? Install it first.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install noorqureshi/recon-js-analysisWrites to ~/.notholy/skills after checking the signature and the SHA-256.
SignatureSigned, ed25519
Package5e0db591…09086a7c
5e0db59138c9…296309086a7c1 file · 1.2 KBScanLowno findings
Sourcegithub.com/NoorQureshi/security-skills/tree/main/skills/recon/recon-js-analysis@ee0e0c5
On this page
When it applies
The app is JS-heavy (SPA). The front-end bundle is a map of the backend: it references API endpoints, parameters, feature flags, roles, and sometimes secrets — much of it not linked in the UI.
Why it works
Client code must know how to call the server, so endpoints/params are embedded in JS. Bundlers also occasionally ship source maps (full original source) and developers leave keys/comments.
Method
- Collect all JS:
katana -jc,subjs, or crawl; grab every.js(incl. lazy-loaded chunks). - Extract endpoints/params:
linkfinder/jsluicepull URLs, paths, and param names from bundles. - Hunt secrets & flags: grep for
apiKey|token|secret|internal|admin|debug, feature flags, and role checks done client-side (server may not enforce them → BOLA/BFLA leads). - Source maps: if
.mapfiles ship, reconstruct original source (source-maptools) → full whitebox-ish view. - Feed results: new endpoints →
api-*; client-only auth checks →api-bola; secrets → validate.
Gotchas
- Client-side "admin" gating usually isn't enforced server-side — test the endpoints directly.
- De-obfuscate/beautify minified bundles before grepping (
js-beautify). - Lazy-loaded chunks hide the juicy routes — enumerate all chunk files, not just
main.js.
Verify success
Endpoints/params/secrets extracted from JS that weren't in the UI — new, testable surface.
References
LinkFinder/jsluice; katana; "JS recon" bug-bounty methodology.
Files in this version
- SKILL.md2.0 KB
Permissions
| Permission | Declared | Found by the scan |
|---|---|---|
| Reads files | No | No |
| Writes files | No | No |
| Runs shell commands | No | No |
| Uses the network | No | No |
| Uses connectors | No | No |
| Drives a browser | No | No |
Scan findings
Reviewed on Nov 13, 2026
The scan found nothing to flag in this version.
A clean scan lowers the risk but does not prove a package is safe. Read what you install.
| Version | Published | Commit | SHA-256 | Signature | Permission change |
|---|---|---|---|---|---|
| v2026.10.14-ee0e0c5 | Nov 13, 2026 | ee0e0c5 | 5e0db591 | Signed | – |
More from NoorQureshi
All from this publisherMore in Recon and OSINT
See the category- gobusteraeondave/gobuster4
- ghuntaeondave/ghunt4
- stride-threat-modelingsecurityskills/stride-threat-modeling3
- attack-surface-reconsecurityskills/attack-surface-recon3
- bug-bounty-recon-pipelinesecurityskills/bug-bounty-recon-pipeline3
- implementing-attack-surface-managementmukul975/implementing-attack-surface-management3
Ask anything your scope allows.
Create an account, add credits and ask the first question in the chat or the terminal.
- 1/3
Create the account
Individual or company. You can switch to a company later without losing balance or keys.
IndividualCompany - 2/3
Add credits
By card. Pay per token, no subscription.
$5.00minimum deposit - 3/3
Ask
In the chat, or install the CLI and run notholy login in your terminal.
$ notholy login