> 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/zh/active-directory/lateral-movement/llmnr-nbt-ns-poisoning.md).

# LLMNR / NBT-NS 投毒

针对 LLMNR / NBT-NS 投毒的 Active Directory 安全笔记，涵盖枚举、Kerberos、凭据、ACL 滥用、横向移动、利用流程和验证步骤。

如果使用有效名称访问，解析首先会通过域控制器的 DNS。

{% code overflow="wrap" %}

```bash
dir //WS01/c$
```

{% endcode %}

如果名称不存在，Windows 随后会尝试通过 `LLMNR` 或 `NBT-NS` 进行广播。

{% code overflow="wrap" %}

```bash
dir //test/c$
```

{% endcode %}

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

在 Linux 上，我们可以监听这些请求并以 `Responder`.

{% code overflow="wrap" %}

```bash
sudo responder -I ens33
```

{% endcode %}

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

如果受害者输入了错误的共享名称，请求就会落到我们的机器上。

{% code overflow="wrap" %}

```bash
dir //test/c$
```

{% endcode %}

然后我们就能获取尝试建立连接的账户的 NTLM 哈希。

<figure><img src="https://1574813340-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-2f583775a8076a1ee87aa4400fee0b32587b1c78%2Fimage%20(3328).png?alt=media" 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 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/zh/active-directory/lateral-movement/llmnr-nbt-ns-poisoning.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.
