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/mobile-webviewMobile, firmware and hardware

mobile-webview

⁨Exploit insecure mobile WebViews — JS-bridge abuse, file access, and XSS→native. Load when an app renders web content in a WebView/WKWebView, exposes a JS bridge, or loads attacker-influenced URLs. Signals: addJavascriptInterface, WKScriptMessageHandler, loadUrl, file:// access, deep-link → WebView.⁩

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/mobile-webview

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

SignatureSigned, ed25519
lLARYqRpdg…f5LIMYAQ==The CLI checks the SHA-256 and the signature before it writes a file.
Package35bbe833…7fe79f4d
35bbe833653a…586f7fe79f4d1 file · ⁦1.3 KB⁩
ScanLowno findings
The scan found nothing to flag in this version.See the full scan
Sourcegithub.com/NoorQureshi/security-skills/tree/main/skills/mobile/mobile-webview@ee0e0c5

When it applies

The app shows web content in a WebView (Android WebView / iOS WKWebView) and either exposes a native JS bridge or loads URLs/content an attacker can influence (deep link, param, MITM'd http).

Why it works

WebViews blur the web/native boundary. A JS bridge (addJavascriptInterface / WKScriptMessageHandler) lets page JavaScript call native code — so XSS or a malicious loaded page can invoke native functionality. Misconfig (setAllowFileAccess, setJavaScriptEnabled, mixed content) widens it to local file theft.

Method

  1. Find the WebView config in jadx/class-dump: setJavaScriptEnabled(true), addJavascriptInterface(obj,"name") (Android <17 = any method exposed), setAllowFileAccess, setAllowUniversalAccessFromFileURLs, and what URLs it loads.
  2. Reach the WebView with your content: via a deep link that passes a URL param into loadUrl, a param reflected into the page (XSS), or MITM if it loads http:// (ATS/cleartext).
  3. Abuse the bridge: from injected JS call the exposed native methods (window.name.method(...)) — read files, get device data, trigger actions the bridge exposes.
  4. File/scheme access: file:// loads + universal file access → read app-private files; content:// tricks.

Gotchas

  • addJavascriptInterface on old targetSdk exposes reflection → RCE-ish; on modern it's limited to @JavascriptInterface methods — enumerate those.
  • Impact = what the bridge exposes + whether you can get JS to run; prove both.
  • iOS WKWebView message handlers are the equivalent bridge — check userContentController.

Verify success

Injected JavaScript invokes native functionality via the bridge (data read, action performed), or local files are exfiltrated through the WebView.

References

OWASP MASTG (platform/WebView); Android WebView security docs; "WebView bridge abuse" write-ups.

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

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.

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

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