Statically deobfuscate JavaScript without leaving the editor. The analysed code is never executed.
| Command | What it does |
|---|---|
| Defuscator: Deobfuscate File | Opens the decoded, beautified source in a side editor |
| Defuscator: Deobfuscate Selection | Same, for just the selection — handy for one packed blob inside a larger file |
| Defuscator: Analyze File | Reports both scores, the obfuscator family, findings and indicators |
Deobfuscate is also on the editor context menu for JavaScript, TypeScript and HTML files.
obfuscator.io string arrays with rotation, base64 and RC4 encodings, wrappers and every identifier style; Dean Edwards P.A.C.K.E.R.; JSFuck, JJEncode and AAEncode; hex and unicode escapes; control-flow flattening; proxy objects; and inline source maps.
- Obfuscation — how hard the code is trying not to be read, measured on the original source.
- Capability risk — what it would do if it ran, measured on the decoded output.
They answer different questions. A low risk score on a heavily obfuscated file can mean not resolved yet rather than safe, which is why both are shown.
None up front. The extension looks for the CLI in this order:
- The
defuscator.cliPathsetting, if you set it defuscatoron your PATH —npm install -g defuscatornpx, fetching a prebuilt binary on first use
A global install is worth it if you use this often; the first npx call pays for a download.
| Setting | Default | Description |
|---|---|---|
defuscator.cliPath |
"" |
Path to a defuscator binary. Overrides discovery. |
defuscator.version |
1.0.0 |
Version fetched via npx. Pinned so runs are reproducible. |
- defuscator.com — web app and docs
- Benchmark — reproducible, includes the cases it fails
- GitHub Action — the same engine gating CI
MIT licensed.