Live Active security incident? Get immediate response
MITRE ATT&CK® Analytic

AN1596: Analytic 1596

Detect attempts to enumerate kernel modules through lsmod, modinfo, or inspection of /proc/modules and /dev entries. Focus on unusual execution contexts such as unprivileged users or processes outside expected administrative workflows.

EnterpriseAN1596AnalyticObject v1.0 Modified
Glexia's Take

Analyst context for executives and security teams

Analyst confidence Medium

This analytic is about spotting Linux activity that inventories loaded kernel modules or related device/module information. For leaders, the value is not that enumeration is always malicious; it is that unexpected kernel-module discovery can be an early signal that someone is assessing system internals, driver exposure, or privilege-relevant attack surface outside normal administration.

Executive priority

Prioritize this as a validation point for Linux monitoring maturity. Security leaders should ask whether SOC and incident response teams can distinguish expected administrative module checks from unusual activity by unprivileged users or non-administrative processes. This supports operational resilience, vulnerability prioritization, and audit evidence around host visibility, especially on Linux systems that support critical services.

Technical view

For Linux environments, validate visibility into executions of lsmod and modinfo, access or inspection of /proc/modules, and relevant /dev entry enumeration where collected. Because ATT&CK provides no separate detection logic and no tactic mapping for this analytic, teams should treat it as behavior-level coverage: baseline normal administrative workflows, then alert or hunt on module enumeration from unusual users, parent processes, service accounts, scripts, or application contexts.

Likely telemetry

  • Linux process execution telemetry, including command name, command line, user, parent process, and working directory
  • File or path access telemetry for /proc/modules where available
  • File or directory enumeration telemetry for relevant /dev entries where available
  • Authentication/session context to separate interactive administration from unexpected service or unprivileged execution
  • Host inventory or administrative baseline data identifying expected Linux maintenance workflows

Detection direction

  • Tune around unusual execution context rather than the existence of lsmod or modinfo alone, since legitimate administrators may use these tools.
  • Compare activity against known Linux administrative workflows, maintenance windows, and approved automation.
  • Review parent-child process relationships to identify module enumeration launched by unexpected applications, scripts, or service processes.
  • Account for blind spots where endpoint telemetry does not capture file reads under /proc or directory inspection under /dev.
  • Use this analytic as a hunting and triage signal, not a standalone incident conclusion, because no ATT&CK detection text, tactic, or relationship context is supplied.

Mitigation priorities

  • Establish a baseline of approved Linux administration and monitoring activities that legitimately inspect kernel modules.
  • Ensure endpoint or host logging covers process execution and, where feasible, sensitive path access for /proc/modules and relevant /dev locations.
  • Limit privileged administrative access and review whether unprivileged users or service accounts have unexpected ability or need to perform module discovery.
  • Document detection assumptions and evidence sources so compliance and incident response teams can show what Linux host visibility exists and where gaps remain.
  • Use findings from unusual module enumeration to drive follow-up vulnerability, configuration, and privilege reviews rather than assuming malicious intent from this behavior alone.
Analyst notes and limits

The official object is a detection analytic for Linux focused on attempts to enumerate kernel modules through lsmod, modinfo, /proc/modules, and /dev entries, especially from unusual contexts. No relationships, tactics, aliases, or official detection procedure were supplied, so local baselining is essential.

This take is limited to the supplied ATT&CK fields. It does not establish adversary use, active exploitation, business impact, or guaranteed detectability. The ATT&CK object does not provide tactic mapping or detailed detection logic, so organizations must validate relevance against their own Linux telemetry and administrative patterns.

Official MITRE ATT&CK definition

Analytic 1596

Detect attempts to enumerate kernel modules through lsmod, modinfo, or inspection of /proc/modules and /dev entries. Focus on unusual execution contexts such as unprivileged users or processes outside expected administrative workflows.

View the same entry on attack.mitre.org (MITRE-hosted reference; in-page links above use the Glexia ATT&CK library.)

Glexia analysis

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.

Relationship explorer

All related ATT&CK context

No relationships are available in the current normalized data for this object.

Change history

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 .

ATT&CK release
19.1
Object version
1.0
Created
Modified
Raw hash
bef12f857a007468...
Imported snapshots across ATT&CK releases (1)
Release Bundle imported Object version Modified Status Raw hash
19.1 1.0 Current bundle bef12f857a00…
Raw source

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.

Source references

External references and citations

MITRE external references are preserved separately from Glexia analysis so citations remain traceable to their original source records.

  1. [1]
    mitre-attack AN1596
    Open source URL
Source and licensing

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.