> For the complete documentation index, see [llms.txt](https://hacking-notes.jord4n.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hacking-notes.jord4n.pro/pt-br/hacking-tools/exploitation/bug-bounty-and-research-resources.md). # Recursos de Bug Bounty e Pesquisa Recursos de bug bounty e pesquisa de segurança para writeups públicos, bancos de dados de vulnerabilidades, referências de exploits, notas de metodologia e pesquisa de payloads. Use estes recursos para pesquisa de vulnerabilidades, writeups públicos, referências de exploits e inspiração de metodologia. Mantenha os passos de prova técnica nas páginas relevantes de vulnerabilidade ou writeup. ## Recursos
NomeDescriçãoLink oficialImagem de capa
Pentester LandWriteups públicos de bug bounty e referências de pesquisa de segurança.https://pentester.land/image.png
Banco de Dados de Vulnerabilidades da Rapid7Pesquise CVEs, detalhes de vulnerabilidades, referências de exploits e contexto de módulos do Metasploit.https://www.rapid7.com/db/Screenshot 2026-07-20 155200.png
Exploit-DBNavegue por exploits públicos, código de prova de conceito, artigos e referências do Google Hacking Database.https://www.exploit-db.com/Screenshot 2026-07-20 155602.png
HackTricksUse playbooks e caminhos de ataque em diferentes tecnologias e ambientes.https://book.hacktricks.xyz/Screenshot 2026-07-20 155648.png
--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://hacking-notes.jord4n.pro/pt-br/hacking-tools/exploitation/bug-bounty-and-research-resources.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.