> 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/cms/hardhatc2-cms-exploitation.md).

# HardHat C2

HardHat C2 利用笔记，涵盖 JWT 认证绕过、管理员 token 构造、TeamLead 用户创建、ImplantInteract 终端滥用和 RCE。

HardHat C2 利用笔记：JWT 身份验证绕过、TeamLead 用户创建、ImplantInteract 命令执行以及反向 Shell 投递。

<table data-view="cards" data-full-width="false" data-search="false"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><h3><i class="fa-helmet-safety" style="color:$primary;">:helmet-safety:</i></h3></td><td><h4>认证绕过</h4></td><td>HardHat C2 身份验证绕过笔记：JWT 构造、管理员令牌滥用、TeamLead 用户创建、API 利用以及 C2 面板接管。</td><td><a href="/zh/cms/hardhatc2-cms-exploitation/hardhat-c2-authentication-bypass.md">HardHat C2 - 认证绕过</a></td></tr><tr><td><h3><i class="fa-helmet-safety" style="color:$primary;">:helmet-safety:</i></h3></td><td><h4>远程代码执行</h4></td><td>HardHat C2 RCE 笔记：ImplantInteract 终端滥用、whoami 验证、反向 Shell 执行、SSH authorized_keys 持久化以及后渗透。</td><td><a href="/zh/cms/hardhatc2-cms-exploitation/hardhat-c2-remote-code-execution-rce.md">HardHat C2 - 远程代码执行（RCE）</a></td></tr></tbody></table>


---

# 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/cms/hardhatc2-cms-exploitation.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.
