T1629.002: Device Driver Firmware

Framework: MITRE ATT&CK · Tactic: Persistence · Total Cataloged Families: 1 · Observed Samples: 1 · Primary Threat Categories: Trojan

Operational Executive Summary

T1629.002 (Device Driver Firmware) is classified under the Persistence tactic within the MITRE ATT&CK framework. Mechanisms that adversaries use to maintain access across reboots, credential changes, and system maintenance, including Registry Run keys, scheduled tasks, and autostart services. In telemetry gathered across enterprise endpoints and the EMBER 2018 benchmark, this technique was weaponized across 1 distinct malware families, totaling over 1 validated samples.

Technical Anatomy & Adversary Tradecraft

Adversaries leverage Device Driver Firmware to accomplish operational objectives while minimizing anomalous forensic footprints. When executing Device Driver Firmware, malicious binaries commonly interact directly with low-level Windows APIs, kernel mode drivers, or native scripting interfaces to bypass traditional file-integrity monitors and static antivirus signatures.

In modern multi-stage campaigns, T1629.002 is frequently observed functioning as an intermediate bridge: initial access payloads (such as spearphishing loaders or exploit macros) execute Device Driver Firmware to establish in-memory execution or persistence before staging secondary ransomware or data-exfiltration implants.

Authoritative MITRE ATT&CK Reference: View official technique documentation, sub-techniques, and adversary groups at https://attack.mitre.org/techniques/T1629/002/.

Detection Engineering & Threat Hunting

Detecting Device Driver Firmware requires telemetry correlation across endpoint detection and response (EDR) agents, Sysmon event streams, and security information event management (SIEM) pipelines:

Process Creation & Lineage: Monitor parent-child process anomalies where unexpected parent binaries (e.g., Office executables, web browsers, or script hosts) spawn command shells or native Windows utilities.
API Hooking & Behavioral Telemetry: EDR platforms should flag rapid calls to memory allocation, process injection, or registry manipulation APIs originating from unbacked executable memory regions.
Network Anomaly Correlation: Cross-reference endpoint execution timestamps with external network socket establishment to identify anomalous beaconing or covert data staging.

SOC Containment & Hardening Guidance

To mitigate risks associated with T1629.002 (Device Driver Firmware) across production infrastructure, security teams should implement the following defensive controls:

Attack Surface Reduction (ASR): Enforce strict application control policies (WDAC or AppLocker) to restrict execution to signed and verified corporate binaries.
Least Privilege & Credential Hygiene: Restrict local administrative privileges to prevent adversaries from tampering with defensive agents or escalating privileges.
Network Microsegmentation: Restrict lateral communication across endpoint VLANs to prevent wormable payloads from utilizing Device Driver Firmware across adjacent network segments.

→ Incident Response Guidance: Read our Active Incident Response Playbook

Cataloged Malware Families Utilizing T1629.002 (1 Families)

The following malware families in the SystemHelpDesk catalog have been verified utilizing T1629.002 (Device Driver Firmware):

1 families

Family	Category	Sample Count	Technical Summary
taptrap	Trojan	`1`	<h3>Executive Summary</h3> TapTrap is a malicious Trojan specifically engineered to target the Android mobile operating system. Operating under the guise of leg...