Drive-by Compromise
- ID
- T1189
- Tactics
- TA0001 Initial Access
- Platforms
- Identity Provider, Linux, macOS, Windows
- Data sources
- Logon Session Creation, Process Creation, Network Connection Creation, Application Log Content, Process Modification, File Creation, Network Traffic Content, User Account Authentication, User Account Metadata
- Source
- attack.mitre.org
- MITRE last modified
- 25 Oct 2025
Adversaries may gain access to a system through a user visiting a website over the normal course of browsing. Multiple ways of delivering exploit code to a browser exist (i.e., Drive-by Target), including:
- A legitimate website is compromised, allowing adversaries to inject malicious code
- Script files served to a legitimate website from a publicly writeable cloud storage bucket are modified by an adversary
- Malicious ads are paid for and served through legitimate ad providers (i.e., Malvertising)
- Built-in web application interfaces that allow user-controllable content are leveraged for the insertion of malicious scripts or iFrames (e.g., cross-site scripting)
Browser push notifications may also be abused by adversaries and leveraged for malicious code injection via User Execution. By clicking "allow" on browser push notifications, users may be granting a website permission to run JavaScript code on their browser.[9][10][11]
Often the website used by an adversary is one visited by a specific community, such as government, a particular industry, or a particular region, where the goal is to compromise a specific user or set of users based on a shared interest. This kind of targeted campaign is often referred to a strategic web compromise or watering hole attack. There are several known examples of this occurring.[12]
Typical drive-by compromise process:
1. A user visits a website that is used to host the adversary controlled content.
2. Scripts automatically execute, typically searching versions of the browser and plugins for a potentially vulnerable version. The user may be required to assist in this process by enabling scripting, notifications, or active website components and ignoring warning dialog boxes.
3. Upon finding a vulnerable version, exploit code is delivered to the browser.
4. If exploitation is successful, the adversary will gain code execution on the user's system unless other protections are in place. In some cases, a second visit to the website after the initial scan is required before exploit code is delivered.
Unlike Exploit Public-Facing Application, the focus of this technique is to exploit software on a client endpoint upon visiting a website. This will commonly give an adversary access to systems on the internal network instead of external systems that may be in a DMZ.
Detection
- DET0176 Drive-by Compromise — Behavior-based, Multi-platform Detection Strategy (T1189)
Data components: Logon Session Creation, Process Creation, Network Connection Creation, Application Log Content, Process Modification, File Creation, Network Traffic Content, User Account Authentication, User Account Metadata
Mitigations (5)
- M1017 User Training
Train users to be aware of access or manipulation attempts by an adversary to reduce the risk of successful spearphishing, social engineering, and other techniques that involve user interaction.
- M1021 Restrict Web-Based Content
Adblockers can help prevent malicious code served through ads from executing in the first place. Script blocking extensions can also help to prevent the execution of JavaScript.
Consider disabling browser push notifications from certain applications and browsers.[1][2][3]
- M1048 Application Isolation and Sandboxing
Browser sandboxes can be used to mitigate some of the impact of exploitation, but sandbox escapes may still exist.[4][5]
Other types of virtualization and application microsegmentation may also mitigate the impact of client-side exploitation. The risks of additional exploits and weaknesses in implementation may still exist for these types of systems.[5]
- M1050 Exploit Protection
Security applications that look for behavior used during exploitation such as Windows Defender Exploit Guard (WDEG) and the Enhanced Mitigation Experience Toolkit (EMET) can be used to mitigate some exploitation behavior.[6] Control flow integrity checking is another way to potentially identify and stop a software exploit from occurring.[7] Many of these protections depend on the architecture and target application binary for compatibility.
- M1051 Update Software
Ensuring that all browsers and plugins are kept updated can help prevent the exploit phase of this technique. Use modern browsers with security features turned on.[8]
Groups (31)
- G0001 Axiom
- G0007 APT28
- G0010 Turla
- G0012 Darkhotel
- G0027 Threat Group-3390
- G0032 Lazarus Group
- G0035 Dragonfly
- G0040 Patchwork
- G0048 RTM
- G0050 APT32
- G0056 PROMETHIUM
- G0059 Magic Hound
- G0060 BRONZE BUTLER
- G0065 Leviathan
- G0066 Elderwood
- G0067 APT37
- G0068 PLATINUM
- G0070 Dark Caracal
- G0073 APT19
- G0077 Leafminer
- G0082 APT38
- G0095 Machete
- G0112 Windshift
- G0124 Windigo
- G0134 Transparent Tribe
- G0138 Andariel
- G1006 Earth Lusca
- G1012 CURIUM
- G1020 Mustard Tempest
- G1034 Daggerfly
- G1035 Winter Vivern
Software (11)
- S0215 KARAE
- S0216 POORAIM
- S0451 LoudMiner
- S0482 Bundlore
- S0483 IcedID
- S0496 REvil
- S0531 Grandoreiro
- S0606 Bad Rabbit
- S1086 Snip3
- S1124 SocGholish
- S9050 Vidar
References
- mac security virus popup
- push notifications -infosecinstitute
- site notifications - krebsonsecurity
- Windows Blogs Microsoft Edge Sandbox
- Ars Technica Pwn2Own 2017 VM Escape
- TechNet Moving Beyond EMET
- Wikipedia Control Flow Integrity
- Browser-updates
- Push notifications - viruspositive
- push notification -mcafee
- push notifications - malwarebytes
- Shadowserver Strategic Web Compromise
