tradecraft-bugbounty-platforms
Understand how the major bug-bounty platforms differ — scope rules, disclosure, triage, and reputation — so you play each correctly. Load when working a program on HackerOne, Bugcrowd, Intigriti, YesWeHack, or Immunefi, on "platform rules", "safe harbor", "VDP vs paid", or before submitting. Signals
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/tradecraft-bugbounty-platformsWrites to ~/.notholy/skills after checking the signature and the SHA-256.
SignatureSigned, ed25519
Packageb2b1ae82…d1cb49f1
b2b1ae822a23…5d0ed1cb49f11 file · 1.6 KBScanLowno findings
Sourcegithub.com/NoorQureshi/security-skills/tree/main/skills/tradecraft/tradecraft-bugbounty-platforms@ee0e0c5
On this page
When it applies
You're operating inside a platform's program. The technical work is the same everywhere, but scope enforcement, disclosure, payout, and reputation mechanics differ — and getting them wrong loses bounties or violates the rules.
Why it works
Each platform encodes its own contract. Reading the program's policy through the lens of that platform's conventions tells you what's actually in scope, what proof triage expects, and how your report will be judged — before you spend effort.
Key points per platform
- Common to all: the program's policy page is authoritative — read scope, out-of-scope, accepted vuln types, testing rules (rate limits, no-DoS, test accounts), and safe-harbor terms before touching anything. VDP (no bounty) vs paid changes your time investment.
- HackerOne: reputation/signal/impact affect invitations; structured severity (CVSS); private programs reward good signal. Watch the "eligible for bounty" vs "known issue" distinctions.
- Bugcrowd: uses the VRT (Vulnerability Rating Taxonomy) — map your finding to it and expect payout by the program's reward range for that VRT entry.
- Intigriti: clear in-scope/out-of-scope tiers; researcher-friendly triage; watch domain wildcards and the severity matrix.
- YesWeHack: EU-centric; strict scope; good for fresh European targets.
- Immunefi (web3): smart-contract/DeFi focus; payouts tied to funds at risk (often huge);
PoC on a fork/testnet, never mainnet exploitation; primacy/known-issue rules are strict. Pair with
code-review-solidity.
Method
- Read the policy end-to-end; extract scope, out-of-scope, rules, safe harbor, and the severity/ reward model.
- Set up isolated test accounts and honour rate limits.
- Rate your finding by the platform's model (CVSS or VRT) — see
reporting-cvss-scoring. - Submit per the platform's report format (
reporting-bug-bounty-writeup) and engage triage professionally (reporting-triage-communication).
Gotchas
- Out-of-scope is as important as in-scope — testing an excluded asset can void safe harbor.
- "Wildcard" scope still excludes third-party/SaaS you don't control — check.
- Platform reputation is durable; a spammy or rule-breaking submission history follows you.
References
Each platform's program-policy and disclosure docs; Bugcrowd VRT; FIRST CVSS; program safe-harbor statements.
Files in this version
- SKILL.md2.9 KB
Permissions
| Permission | Declared | Found by the scan |
|---|---|---|
| Reads files | No | No |
| Writes files | No | No |
| Runs shell commands | No | No |
| Uses the network | No | No |
| Uses connectors | No | No |
| Drives a browser | No | No |
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.
| Version | Published | Commit | SHA-256 | Signature | Permission change |
|---|---|---|---|---|---|
| v2026.10.14-ee0e0c5 | Nov 13, 2026 | ee0e0c5 | b2b1ae82 | Signed | – |
More from NoorQureshi
All from this publisherMore in Web and bug bounty
See the category- src-hunterzhaoxuya520/src-hunter5
- owasp-top10-analysissecurityskills/owasp-top10-analysis5
- testing-for-xml-injection-vulnerabilitiesmukul975/testing-for-xml-injection-vulnerabilities5
- offensive-xsssnailsploit/offensive-xss5
- offensive-rcesnailsploit/offensive-rce5
- source-review-techniqueaeondave/source-review-technique5
Ask anything your scope allows.
Create an account, add credits and ask the first question in the chat or the terminal.
- 1/3
Create the account
Individual or company. You can switch to a company later without losing balance or keys.
IndividualCompany - 2/3
Add credits
By card. Pay per token, no subscription.
$5.00minimum deposit - 3/3
Ask
In the chat, or install the CLI and run notholy login in your terminal.
$ notholy login