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/reporting-bug-bounty-writeupReporting and compliance

reporting-bug-bounty-writeup

⁨Turn a confirmed finding into a triage-friendly bug-bounty report (HackerOne/Bugcrowd) with correct severity and clean evidence. Load when a bug is validated and needs submitting, on "write the report", "CVSS", "severity", or before disclosure. Signals: a reproduced finding, a program's VRT/severity⁩

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/reporting-bug-bounty-writeup

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

SignatureSigned, ed25519
gI8PyNP866…67P9qxCQ==The CLI checks the SHA-256 and the signature before it writes a file.
Package89ce9d9a…707f78e1
89ce9d9a843c…207f707f78e11 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/reporting/reporting-bug-bounty-writeup@ee0e0c5

When it governs

After you've reproduced a finding and confirmed it's in scope. A great report gets triaged fast and paid fairly; a sloppy one gets closed as informational regardless of the bug.

Structure (what triagers want)

  1. Title — [Vuln class] on <asset> allows <impact> (specific, no hype).
  2. Summary — 2–3 sentences: what, where, why it matters.
  3. Severity — CVSS 3.1 vector + score, reconciled with the program's VRT/policy. Justify the Impact metrics from demonstrated impact, not theoretical maximum.
  4. Steps to reproduce — numbered, copy-pasteable, from a clean session. Include exact requests (method, URL, headers, body) and account roles used.
  5. Proof — minimal PoC that proves impact (a screenshot with the URL bar, a request/response pair, a short video). document.domain for XSS; sts get-caller-identity for cloud, etc.
  6. Impact — the realistic business consequence, tied to what you proved.
  7. Remediation — the correct fix (allowlist, output encoding, object-level authz…).

Evidence hygiene (do before you submit)

  • Redact real PII/secrets — prove the class with your own/test data, not customer records.
  • Scrub cookies/tokens/authorization headers from pasted requests.
  • Deduplicate: one report per root cause; note additional affected endpoints inside it.
  • Stay within RoE: no data hoarding, no lateral movement beyond proof, no DoS.

Severity gotchas

  • Don't claim Critical for a self-XSS or a bug needing implausible preconditions — inflated severity gets you closed as N/A.
  • Chain low bugs into a higher-impact narrative when they genuinely combine (and show the chain).
  • Map to the program's own scale; CVSS is the starting point, the program policy is the ruling.

Verify before sending

A colleague (or you, from a fresh session) can reproduce it from your steps alone, the PoC proves impact, and nothing sensitive is exposed in the report.

References

FIRST CVSS 3.1 calculator; Bugcrowd VRT; HackerOne report best-practices.

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

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