Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
MediumPublic exploit

Windows File Explorer NTLM Credential Leak via Remote LNK Target Icon Extraction

IdentifiersCVE-2025-50154CWE-200· Exposure of Sensitive Information…

CVE-2025-50154 is a Windows File Explorer information disclosure/spoofing-related vulnerability that bypasses Microsoft’s earlier fix for CVE-2025-24054. According to the provided content, the issue arises when Windows Explorer processes a specially crafted shortcut (LNK) whose displayed icon is not referenced directly through a remote UNC icon path, but instead is embedded as an icon resource inside a remote executable hosted on a UNC path. The shortcut uses a benign local icon setting while its target points to the remote binary. During normal rendering, explorer.exe automatically retrieves the remote executable in order to extract RT_ICON / RT_GROUP_ICON resources from the binary’s .rsrc section. That network retrieval triggers outbound NTLM authentication to the attacker-controlled SMB server without user interaction, leaking NTLMv2 material. The content further states that the remote file may be silently transferred to disk during this process even though it is not executed immediately. Microsoft assigned CVE-2025-50154 after researchers reported that the original patch focused on blocking UNC-based icon rendering but did not prevent Explorer from fetching a remote binary to obtain embedded icon resources.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can disclose NTLMv2 authentication material from a victim system to an attacker-controlled server over the network with zero-click or no meaningful user interaction beyond Explorer rendering the crafted item. The captured NTLM material can be used for offline password cracking or NTLM relay attacks. As noted in the provided content, relay scenarios may enable follow-on privilege escalation, lateral movement, and potentially remote code execution when privileged accounts authenticate. The content also indicates that Explorer may silently stage the remote executable on disk while extracting icon resources, creating an additional foothold for later malicious use even if the binary is not executed immediately.

Mitigation

If you can’t patch tonight, do this now.

Until fully patched, reduce or eliminate outbound NTLM authentication exposure to untrusted hosts, especially over SMB. Block or restrict outbound SMB/UNC access to the internet and untrusted networks, monitor for unexpected explorer.exe-initiated SMB connections, and treat LNK files from untrusted sources as high risk. Limit NTLM usage where feasible, enforce SMB signing and relay protections where applicable, and use network controls to prevent authentication to attacker-controlled servers. Additional hardening around File Explorer handling of untrusted files and user delivery vectors such as email attachments, ZIP archives, and internet downloads can further reduce exposure.

Remediation

Patch, then assume compromise.

Apply Microsoft’s security update that addresses CVE-2025-50154 and any subsequent cumulative or out-of-band updates that fully close the bypass chain. The provided content indicates Microsoft recognized CVE-2025-50154 as a gap left by the original CVE-2025-24054 fix and later issued additional fixes, with further updates expected to address remaining bypasses. Organizations should prioritize patching Windows systems, especially endpoints where File Explorer may process untrusted shortcut files from email, archives, downloads, or network shares.
PUBLIC EXPLOITS

Exploits

2 valid exploits after Mallory filtered fakes, detection scripts, and README-only repos (3 hidden).

VALID 2 / 5 TOTALView more in app
CVE-2025-50154-Aggressor-ScriptMaturityPoCFrameworkCobalt Strike Aggressor ScriptVerified exploit

This repository provides a Cobalt Strike Aggressor script (lnk_weaponizer.cna) and a standalone PowerShell script (standalone_lnk_weaponizer.ps1) for generating weaponized Windows LNK and Library-MS files. The primary purpose is to capture NTLMv2-SSP hashes from Windows systems by tricking users into opening these files, which point to attacker-controlled SMB shares. The Aggressor script integrates with Cobalt Strike, offering both GUI and command-line interfaces for file generation, including a right-click menu for beacons. The Library-MS technique implements a bypass for CVE-2025-24054, allowing for additional evasion of security controls. The PowerShell script supports both single-target and batch operations via CSV. The repository includes documentation (README.md, INSTALL.md), usage scenarios, and sample target files. The exploit is operational, providing real-world red team capabilities for credential capture and lateral movement in Windows environments.

Ash1996xDisclosed Aug 16, 2025aggressor scriptpowershellnetwork
CVE-2025-50154MaturityPoCVerified exploit

This repository provides a proof-of-concept exploit for CVE-2025-50154, a Windows File Explorer zero-click NTLMv2-SSP hash disclosure vulnerability. The exploit consists of a PowerShell script (poc.ps1) that generates a malicious .LNK shortcut file. The shortcut's target path points to a remote SMB share hosting a binary file, while the icon is set to the default Windows shell32.dll. When a victim's Windows Explorer renders the shortcut, it attempts to fetch the icon from the remote file, causing the victim's NTLMv2-SSP hash to be sent to the attacker's SMB server. The repository includes a README with detailed usage instructions and a LICENSE file. The main exploit capability is to trigger NTLM hash disclosure over the network without user interaction, leveraging Windows Explorer's icon rendering behavior.

rubenformationDisclosed Aug 13, 2025powershellnetwork
EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Microsoft CorporationWindows 10 1507operating_system
Microsoft CorporationWindows 10 1607operating_system
Microsoft CorporationWindows 10 1809operating_system
Microsoft CorporationWindows 10 21h2operating_system
Microsoft CorporationWindows 10 22h2operating_system
Microsoft CorporationWindows 11 22h2operating_system
Microsoft CorporationWindows 11 23h2operating_system
Microsoft CorporationWindows 11 24h2operating_system
Microsoft CorporationWindows Server 2008operating_system
Microsoft CorporationWindows Server 2008 R2operating_system
Microsoft CorporationWindows Server 2008 Sp2operating_system
Microsoft CorporationWindows Server 2012operating_system
Microsoft CorporationWindows Server 2012 R2operating_system
Microsoft CorporationWindows Server 2016operating_system
Microsoft CorporationWindows Server 2019operating_system
Microsoft CorporationWindows Server 2022operating_system
Microsoft CorporationWindows Server 2022 23h2operating_system
Microsoft CorporationWindows Server 2025operating_system
Microsoft CorporationWindows Server 23h2operating_system

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity35

Community discussion across Reddit, Mastodon, and other social sources.