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 instalaciones+3 en 7 días27 EstrellasMITsincronizado hace 22 horas
Instalar
¿Aún no tienes la CLI de NotHoly? Instálala primero.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install noorqureshi/tradecraft-bugbounty-platformsEscribe en ~/.notholy/skills después de comprobar la firma y el SHA-256.
FirmaFirmado, ed25519
Paqueteb2b1ae82…d1cb49f1
b2b1ae822a23…5d0ed1cb49f11 archivo · 1.6 KBEscaneoBajosin hallazgos
Fuentegithub.com/NoorQureshi/security-skills/tree/main/skills/tradecraft/tradecraft-bugbounty-platforms@ee0e0c5
Esta entrada todavía no está escrita en tu idioma, así que aparece en English.
En esta página
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.
Archivos de esta versión
- SKILL.md2.9 KB
Permisos
| Permiso | Declarado | Hallado en el escaneo |
|---|---|---|
| Lee archivos | No | No |
| Escribe archivos | No | No |
| Ejecuta comandos de shell | No | No |
| Usa la red | No | No |
| Usa conectores | No | No |
| Controla un navegador | No | No |
Hallazgos del escaneo
Revisado el 13 nov 2026
El escaneo no encontró nada que señalar en esta versión.
Un escaneo limpio baja el riesgo, pero no prueba que el paquete sea seguro. Lee lo que instalas.
| Versión | Publicada | Commit | SHA-256 | Firma | Cambio de permisos |
|---|---|---|---|---|---|
| v2026.10.14-ee0e0c5 | 13 nov 2026 | ee0e0c5 | b2b1ae82 | Firmada | – |
Más de NoorQureshi
Todo de este publicadorMás en Web y bug bounty
Ver la categoría- 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
Pregunta todo lo que tu alcance permite.
Crea la cuenta, añade créditos y haz la primera pregunta en el chat o en la terminal.
- 1/3
Crea la cuenta
Individual o empresa. Puedes pasar a empresa después sin perder saldo ni claves.
IndividualEmpresa - 2/3
Añade créditos
Con tarjeta. Pagas por token, sin suscripción.
$5.00recarga mínima - 3/3
Pregunta
En el chat, o instala el CLI y ejecuta notholy login en tu terminal.
$ notholy login