tradecraft-duplicate-avoidance
Avoid burning time on bugs that will be closed as duplicates. Load during bug-bounty work when deciding what to report or where to dig, on "will this be a dup", "is this already known", maximizing unique findings. Signals: a mature/popular program, a common vuln on an obvious asset, a recently expan
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-duplicate-avoidanceEscribe en ~/.notholy/skills después de comprobar la firma y el SHA-256.
FirmaFirmado, ed25519
Paquete9b24b770…82653c00
9b24b770e195…376482653c001 archivo · 1.5 KBEscaneoBajosin hallazgos
Fuentegithub.com/NoorQureshi/security-skills/tree/main/skills/tradecraft/tradecraft-duplicate-avoidance@ee0e0c5
Esta entrada todavía no está escrita en tu idioma, así que aparece en English.
En esta página
When it applies
Bug-bounty payouts go to the first valid report. On popular programs the obvious bugs on obvious assets are already found, so the skill is steering toward findings that are still unclaimed — and recognising when a bug you have is likely already in the queue.
Why it works
Duplication is a function of visibility and timing: the more hunters have seen an asset and the longer it's been in scope, the lower your odds on a surface-level bug. Freshness and novelty move you to the front of the line, where the same effort actually pays.
Method
- Read the disclosed reports for the program (and the researcher's public activity) to learn what's already been found and what patterns the program pays for.
- Hunt fresh surface: newly added scope, a feature shipped this week, an acquisition's domains —
the crowd hasn't swept these yet. Monitor scope-change and asset feeds (
automation-*). - Go deeper, not wider: a chained/business-logic bug or a variant behind auth is far less likely to be a dup than reflected XSS on the marketing site.
- Vary the obvious: if you find a common bug, look for the non-obvious instance (a second endpoint, a different parameter, a bypass of the partial fix) that others stopped short of.
- Move fast on fresh scope: when a program expands, the first 24-48h are the least duplicated — prioritise then.
- Sanity-check before reporting: does this need no special preconditions and sit on the most obvious asset? If so, assume others found it — raise the bar or add a unique angle.
Gotchas
- "Informative"/duplicate closes still cost you and the triager time — quality over quantity.
- Some programs pay dupes partially or not at all; know the policy (
tradecraft-bugbounty-platforms). - Novelty isn't an excuse for a weak report — a unique bug still needs solid proof (
reporting-*).
Verify success
Before investing in a report you can name why it's likely not a duplicate — fresh asset, behind auth, a chain, or a variant others missed — not just "it's a valid bug".
References
Program disclosure timelines; researcher write-ups on dup rates; the tradecraft-target-selection skill.
Archivos de esta versión
- SKILL.md2.7 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 | 9b24b770 | 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