> For the complete documentation index, see [llms.txt](https://red.infiltr8.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://red.infiltr8.io/ad/movement/credentials/credential-shuffling.md).

# Shuffling

When credentials are found (through [dumping](/ad/movement/credentials/dumping.md) or [cracking](/ad/movement/credentials/cracking.md) for instance), attackers try to use them to obtain access to new resources and eventually [dump new credentials](/ad/movement/credentials/dumping.md). Those new credentials can then be used to access other resources, eventually find other credentials, and so forth. This process can theoretically be repeated until all resources have been carved out and all credentials have been found.

{% content-ref url="/pages/R5IhttI2Ozcp9POjI0uB" %}
[Dumping](/ad/movement/credentials/dumping.md)
{% endcontent-ref %}

As Sean Metcalf says in the part 4 "Credential Theft Shuffle" of adsecurity's "Attack Methods for gaining Domain Admin Rights in Active Directory" article ([link](https://adsecurity.org/?p=2362)):

> I’m calling this section “The Credential Theft Shuffle” (or “Credential Shuffle”) since it is difficult to encapsulate this activity simply. Think of it as a dance. Compromise a single workstation, escalate privileges, and dump credentials. Laterally move to other workstations using dumped credentials, escalate privileges, and dump more credentials.
>
> This usually quickly results in Domain Admin credentials since most Active Directory admins logon to their workstation with a user account and then use RunAs (which places their admin credentials on the local workstation) or RDP to connect to a server \[...].


---

# 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://red.infiltr8.io/ad/movement/credentials/credential-shuffling.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.