> 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/ports-and-services/ftp-21/ftp-brute-force-attack.md).
# FTP - Ataque de Força Bruta
Notas de teste de força bruta em FTP para Hydra, enumeração de serviço com Nmap, validação de credenciais, verificações de acesso anônimo e auditoria autorizada de senhas.
1. Execute o seguinte comando com [Nmap](/pt-br/reconnaissance/nmap.md) para verificar a versão do FTP e procurar vulnerabilidades conhecidas:
```bash
nmap -sCV -p21 127.0.0.1
```
2. A versão instalada é **7.93** e nenhuma vulnerabilidade conhecida é detectada.
3. Execute um ataque de força bruta com **Hydra**. Minúsculas `-l` ou `-p` significa que o nome de usuário ou a senha é fixa; maiúsculas `-L` ou `-P` significa que o Hydra lê valores de um arquivo.
```bash
hydra -l jordan -P /usr/share/wordlists/rockyou.txt ftp://127.0.0.1 -t 15
```
4. Credenciais válidas são encontradas.
**Força bruta de FTP com listas de palavras comuns de usuários e senhas**
{% code overflow="wrap" %}
```bash
hydra -L /usr/share/metasploit-framework/data/wordlists/common_users.txt -P /usr/share/metasploit-frameword/data/wordlists/unix_passwords.txt 10.10.10.10. -t 4 ftp
```
{% endcode %}
---
# 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/ports-and-services/ftp-21/ftp-brute-force-attack.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.
