COM Object Hijacking is a Windows persistence and execution technique in which an attacker replaces or redirects a COM registration so a system or application loads malicious code. It works by abusing class registration, CLSIDs or related registry paths, often at startup or when a trusted process activates the object.
How COM Object Hijacking Works
COM Object Hijacking is a Windows persistence technique that abuses how applications resolve Component Object Model registrations. Instead of loading the intended object, the system is redirected to attacker-controlled code through altered class registration or related registry entries. The result is trusted execution flow being bent toward malicious DLL or executable loading.
The technique is attractive because it sits inside normal Windows plumbing. Many COM activations happen in the background, during logon, or when a legitimate process requests a registered component, so malicious redirection can blend into ordinary startup and application behaviour.
Why It Is an Effective Persistence Mechanism
COM hijacking is effective because it leverages a trusted mechanism that the operating system expects to work quietly and repeatedly. If an attacker can change the registration path, the payload may execute whenever the object is requested, which can survive reboots and continue long after the initial compromise.
This is part of a wider family of persistence methods that abuse startup and event-driven execution rather than obvious autorun shortcuts. The operational value to an attacker is durability, low friction, and the ability to hide in configuration data rather than in a visibly suspicious process tree.
For defenders, COM hijacking belongs in the same mental model as other Windows persistence abuse such as run keys, services, WMI subscriptions, and IFEO-style redirection. NHIMG’s Persistence Techniques Guide places it in that broader persistence landscape and helps compare it with adjacent mechanisms.
Where Defenders Look for Exposure
Exposure assessment starts with knowing which COM registrations exist, where they live in the registry, and which of them are touched by high-value applications or privileged processes. A weak point is often not the object itself, but the ability to alter the registration path or replace the referenced component without strong change control.
Teams should also pay attention to user-writable registry locations, unusual CLSID entries, and registrations that point to unexpected binaries, scripts, or non-standard paths. Because many environments have legitimate COM extensibility, the real challenge is distinguishing sanctioned software integration from silent persistence abuse.
For broader Windows hardening context, the technique is closely related to registry permission weaknesses and other configuration-abuse paths. The D3-SCP System Configuration Permissions guide is useful when the question becomes how to prevent unauthorised registry changes that enable this kind of hijack.
Detection and Remediation Patterns
Detection works best when configuration change monitoring is paired with process and module visibility. A suspicious pattern is a COM registration change followed by execution from an unexpected image path, especially when the request originates from a trusted or frequently used process.
Post-incident review should include registry diffs, file integrity checks on referenced binaries, and investigation of any parent process that activated the object. If the hijack was used for persistence, defenders should assume the attacker may also have established other footholds, because persistence techniques often travel in packs.
Hardening guidance is not just about removing the malicious entry. It is also about restricting write access to sensitive configuration paths, auditing registry modifications, and validating that legitimate COM registrations point only to approved components. T1546 Event Triggered Execution Defensive Guide is the most directly relevant reference when you need to detect and disrupt this class of event-triggered persistence.
Threat Hunting and Control Priorities
Hunting should focus on abnormal registration changes, suspicious DLL or executable paths, and COM activations that coincide with logon or other repeatable trigger events. The strongest control objective is to make registry tampering difficult and visible, then verify that execution chains still resolve only to approved objects.
NIST SP 800-53 Rev 5 Security and Privacy Controls is relevant because this technique is ultimately a control problem around configuration integrity, access restriction, and monitoring. On the operational side, defenders should pair that with ATT&CK-aligned detection logic and review registry permissions wherever software extensibility is required.
When COM hijacking is suspected, the safest response is to treat the registry and the referenced binaries as a single attack surface. If either side remains writable by the wrong principal, the persistence mechanism can be re-established even after the visible payload is removed.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
MITRE ATT&CK addresses the attack and risk surface, while NIST SP 800-53 Rev 5 sets the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| MITRE ATT&CK | T1546 — Event Triggered Execution | COM hijacking is a persistence subtype of event-triggered execution. |
| Recommendation — Map COM hijacking to T1546 and hunt for registry-triggered persistence. | ||
| NIST SP 800-53 Rev 5 | CM-5 — Access Restrictions for Change | Registry hijacking depends on unauthorized configuration change paths. |
| AU-6 — Audit Review, Analysis, and Reporting | Detection relies on reviewing registry and process-change evidence. | |
| SI-4 — System Monitoring | COM hijacking is detected through monitoring of execution and configuration drift. | |
| Recommendation — Restrict registry write paths and validate change authorization for COM registrations. Review registry and process audit events to spot COM registration tampering. Monitor COM registration changes and suspicious activation chains. | ||
Related resources from NHI Mgmt Group
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on November 16, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org