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

# HardHat C2

JWT認証バイパス、管理者トークン作成、TeamLeadユーザー作成、ImplantInteract端末の悪用、RCEのためのHardHat C2攻略ノート。

HardHat C2 の JWT 認証バイパス、TeamLead ユーザー作成、ImplantInteract のコマンド実行、およびリバースシェル配信に関する侵害メモ。

<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="/ja/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 の ImplantInteract ターミナル悪用、whoami 検証、リバースシェル実行、SSH authorized_keys 永続化、および侵害後活動に関する RCE メモ。</td><td><a href="/ja/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/ja/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.
