<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Devladani on Medium]]></title>
        <description><![CDATA[Stories by Devladani on Medium]]></description>
        <link>https://medium.com/@devladani1710?source=rss-88fb87dc0ef6------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*yaY2tSaPzxRwFUfN</url>
            <title>Stories by Devladani on Medium</title>
            <link>https://medium.com/@devladani1710?source=rss-88fb87dc0ef6------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 14:01:51 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@devladani1710/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[The Hidden Threat Behind .IMG Files: How Disk Images Deliver Malware]]></title>
            <link>https://medium.com/@devladani1710/the-hidden-threat-behind-img-files-how-disk-images-deliver-malware-6f5e4268d008?source=rss-88fb87dc0ef6------2</link>
            <guid isPermaLink="false">https://medium.com/p/6f5e4268d008</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[ethical-hacking]]></category>
            <category><![CDATA[phishing]]></category>
            <category><![CDATA[information-security]]></category>
            <category><![CDATA[malware]]></category>
            <dc:creator><![CDATA[Devladani]]></dc:creator>
            <pubDate>Fri, 09 Oct 2026 06:22:31 GMT</pubDate>
            <atom:updated>2026-10-09T06:22:31.376Z</atom:updated>
            <content:encoded><![CDATA[<p><em>By Dev | Cyber Security Analyst | VAPT</em></p><p>[Note: This Write-up has been written under guidance of <a href="https://medium.com/u/87ba6554136e">Rey Patel</a>, <a href="https://medium.com/u/49f68f75c58">Amish Patel</a>, <a href="https://medium.com/u/e33c6c1bd4ed">Hacker4help</a>]</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*x58a0G1iVrB2Z2iKHvggFA.png" /></figure><p>A file called Invoice.img looks like a picture. It is not. It is a virtual drive, and attackers have used that gap between what users expect and what the file really is to deliver remote-access trojans through phishing.</p><h3>TL;DR</h3><ul><li><strong>What is an </strong><strong>.img file?</strong> A raw disk image: a whole filesystem packed into one file.</li><li><strong>Why do attackers use it?</strong> Users expect a picture, Windows 8+ mounts it with a double-click, and security tooling may inspect it poorly.</li><li><strong>Is the file itself malicious?</strong> No. The danger is the content inside and what the victim does with it.</li><li><strong>Does mounting run the malware?</strong> No. A user action (or a separate exploit) is still needed.</li><li><strong>Real-world example:</strong> Phishing .img attachments delivering NanoCore RAT (CrowdStrike, Cisco CSIRT).</li></ul><h3>Introduction</h3><p>In cybersecurity, not every file is what it appears to be.</p><p>Many users associate the word <em>image</em> with photographs or screenshots. An .img file is usually a <strong>disk image</strong>: a bit-for-bit container that can hold a filesystem, folders, executables, scripts and shortcuts.</p><p>Threat actors abuse this in phishing campaigns. CrowdStrike’s Falcon Complete team reported a spike in weaponized disk images (ISO and IMG) during 2019 and early 2020, used to deliver remote access trojans such as NanoCore. Around the same time, Cisco’s CSIRT documented a large malspam campaign using the .IMG extension to evade automated malware analysis and infect machines with RATs.</p><p><strong>The real threat is not the </strong><strong>.img extension. It is the malicious content it carries and how the victim interacts with it.</strong></p><h3>Why .IMG Works as a Delivery Format</h3><p>Before Windows 8, mounting a disk image needed third-party software. Since then, Windows can mount these files natively: the user double-clicks and a new drive letter appears. That convenience is what attackers exploit.</p><ul><li><strong>Misleading name:</strong> “IMG” suggests a picture, lowering suspicion.</li><li><strong>Native mounting:</strong> One double-click exposes the contents as a drive.</li><li><strong>Scanner blind spots:</strong> Some mail gateways and sandboxes do not unpack disk images well, so the payload can pass unexamined.</li><li><strong>Mark-of-the-Web (MOTW):</strong> Files inside a mounted image have historically not inherited the download tag that triggers SmartScreen and Office Protected View.</li><li><strong>Social engineering:</strong> Urgent invoice, shipping or order themes push the victim to act fast.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pvFEAKXe5Cc7UOCcxAjz_A.png" /></figure><blockquote><strong><em>Note on MOTW:</em></strong><em> Windows has changed how MOTW propagates from disk images over time, so behavior depends on the OS version and patch level. Do not assume the bypass works (or is fixed) on a given machine; test it in your own lab.</em></blockquote><p>Disk images do not guarantee that antivirus or email security will be bypassed. Whether an attack succeeds depends on the specific campaign and the defenses in place.</p><h3>How the Attack Works</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vlOR5r8Y3kOT5ZtRGc_IcQ.png" /></figure><h3>1. Initial delivery through phishing</h3><p>The attacker emails an attachment named like Invoice.img or Order_09221.img. The message is written to create urgency so the victim opens it without verifying the sender.</p><h3>2. Mounting the image</h3><p>When the victim double-clicks, Windows mounts the image as a new drive. Inside, there may be a legitimate-looking file next to a malicious executable or a deceptive shortcut.</p><p><strong>Mounting does not execute anything by itself.</strong> The attack only moves forward if the victim launches a file, or if another vulnerability or execution mechanism is involved.</p><h3>3. Payload execution</h3><p>If the victim runs the executable, the payload starts. In the NanoCore campaign CrowdStrike analyzed, an obfuscated AutoIt script acted as a dropper that eventually loaded NanoCore RAT, and persistence was set up with a URL shortcut in the Startup folder.</p><p>Depending on the malware family and the privileges available, a payload may attempt to:</p><ul><li>Establish unauthorized remote access</li><li>Collect sensitive information</li><li>Contact attacker-controlled infrastructure (C2)</li><li>Download additional components</li><li>Persist across reboots</li></ul><p>These capabilities come from the malware, not from the .img format.</p><h3>4. Potential compromise</h3><p>From there the attacker acts within the victim’s privileges and whatever security controls are in the way. A single attachment can become the start of a larger incident.</p><h3>MITRE ATT&amp;CK mapping</h3><ul><li><strong>Delivery:</strong> T1566.001 Phishing: Spearphishing Attachment</li><li><strong>Evasion:</strong> T1553.005 Subvert Trust Controls: Mark-of-the-Web Bypass</li><li><strong>Execution:</strong> T1204.002 User Execution: Malicious File</li><li><strong>Persistence:</strong> T1547.001 Registry Run Keys / Startup Folder</li><li><strong>Command and control:</strong> T1071 Application Layer Protocol</li></ul><h3>How to Analyze a Suspicious .IMG Safely</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZuTdUsFywmiAdhfYZAkDsw.png" /></figure><p>Investigate before executing anything, and only on files you are authorized to examine.</p><h3>Step 1: Identify the real file type</h3><pre>file suspicious.img</pre><p>This gives an initial indication of the format (for example ISO 9660, UDF, FAT). It is a starting point, not proof that the file is safe.</p><h3>Step 2: Hash it</h3><pre>sha256sum suspicious.img</pre><p>Search the hash on reputable sources such as VirusTotal or MalwareBazaar. A known-bad match is strong evidence; an unknown hash proves nothing, because new samples are often unseen.</p><h3>Step 3: Inspect the contents without running anything</h3><p>List the contents without mounting:</p><pre>7z l suspicious.img</pre><p>Or mount read-only inside an analysis VM, blocking execution:</p><pre>sudo mkdir -p /mnt/analysis<br>sudo mount -o ro,loop,noexec,nodev suspicious.img /mnt/analysis<br>ls -laR /mnt/analysis</pre><p>Look for executables, scripts (.js, .vbs, .bat, .ps1), .lnk shortcuts, hidden files, and names that do not match the attachment&#39;s story.</p><h3>Step 4: Analyze extracted files</h3><ul><li><strong>Static analysis:</strong> strings, exiftool, PE inspection, YARA rules. Safe first pass; does not run the sample.</li><li><strong>Reputation checks:</strong> VirusTotal, MalwareBazaar. Compare hashes and read community verdicts.</li><li><strong>Dynamic analysis:</strong> Isolated, disposable VM with snapshots. Network-isolated or simulated network; revert after each run.</li></ul><p>Behavioral analysis belongs only in a properly isolated lab, with protection against host exposure.</p><h3>Defending Against Disk-Image Malware</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wHxVz05tWtwtadMTs71jcg.png" /></figure><ul><li><strong>Email gateway:</strong> Block or quarantine .img, .iso, .vhd and similar attachments unless there is a business need.</li><li><strong>Mounting policy:</strong> Restrict the double-click mount action for standard users through policy; validate the change in a test group first.</li><li><strong>Application control:</strong> Use AppLocker or WDAC so executables cannot run from newly mounted drives or user-writable paths.</li><li><strong>Detection:</strong> Alert on a disk image being mounted followed shortly by process creation from the new drive letter.</li><li><strong>Patching:</strong> Keep Windows and security tooling updated.</li><li><strong>User awareness:</strong> Unexpected invoice plus a disk image attachment should be reported, not opened.</li><li><strong>Incident response:</strong> If a payload ran, isolate the host, preserve evidence, and hunt for persistence (Startup folder, scheduled tasks, Run keys).</li></ul><h3>Conclusion</h3><p>The .img format is not malicious. It is a legitimate technology that attackers repurpose because users trust it, Windows mounts it easily, and some defenses do not look inside it.</p><p>For defenders, the lesson is to examine the actual file, understand the full execution chain, and separate verified evidence from assumptions.</p><p><strong>Never judge a file by its extension alone. Identify it, inspect it, and verify it before trusting it.</strong></p><h3>References</h3><ol><li>CrowdStrike (Guillermo Taibo), <em>Weaponized Disk Image Files: Analysis, Trends and Remediation</em>: <a href="https://www.crowdstrike.com/en-us/blog/weaponizing-disk-image-files-analysis/">https://www.crowdstrike.com/en-us/blog/weaponizing-disk-image-files-analysis/</a></li><li>Cisco CSIRT, <em>Disk Image Deception</em> (Cisco Blogs, January 15, 2020): <a href="https://blogs.cisco.com/security/disk-image-deception-incident-response">https://blogs.cisco.com/security/disk-image-deception-incident-response</a></li><li>MITRE ATT&amp;CK, T1553.005 Mark-of-the-Web Bypass: <a href="https://attack.mitre.org/techniques/T1553/005/">https://attack.mitre.org/techniques/T1553/005/</a></li></ol><p><em>Disclaimer: This article is for cybersecurity education and defensive malware analysis. Investigate only systems and files you are authorized to examine.</em></p><p>#CyberSecurity #MalwareAnalysis #ThreatResearch #InformationSecurity #Phishing</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6f5e4268d008" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>