Has used .iso files to deploy malicious .lnk files.1
Mark-of-the-Web Bypass T1553.005
- Tactic
- Defense Impairment
- Platform
- Windows
- Version
- 2.0
- Created
- 22 February 2021
- Last modified
- 12 May 2026
- Contributor
- Christiaan Beek, @ChristiaanBeek
Adversaries may abuse specific file formats to subvert Mark-of-the-Web (MOTW) controls. In Windows, when files are downloaded from the Internet, they are tagged with a hidden NTFS Alternate Data Stream (ADS) named Zone.Identifier with a specific value known as the MOTW.[1] Files that are tagged with MOTW are protected and cannot perform certain actions. For example, starting in MS Office 10, if a MS Office file has the MOTW, it will open in Protected View. Executables tagged with the MOTW will be processed by Windows Defender SmartScreen that compares files with an allowlist of well-known executables. If the file is not known/trusted, SmartScreen will prevent the execution and warn the user not to run it.[2][3][4]
Mark-of-the-Web Bypass MITRE reference T1553.005
3 groups have been recorded using this technique. Newest first; each entry carries MITRE’s procedure text and a link to the group’s full record. Click a name to filter the rules below.
Has used ISO and VHD files to deploy malware and to bypass Mark-of-the-Web (MOTW) security measures.1
Has embedded ISO images and VHDX files in HTML to evade Mark-of-the-Web.1
All 3 groups for this technique
2 software entries are documented implementing this technique. MITRE files each as a tool or as malware; newest first, then by how many groups carry them.
Has modified the :Zone.Identifier in the ADS area to zero.1
Has been packaged in ISO files in order to bypass Mark of the Web (MOTW) security measures.1
All 2 software entries for this technique
Offense vs defense T1553.005
Is defensive coverage keeping up with adversary use? Eight counts, each ranked against all 697 ATT&CK techniques. Attack sits left, defense right, so a shape leaning left means adversaries are better documented here than defenders are equipped. Hover any spoke for its percentile and the share of techniques that have more. The timeline below shows when each side arrived.
How it got here
Adversary activity (campaign spans) over cumulative rule output. Each source is plotted independently from zero, so neither line includes the other. Campaign dates are year-granularity.
Mark-of-the-Web Bypass detection strategy DET0257
MITRE names one behaviour worth catching for this technique and breaks it into 1 analytic, one per platform. Each carries the log sources it needs and the fields you tune per environment.
Detect Mark-of-the-Web (MOTW) Bypass via Container and Disk Image Files
AN0712 · Windows
Detects extraction or mounting of container/archive files (e.g., .iso, .vhd, .zip) that originated from the Internet but whose contained files lack Zone.Identifier MOTW tagging. Correlates file creation metadata with subsequent execution of unsigned or untrusted binaries launched outside SmartScreen or Protected View.
Log sources
The data this analytic draws on. You do not need every component — each one you already collect covers part of it. Each links to its ATT&CK record.
| Data component | Name | Channel |
|---|---|---|
| File CreationDC0039 | WinEventLog:Sysmon | EventCode=11 |
| File AccessDC0055 | WinEventLog:Security | EventCode=4663, 4670, 4656 |
| File MetadataDC0059 | WinEventLog:Sysmon | EventCode=15 |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| WatchedExtensions | Adjust monitored file types (e.g., .iso, .vhd, .zip, .gz, .rar) based on enterprise usage |
| TimeWindow | Defines correlation window between extraction/mount and first execution of inner files |
| TrustedExtractionTools | Whitelist known enterprise archivers and deployment mechanisms to reduce false positives |
Consider disabling auto-mounting of disk image files (i.e., .iso, .img, .vhd, and .vhdx). This can be achieved by modifying the Registry values related to the Windows Explorer file associations in order to disable the automatic Explorer "Mount and Burn" dialog for these file extensions. Note: this will not deactivate the mount functionality itself.
Consider blocking container file types at web and/or email gateways. Consider unregistering container file extensions in Windows File Explorer.
Tests from Atomic Red Team (MIT licence) · technique definition