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

# HardHat C2

HardHat C2 exploitation notes for JWT authentication bypass, admin token crafting, TeamLead user creation, ImplantInteract terminal abuse, and RCE.

HardHat C2 exploitation notes for JWT authentication bypass, TeamLead user creation, ImplantInteract command execution, and reverse shell delivery.

<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>Authentication Bypass</h4></td><td>HardHat C2 authentication bypass notes for JWT crafting, admin token abuse, TeamLead user creation, API exploitation, and C2 panel takeover.</td><td><a href="/cms/hardhatc2-cms-exploitation/hardhat-c2-authentication-bypass.md">HardHat C2 - Authentication Bypass</a></td></tr><tr><td><h3><i class="fa-helmet-safety" style="color:$primary;">:helmet-safety:</i></h3></td><td><h4>Remote Code Execution</h4></td><td>HardHat C2 RCE notes for ImplantInteract terminal abuse, whoami validation, reverse shell execution, SSH authorized_keys persistence, and post-exploitation.</td><td><a href="/cms/hardhatc2-cms-exploitation/hardhat-c2-remote-code-execution-rce.md">HardHat C2 - Remote Code Execution (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/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.
