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 installazioni+3 in 7 giorni27 StelleMITsincronizzato 22 ore fa
Installa
Non hai ancora la CLI di NotHoly? Installala prima.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install noorqureshi/tradecraft-bugbounty-platformsScrive in ~/.notholy/skills dopo aver controllato la firma e lo SHA-256.
FirmaFirmato, ed25519
Pacchettob2b1ae82…d1cb49f1
b2b1ae822a23…5d0ed1cb49f11 file · 1.6 KBScansioneBassonessuna segnalazione
Sorgentegithub.com/NoorQureshi/security-skills/tree/main/skills/tradecraft/tradecraft-bugbounty-platforms@ee0e0c5
Questa voce non è ancora scritta in italiano, quindi è mostrata in un'altra lingua: English.
In questa pagina
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.
File di questa versione
- SKILL.md2.9 KB
Permessi
| Permesso | Dichiarato | Trovato dalla scansione |
|---|---|---|
| Legge file | No | No |
| Scrive file | No | No |
| Esegue comandi shell | No | No |
| Usa la rete | No | No |
| Usa i connettori | No | No |
| Controlla un browser | No | No |
Segnalazioni della scansione
Rivisto il 13 nov 2026
La scansione non ha trovato nulla da segnalare in questa versione.
Una scansione pulita abbassa il rischio, ma non prova che il pacchetto sia sicuro. Leggi quello che installi.
| Versione | Pubblicata | Commit | SHA-256 | Firma | Cambio di permessi |
|---|---|---|---|---|---|
| v2026.10.14-ee0e0c5 | 13 nov 2026 | ee0e0c5 | b2b1ae82 | Firmata | – |
Altro da NoorQureshi
Tutto da questo editoreAltro in Web e bug bounty
Vai alla categoria- 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
Chiedi tutto quello che il tuo perimetro consente.
Crea un account, aggiungi crediti e fai la prima domanda in chat o nel terminale.
- 1/3
Crea l'account
Privato o azienda. Puoi passare ad azienda in seguito senza perdere saldo o chiavi.
PrivatoAzienda - 2/3
Aggiungi crediti
Con carta. Paghi a token, senza abbonamento.
$5.00ricarica minima - 3/3
Chiedi
In chat, oppure installa la CLI ed esegui notholy login nel terminale.
$ notholy login