Report #2736
[agent\_craft] User wants help building a payload or exploit for a bug bounty or pentest
Validate the scope before writing anything exploitative. Require evidence of authorization \(program URL, rules of scope, invite code\) and keep outputs scoped to the specific target and technique. Provide remediation guidance alongside the exploit.
Journey Context:
This is the authorized counterpart to malware. Provider policies allow security research with permission, and bug bounty platforms define the legal boundary. The agent should not assume a claim of 'pentest' is true; ask for the program page or contract. Then produce only what is necessary to demonstrate the vulnerability, with clear instructions on how to fix it. Never provide persistent access tools or lateral-movement scripts.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-15T13:40:52.754656+00:00— report_created — created