YesWeHack AI policy
YesWeHack's AI policy lets you use LLMs if you keep control of their results and verify findings by hand. Its code of conduct puts AI slop at severity 7, the top of its 1 to 7 scale.
The rule, quoted
"Limit testing volume to what is reasonable and maintain control over tools, scanners, payloads, and LLM results."
YesWeHack platform code of conduct, read November 18, 2026
"Spamming a program by submitting reports based on assumptions, AI-generated hypotheses without manual verification."
YesWeHack platform code of conduct, "Program spamming and AI Slop", read November 18, 2026
"Submitting a vulnerability report that includes findings which are of poor quality, and which have not been expertly validated, manually tested, and confirmed by the Security Researcher through reliable methods or sources."
YesWeHack platform code of conduct, read November 18, 2026
What it means for you
| Task | YesWeHack says |
|---|---|
| Read scope and sort notes with AI | Allowed |
| Draft the report with AI | Allowed |
| Submit a finding you did not verify | Not allowed |
| Let an agent submit on its own | Not allowed |
| Paste confidential program data into an outside AI tool | Report data stays confidential under the general rules. |
| Say that you used AI | Not required by the platform; some programs ask |
"Program spamming and AI Slop" sits at severity 7 on the code's 1 to 7 scale, the same level as extortion, and a report marked Spam costs 3 times the submission cost in credits.
More from the policy
"This feature helps limiting the number of low-quality reports submitted on the platform (e.g., AI-generated reports and spam)"
YesWeHack changelog, July 2026, read November 18, 2026
"The program rules define the specific terms of engagement, and all stakeholders must comply with them at all times"
YesWeHack platform code of conduct, read November 18, 2026
Also reads: YesWeHack credits, YesWeHack blog, June 18, 2026. Read November 18, 2026.
Other platforms
HackerOne
Encouraged
permits and encourages the responsible use of AI tools throughout the research workflow
- AI for recon, discovery and reports
- Validate every finding yourself
- Fully autonomous hackbots
- Disclosure of AI use required
Code of Conduct. Updated for AI in May 2026.
Bugcrowd
Allowed
manually review and validate any vulnerability report you've created with the help of GenAI tools
- GenAI to help write reports
- Review every report by hand
- Confidential data in AI tools
- Disclosure of AI use required
Code of Conduct. Modified December 1, 2025.
Intigriti
Encouraged
permitted and encouraged when used responsibly as part of a hacker's workflow
- AI across your workflow
- Disclose when and how you used AI
- Verify the bug yourself
- Unverified or fabricated reports
Community Code of Conduct. Dated March 9, 2026.