Credential Dumping via Symlink to Shadow Copy
Detection of attackers creating symbolic links to Volume Shadow Copies to bypass file system locks and access sensitive system files for credential theft.
Attackers frequently target the Windows Volume Shadow Copy Service (VSS) to bypass file system permissions and locks that prevent direct access to sensitive system files. By creating a symbolic link to an existing shadow copy, an attacker can read restricted files such as the Security Account Manager (SAM) database or the Active Directory NTDS.dit file while the OS is running. This activity is a common precursor to credential dumping, allowing for offline password cracking or Golden Ticket generation. Identifying the execution of the mklink command in conjunction with shadow copy paths provides a high-fidelity signal for unauthorized access attempts that could lead to full domain or system compromise.
Attack Chain
- Attacker gains initial access and executes code with administrative privileges on a Windows host.
- Attacker checks for existing volume shadow copies using
vssadmin list shadowsor WMI queries. - Attacker uses
mklinkto create a symbolic link (junction point) directed at a specific shadow copy volume (e.g., \?\GLOBALROOT\Device\HarddiskVolumeShadowCopyX). - Attacker accesses protected files (e.g., C:\Windows\System32\config\SAM) through the newly created junction point.
- Attacker exfiltrates the hive files or performs local dumping using tools like Mimikatz or SecretsDump.
- Attacker deletes the shadow copy or removes the symbolic link to clean up forensic artifacts.
Impact
Successful exploitation allows an attacker to extract credentials from offline backups, which bypasses many traditional security controls that monitor live file access. This can result in complete account takeover, escalation of privileges, and long-term persistence within the environment, ultimately leading to significant data exfiltration or total domain compromise.
Recommendation
- Deploy the provided Sigma rule to detect the use of
mklinkpointing to shadow copy paths on all Windows endpoints. - Enable process-creation logging (e.g., Sysmon Event ID 1 or Security Event ID 4688) with full command-line arguments.
- Audit administrative account activity and restrict the ability of service accounts to execute
mklinkor interact with VSS.
Immediate actions
Deploy provided Sigma rule for mklink detection
Threat Hunt
Search for mklink executions involving shadow copy strings
Data: Process creation events with command line
Detection coverage 1
Detect Credential Dumping via Symlink to Shadow Copy
highDetects the use of mklink to create symbolic links to Volume Shadow Copies, a common technique for accessing SAM or NTDS.dit files.
Detection queries are available on the platform. Get full rules →