Cross-source coverage

T1122 / ATT&CK

Component Object Model Hijacking

ATT&CK has retired this technique. Rules still tag it; the current id is T1546.015 Event Triggered Execution: Component Object Model Hijacking.

1 rule across 1 source.

Showing deprecated rules · back to the default

From MITRE ATT&CK 19.2

The Component Object Model (COM) is a system within Windows to enable interaction between software components through the operating system. Adversaries can use this system to insert malicious code that can be executed in place of legitimate software through hijacking the COM references and relationships as a means for persistence. Hijacking a COM object requires a change in the Windows Registry to replace a reference to a legitimate system component which may cause that component to not work when executed. When that system component is executed through normal system operation the adversary's code will be executed instead. An adversary is likely to hijack objects that are used frequently enough to maintain a consistent level of persistence, but are unlikely to break noticeable functionality within the system as to avoid system instability that could lead to detection.

Tactics
Stealth · Persistence
Platforms
Windows
Telemetry

chronicle/detection-rules

1 rule
Detection Severity Format
detection_of_com_hijacking Undefined YARA-L

Detection rules belong to the projects that publish them and remain under their own licenses. This site indexes and links to them; it claims no rights in them.