| name | T1176_software-extensions |
| description | Adversaries may abuse software extensions to establish persistent access to victim systems. |
| category | configuration |
| version | 18.1 |
| author | cyberstrike-official |
| tags | ["mitre-attack","enterprise","t1176","persistence","linux","macos","windows"] |
| technique_id | T1176 |
| tactic | persistence |
| all_tactics | ["persistence"] |
| platforms | ["Linux","macOS","Windows"] |
| mitre_url | https://attack.mitre.org/techniques/T1176 |
| tech_stack | ["linux","macos","windows"] |
| cwe_ids | ["CWE-276"] |
| chains_with | ["T1176.001","T1176.002"] |
| prerequisites | [] |
| severity_boost | {"T1176.001":"Chain with T1176.001 for deeper attack path","T1176.002":"Chain with T1176.002 for deeper attack path"} |
T1176 Software Extensions
High-Level Description
Adversaries may abuse software extensions to establish persistent access to victim systems. Software extensions are modular components that enhance or customize the functionality of software applications, including web browsers, Integrated Development Environments (IDEs), and other platforms. Extensions are typically installed via official marketplaces, app stores, or manually loaded by users, and they often inherit the permissions and access levels of the host application.
Malicious extensions can be introduced through various methods, including social engineering, compromised marketplaces, or direct installation by users or by adversaries who have already gained access to a system. Malicious extensions can be named similarly or identically to benign extensions in marketplaces. Security mechanisms in extension marketplaces may be insufficient to detect malicious components, allowing adversaries to bypass automated scanners or exploit trust established during the installation process. Adversaries may also abuse benign extensions to achieve their objectives, such as using legitimate functionality to tunnel data or bypass security controls.
The modular nature of extensions and their integration with host applications make them an attractive target for adversaries seeking to exploit trusted software ecosystems. Detection can be challenging due to the inherent trust placed in extensions during installation and their ability to blend into normal application workflows.
Kill Chain Phase
Platforms: Linux, macOS, Windows
What to Check
How to Test
Atomic Red Team Tests
The following tests are from Atomic Red Team and provide actionable ways to test this technique:
Atomic Test 1: Chrome/Chromium (Developer Mode)
Turn on Chrome/Chromium developer mode and Load Extension found in the src directory