AN0688: Analytic 0688
Detection of unauthorized keylogger behavior through access to `/dev/input`, loading kernel modules (e.g., via insmod), or polling user input devices from non-user shells
Analyst context for executives and security teams
This analytic matters because Linux keylogging can turn ordinary endpoint access into credential and sensitive-data theft. The supplied ATT&CK object focuses on unauthorized interaction with Linux input mechanisms, including access to `/dev/input`, kernel module loading such as `insmod`, or polling user input devices from non-user shells. For leaders, the decision value is whether Linux servers, workstations, jump hosts, or administrator endpoints have enough logging and control depth to identify suspicious input capture behavior before it undermines identity security and incident containment.
Executive priority
Prioritize this where Linux systems are used for administration, engineering, privileged access, or other sensitive workflows. The business question is not only whether malware can be found, but whether the organization can prove who accessed input devices, whether kernel module activity is controlled, and whether SOC/IR teams can distinguish legitimate hardware or driver activity from suspicious keylogger-like behavior. This supports resilience, identity protection, and audit evidence around privileged Linux activity.
Technical view
For SOC, detection engineering, and IR teams, validate Linux telemetry for unauthorized reads or polling of `/dev/input`, kernel module load activity such as use of `insmod`, and user-input device access from shells or processes that are not expected to interact with user sessions. Because no official detection logic is provided, teams should build environment-specific baselines for legitimate device access and module loading, then investigate deviations involving non-user shells, unusual parent processes, unexpected users, or systems handling privileged workflows.
Likely telemetry
- Linux process execution telemetry, including command line, parent process, user, and session context
- File or device access telemetry for `/dev/input` and related input device nodes
- Kernel module load telemetry, including use of tools such as `insmod` where available
- Shell and session telemetry to distinguish interactive user activity from non-user shells
- Endpoint or audit logs capable of tying process activity to host, account, and time context
Detection direction
- Confirm whether Linux hosts generate and retain telemetry for reads or opens against `/dev/input`; absence of this evidence is a major coverage blind spot.
- Tune detections around input device access by non-interactive, service, automation, or unexpected shell contexts rather than treating every access as malicious.
- Monitor kernel module loading events and investigate unexpected use of module-loading utilities such as `insmod`, especially on systems where module changes are rare.
- Baseline legitimate desktop, hardware, accessibility, virtualization, and driver-management behavior to reduce false positives.
- Prioritize alerting on sensitive Linux assets used for administration or privileged access, where keylogging has higher identity and operational risk.
Mitigation priorities
- Restrict access to input device nodes to only users and processes with a valid operational need.
- Limit and monitor kernel module loading on Linux systems, especially where module changes are not part of normal administration.
- Harden privileged Linux endpoints and administrative hosts with least privilege, controlled shell access, and change monitoring.
- Ensure incident response playbooks include collection of process, device access, module load, and session evidence when keylogger behavior is suspected.
- Use logging validation and tabletop exercises to confirm the SOC can investigate this behavior with available Linux telemetry.
Analyst notes and limits
This object is a detection analytic, not a technique description. It is limited to Linux and describes keylogger-like behavior through input device access, kernel module loading, and polling from non-user shells. No tactics, relationships, or official detection query were supplied, so practical implementation depends on local Linux logging, endpoint controls, and asset criticality.
No official detection logic, relationship context, tactics, adversary use, or impact claims were provided. This take should be treated as defensive guidance for validating telemetry and controls around the supplied analytic, not as evidence of active exploitation or guaranteed detection coverage.
Analytic 0688
Detection of unauthorized keylogger behavior through access to `/dev/input`, loading kernel modules (e.g., via insmod), or polling user input devices from non-user shells
How security teams should use this page
Treat this object as behavior context, not an attribution claim. Validate the related groups, software, data sources, and mitigations against official ATT&CK relationships and your own telemetry before making control-coverage decisions.
All related ATT&CK context
No relationships are available in the current normalized data for this object.
Object version and sync metadata
The fields below describe the current mirrored snapshot. When Glexia retains multiple ATT&CK source imports, you can open the table to compare the same object across releases (hashes and MITRE timestamps). For MITRE’s own release notes and roadmap, see ATT&CK resources — Updates .
Imported snapshots across ATT&CK releases (1)
| Release | Bundle imported | Object version | Modified | Status | Raw hash |
|---|---|---|---|---|---|
| 19.1 | 1.0 | Current bundle | 1a26bdd10a4b… |
Mirrored ATT&CK source object
The raw object is retained through the mirrored ATT&CK source bundle and object hash. The raw endpoint returns the exact object from the mirrored bundle when available.
External references and citations
MITRE external references are preserved separately from Glexia analysis so citations remain traceable to their original source records.
-
[1]
mitre-attack AN0688Open source URL
Source: MITRE ATT&CK®. © 2026 The MITRE Corporation. This work is reproduced and distributed with the permission of The MITRE Corporation. MITRE ATT&CK and ATT&CK are registered trademarks of The MITRE Corporation. Glexia is not affiliated with or endorsed by MITRE.