find-crypto-entry

Locate cryptographic parameter generators in JavaScript applications via static and dynamic analysis.

335|85|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/715494637/reverse-skill --skill find-crypto-entry-715494637
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: find-crypto-entry
Source: https://github.com/715494637/reverse-skill/tree/main/%E9%A1%B9%E7%9B%AE%E8%B5%84%E6%96%99/ai-reverse-toolkit-main/skills/find-crypto-entry
Command: npx skills add https://github.com/715494637/reverse-skill --skill find-crypto-entry-715494637

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps identify where a specific parameter is generated in JavaScript code, enabling security engineers to trace encryption or signing entry points and understand client-side data flows.

Core Features & Use Cases

  • Hybrid analysis flow combining network request inspection, static source search, and dynamic breakpoint analysis to locate encryption entry points.
  • Applicable for real browser samples, obfuscated or minified code, and complex client-side logic where parameters are derived.
  • Output the entry location including script URL, line/column, function name, and call path to support verification and replication.

Quick Start

Run the steps to locate the encryption entry point for a given parameter name in your target JavaScript project.

Frequently Asked Questions about find-crypto-entry

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I locate where encryption parameters are generated in JavaScript applications?

To locate encryption parameters in JavaScript applications, use a hybrid analysis flow that combines network request inspection, static source search, and optional dynamic breakpoint analysis. This identifies the exact script URL, line, and function generating the cryptographic parameters.

What is the best way to trace cryptographic parameter generators in obfuscated JS code?

Tracing cryptographic parameter generators in obfuscated JS code requires static source search combined with dynamic breakpoint analysis. This approach bypasses minification and obfuscation by confirming the encryption entry point and call path during runtime execution.

Can I find the encryption entry point from a network request initiator in the browser?

Yes, you can find the encryption entry point from a network request initiator. The process requires access to network request listings and request initiators to trace back to the script URL and function name responsible for client-side parameter generation.

Does static and dynamic analysis work together to identify client-side data flows in JS?

Static and dynamic analysis work together to identify client-side data flows by first searching static source code for parameter generation, then applying dynamic breakpoint analysis to confirm the exact encryption entry and call path under real browser conditions.

What details do I get when locating a specific parameter generator in JavaScript?

When locating a specific parameter generator in JavaScript, you get the exact entry location including the script URL, line number, column, function name, and call path. This output supports direct verification and replication of the encryption entry.