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 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-duplicate-avoidanceWrites to ~/.notholy/skills after checking the signature and the SHA-256.
SignatureSigned, ed25519
Package9b24b770…82653c00
9b24b770e195…376482653c001 file · 1.5 KBScanLowno findings
Sourcegithub.com/NoorQureshi/security-skills/tree/main/skills/tradecraft/tradecraft-duplicate-avoidance@ee0e0c5
On this page
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.
Files in this version
- SKILL.md2.7 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 | 9b24b770 | 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