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-postmessageWeb and bug bounty

web-postmessage

⁨Exploit insecure cross-window messaging (`window.postMessage`) — handlers that trust `event.data` without checking `event.origin`, leading to XSS, token theft, or state change. Load when the app uses iframes/popups/SSO widgets, on "postMessage", or when JS registers a `message` listener. Signals: `a⁩

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/web-postmessage

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

SignatureSigned, ed25519
fMGLzgo45i…NRzU70DA==The CLI checks the SHA-256 and the signature before it writes a file.
Package10dfb949…e53e34ae
10dfb949b0dc…7d37e53e34ae1 file · ⁦1.5 KB⁩
ScanLowno findings
The scan found nothing to flag in this version.See the full scan
Sourcegithub.com/NoorQureshi/security-skills/tree/main/skills/web/web-postmessage@ee0e0c5

When it applies

The target sends or receives postMessage between windows/iframes (SSO, payment widgets, chat, embeds). A receiver that doesn't validate the sender's origin will act on a message from your page.

Why it works

postMessage is cross-origin by design; safety depends entirely on the receiver checking event.origin and the sender setting a specific targetOrigin. Miss the origin check and any site can drive the handler; use targetOrigin="*" and any embedder can read the message. Then it's just a matter of what the handler does with event.data — often innerHTML, eval, location, or a relayed token.

Method

  1. Find listeners: grep the JS for addEventListener("message" / onmessage; note the sink each handler feeds (innerHTML, eval, document.write, location, another postMessage).
  2. Check the origin guard: no check, or a weak one — origin.indexOf("trusted")>-1, origin.endsWith("site.com") (matches site.com.evil), a loose regex — is exploitable.
  3. Drive the sink (XSS): host a page that open()s or <iframe>s the target and postMessage()s a payload the handler writes to a DOM sink → script execution.
  4. Steal data (leak): if the target sends messages with targetOrigin="*" (tokens, PII), embed it and read them in your message listener.
  5. Bypass a bad check: register your attacker origin to satisfy the substring/regex flaw (trusted.attacker.com, attackertrusted.com).

Gotchas

  • event.origin (the sender) is the thing to validate — not event.source and not the URL bar.
  • Sandboxed iframes and X-Frame-Options/CSP frame-ancestors may stop framing — use a popup (window.open) instead.
  • Some handlers require a specific data shape/handshake — replay the legit message first, then mutate.

Verify success

A message from your attacker page reaches a dangerous sink (script executes / navigation happens) or you read a secret the target broadcast — reproducible from an external origin.

References

PortSwigger DOM-based / postMessage; MDN Window.postMessage security notes.

Files in this version

Permissions

PermissionDeclaredFound by the scan
Reads filesNoNo
Writes filesNoNo
Runs shell commandsNoNo
Uses the networkNoNo
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, 2026ee0e0c510dfb949Signed–

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