bug-bounty-report-writing
Write bug bounty reports that get triaged quickly and rated accurately — clear impact statements, minimal reproduction steps, and professional tone. Use before submitting any vulnerability report.
v2026.8.26-b2b6b523 instalaciones+3 en 7 días0 Estrellassincronizado hace 19 horas
Instalar
¿Aún no tienes la CLI de NotHoly? Instálala primero.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install securityskills/bug-bounty-report-writingEscribe en ~/.notholy/skills después de comprobar la firma y el SHA-256.
FirmaFirmado, ed25519
Paquete4b1b27c9…fd0d15ae
4b1b27c9575f…0a5ffd0d15ae1 archivo · 1.1 KBEscaneoMedio1 hallazgo
- No se encontró licencia
Fuentegithub.com/securityskills/skills/tree/main/bug-bounty/bug-bounty-report-writing@b2b6b52
Esta entrada todavía no está escrita en tu idioma, así que aparece en English.
En esta página
Turn findings into reports that triagers accept quickly and rate fairly.
Report Structure
- Title — vulnerability class + affected asset.
Stored XSS in ticket comment field on support.example.com - Severity & CVSS — your suggested rating with vector string
- Summary — 2–3 sentences: what, where, impact
- Steps to Reproduce — numbered, copy-pasteable, no assumptions
- Impact — what an attacker gains, concretely
- Supporting Material — HTTP requests/responses, screenshots with sensitive data redacted
- Remediation — specific fix recommendation
Rules
- One vulnerability per report. Chains go in one report only when each step is meaningless alone.
- Impact must be demonstrated or rigorously argued, not speculated. "Could lead to RCE" without a path gets downgraded.
- Redact personal data in evidence. Blur user PII; never include other users' data you accessed — report the access, delete the data.
- No markdown-breaking formatting in pasted logs; use fenced code blocks.
- Write for a triager seeing the asset for the first time.
Common Downgrade Causes to Avoid
- Self-XSS or XSS requiring victim-installed software presented as high severity
- Missing
Content-Security-Policyor verbose headers with no demonstrated exploit - Theoretical IDOR without showing two distinct accounts affected
- Automated scanner output pasted without manual verification
After Submission
- Respond to triager questions within the program's SLA
- Request re-review only after substantive new information
- Do not disclose publicly until the program's disclosure policy allows
Archivos de esta versión
- SKILL.md1.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
- MediaLicencia · No se encontró licencia
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.8.26-b2b6b52 | 13 nov 2026 | b2b6b52 | 4b1b27c9 | Firmada | – |
Más de securityskills
Todo de este publicadorMás en Informes y cumplimiento
Ver la categoría- skillduty1g/skill5
- rea-ci-tests-auditmorluto/rea-ci-tests-audit4
- tracking-threat-actor-infrastructuremukul975/tracking-threat-actor-infrastructure4
- performing-authenticated-scan-with-openvasmukul975/performing-authenticated-scan-with-openvas4
- slicing-code-contexttrailofbits/slicing-code-context4
- 1337aeondave/13374
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