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.(Citation: Chrome Extension C2 Malware)(Citation: Abramovsky VSCode Security) 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.
View in MITRE ATT&CK®| Capability ID | Capability Description | Mapping Type | ATT&CK ID | ATT&CK Name | Notes |
|---|---|---|---|---|---|
| CIS-2.5 | Allowlist Authorized Software | mitigates | T1176 | Software Extensions |
Comments
Adversaries install or use malicious browser or IDE extensions to obtain execution or persistence. The implementation to explicitly allowlists authorized extensions and blocks all others, unauthorized extensions cannot be installed or loaded, directly constraining the technique.
References
|
| CIS-7.4 | Perform Automated Application Patch Management | mitigates | T1176 | Software Extensions |
Comments
Updating browsers and IDEs can remove insecure extension mechanisms, but it does not prevent a user or adversary from installing an otherwise permitted malicious extension.
References
|
| CIS-7.3 | Perform Automated Operating System Patch Management | mitigates | T1176 | Software Extensions |
Comments
ATT&CK mentions ensuring operating systems and software are using the most current version.
References
|
| CIS-9.4 | Restrict Unnecessary or Unauthorized Browser and Email Client Extensions | mitigates | T1176 | Software Extensions |
Comments
This technique includes browser extensions, which are directly addressed by the safeguard.
References
|
| CIS-9.1 | Ensure Use of Only Fully Supported Browsers and Email Clients | mitigates | T1176 | Software Extensions |
Comments
Keeping browsers current affects browser extensions.
References
|
| Capability ID | Capability Description | Mapping Type | ATT&CK ID | ATT&CK Name | Notes |
|---|---|---|---|---|---|
| action.malware.variety.Capture app data | Capture data from application or system process | related-to | T1176 | Software Extensions | |
| action.malware.vector.Web application - drive-by | Web via auto-executed or "drive-by" infection. Child of 'Web application'. | related-to | T1176 | Software Extensions |
| Technique ID | Technique Name | Number of Mappings |
|---|---|---|
| T1176.001 | Browser Extensions | 5 |
| T1176.002 | IDE Extensions | 3 |