Skip to content
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
noorqureshi/web-extension-reverseWeb and bug bounty

web-extension-reverse

⁨Reverse engineer browser extensions (Chrome/Edge MV2/MV3, Firefox) for an authorized review: unpack .crx/.xpi, assess the permission surface, trace background/service-worker and content-script logic, and recover credential, signing, or traffic-handling behavior. Load on "analyze this extension", ext⁩

v2026.10.14-ee0e0c52 installs+2 in 7 days27 StarsMITsynced 23 hours ago

Install

No NotHoly CLI yet? Install it first.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install noorqureshi/web-extension-reverse

Writes to ⁦~/.notholy/skills⁩ after checking the signature and the SHA-256.

SignatureSigned, ed25519
tJi5uLLnT2…bGdYIdBA==The CLI checks the SHA-256 and the signature before it writes a file.
Packagec07b0bf0…854b0f17
c07b0bf0c737…52e4854b0f171 file · ⁦2.5 KB⁩
ScanLow1 finding
  • Links to outside domains
See the full scan
Sourcegithub.com/NoorQureshi/security-skills/tree/main/skills/web/web-extension-reverse@ee0e0c5

When it applies

The target is a browser extension — a .crx/.xpi package or an unpacked extension directory — not ordinary page JavaScript (for that, load reverse-eng-js). Typical jobs: audit an in-scope extension's client-side signing/encryption/proxy logic, hunt for over-privileged permissions in a review, or investigate a malicious or supply-chain-poisoned extension. Target must be confirmed in scope.txt (tradecraft-scope-roe); for malicious samples work in an isolated VM and see defense-malware-triage.

Why it works

An extension is just a zip with a manifest.json that declares its entire trust surface — permissions, host permissions, entry scripts. Reading the manifest first tells you exactly which scripts can touch which origins, and every browser-API capability (webRequest, cookies, nativeMessaging) is reachable by grepping for chrome.* / browser.* calls from those entry points. The dynamic half is free: Chrome runs unpacked extensions natively and DevTools attaches straight to the background service worker.

Method

  1. Unpack. .xpi is a plain zip. .crx has a CRX3 header before the zip data — most unzip tools tolerate it; if not, strip the header or pull the already-unpacked copy from the browser profile (.../Extensions/<id>/<version>/).
  2. Read the manifest first: jq '{permissions, host_permissions, background, content_scripts, web_accessible_resources, externally_connectable, content_security_policy}' manifest.json. Record MV2 (background.scripts, webRequestBlocking) vs MV3 (background.service_worker, declarativeNetRequest) — it changes where the logic lives.
  3. Score the permission surface. Red flags: <all_urls> (read/write any site), webRequest/webRequestBlocking (MITM-grade request rewriting), debugger, cookies, nativeMessaging (escapes the browser to a host binary — follow it with reverse-eng-binary-triage), and externally_connectable (lets web pages drive the extension — a remote attack surface).
  4. Trace the logic. Start at the service worker / background entry, then the content scripts — note each script's matches, run_at, and whether it runs in the isolated world. Grep for chrome.storage / IndexedDB to find stored keys and tokens, and for runtime.onMessage/sendMessage/postMessage to map who can drive what. For obfuscated or webpack-packed code, anchor on the chrome.* API calls and run the reverse-eng-js recovery flow; for the fast attack-side path see web-client-side-signing-bypass.
  5. Go dynamic. Load the unpacked directory at chrome://extensions (Developer mode), watch for load errors, then open DevTools on the service worker link. Trigger events and observe network traffic and message passing; Burp/CDP covers the deeper hooks. For known-bad hunting, run YARA rules for malicious-extension families over the unpacked tree.

Gotchas

  • MV3 service workers suspend when idle — breakpoints go cold. Keep the worker's DevTools window open and trigger the event you're tracing; don't expect it to be alive on its own.
  • MV3 declarativeNetRequest is declarative — the blocking/redirect logic lives in the JSON ruleset, not JS. Read the rules file; there is no function to hook.
  • Content scripts run in an isolated world — page JS can't see their variables, and they can't see the page's. Cross-talk happens over the DOM or postMessage; audit both directions.
  • Secrets live in the installed profile, not the package — chrome.storage.local persists in the profile's LevelDB; check there during a live-host review.
  • .crx from the Web Store is signed and version-locked — for reproducible analysis record the extension ID + version, and diff updates before concluding.

Verify success

You can state, with evidence: the full permission surface and entry scripts, the data flow (what the extension reads, where it sends it, where keys/tokens live), and who can message it (other extensions, web pages, native hosts) — each claim cited to a manifest field or code location.

References

Chrome MV3 migration docs; chrome://extensions developer mode; OWASP CISQ extension guidance.


Portions adapted from reverse-skill by zhaoxuya520, MIT License.

Files in this version

Permissions

PermissionDeclaredFound by the scan
Reads filesNoNo
Writes filesNoNo
Runs shell commandsNoNo
Uses the networkYesYes
Uses connectorsNoNo
Drives a browserNoNo

Scan findings

Reviewed on Nov 13, 2026

  1. InfoLink · Links to outside domains

A clean scan lowers the risk but does not prove a package is safe. Read what you install.

VersionPublishedCommitSHA-256SignaturePermission change
v2026.10.14-ee0e0c5Nov 13, 2026ee0e0c5c07b0bf0Signed–

Ask anything your scope allows.

Create an account, add credits and ask the first question in the chat or the terminal.

  1. 1/3

    Create the account

    Individual or company. You can switch to a company later without losing balance or keys.

    IndividualCompany
  2. 2/3

    Add credits

    By card. Pay per token, no subscription.

    $5.00minimum deposit
  3. 3/3

    Ask

    In the chat, or install the CLI and run notholy login in your terminal.

    $ notholy login