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/exploit-chainingReverse engineering and fuzzing

exploit-chaining

⁨Combine low/medium findings into one high-impact exploit chain, and amplify demonstrated impact. Load when you have several small bugs, a "so what?" finding, on "chain", "escalate impact", or building the narrative for a report. Signals: self-XSS + CSRF, open-redirect + OAuth, IDOR + info-leak, SSRF⁩

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/exploit-chaining

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

SignatureSigned, ed25519
DF4K4QO0mn…m7Q9cMAQ==The CLI checks the SHA-256 and the signature before it writes a file.
Package820a85ab…59396687
820a85ab3d5c…6c2d593966871 file · ⁦1.4 KB⁩
ScanLowno findings
The scan found nothing to flag in this version.See the full scan
Sourcegithub.com/NoorQureshi/security-skills/tree/main/skills/exploit-dev/exploit-chaining@ee0e0c5

When it applies

You have bugs that are individually "meh" (self-XSS, an info leak, an open redirect, a weak CSRF) and need to turn them into something a program pays for — or a pentest foothold that needs several bugs stacked.

Why it works

Impact is compositional. One bug supplies a precondition another needs: a leak provides the id IDOR needs; an open redirect makes OAuth leak a token; SSRF reaches the metadata service that yields cloud creds. The chain's severity is the end impact, not the weakest link.

Method

  1. Inventory every finding with what it gives and what it needs (primitive in / out).
  2. Look for matches: does bug A's output satisfy bug B's precondition? Common chains:
    • self-XSS + login-CSRF / cookie-fixation → land XSS in the victim's session.
    • open redirect + OAuth redirect_uri → steal the authorization code → ATO.
    • IDOR/info-leak → user id/UUID → BOLA on another endpoint.
    • SSRF → cloud-imds-ssrf → IAM creds → cloud impact.
    • file upload (stored) → XSS/SSRF/RCE depending on how it's served.
  3. Build the shortest reliable path to the highest impact; script the PoC end-to-end.
  4. Write the narrative: state the end impact first, then each link with its role, so a triager sees severity immediately (see reporting-bug-bounty-writeup).

Gotchas

  • Don't over-chain — the simplest path to real impact is more credible and reproducible.
  • Each link must be reliable; a flaky step sinks the whole chain in triage.
  • Keep every step in scope and within RoE — a chain that steps out of scope is unreportable.

Verify success

A single reproducible PoC that starts from attacker-controlled input and ends at concrete high impact (ATO, data access, RCE, cloud takeover).

References

Bug-bounty disclosed chains (HackerOne Hacktivity); PortSwigger chained-attack labs.

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, 2026ee0e0c5820a85abSigned–

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