> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/analytics-alerts/alerts-by-name/uncommon-setwindowshookex-api-invocation-of-a-possible-keylogger.md).

# Uncommon SetWindowsHookEx API invocation of a possible keylogger

### Synopsis

| Field                | Value                                           |
| -------------------- | ----------------------------------------------- |
| Activation Period    | 14 Days                                         |
| Training Period      | 30 Days                                         |
| Test Period          | N/A (single event)                              |
| Deduplication Period | 1 Day                                           |
| Required Data        | XDR Agent with eXtended Threat Hunting (XTH)    |
| ATT\&CK Tactic       | Credential Access (TA0006), Collection (TA0009) |
| ATT\&CK Technique    | Input Capture: Keylogging (T1056.001)           |
| Severity             | Medium                                          |

### Description

A process installed a Windows desktop hook by calling the SetWindowsHookEx API function with an unpopular module. This behavior is commonly seen in keyloggers.

### Attacker's Goals

Attackers can monitor keyboard events as another way for credential gathering or to collect more user data over time for espionage purposes.

### Investigative actions

* Check if the process has a user interface (a visible window).
* Check if the process has an option to set or modify keyboard hot-keys.
* Check if the process is part of a remote control tool.
* Check if the process is a known user application that was updated recently.
* Check if the process is built with AutoHotkey and is known to the user.\* If the process is a scripting engine or a hosting executable, check the actor process command line.
* Investigate the endpoint if the process writes files to disk.


---

# 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://cortex-docs.paloaltonetworks.com/analytics-alerts/alerts-by-name/uncommon-setwindowshookex-api-invocation-of-a-possible-keylogger.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.