操作系统凭证转储是攻击者通过内存读取、注册表解析或网络协议交互等手段获取系统登录凭证的攻击技术,通常作为横向移动和权限提升的关键环节。传统防御手段聚焦于监控敏感进程(如lsass.exe)的内存访问行为、检测注册表异常操作以及分析可疑的网络身份验证请求。典型缓解措施包括启用LSASS保护模式、监控SAM文件访问日志、部署内存完整性验证机制等。
为规避基于行为特征和日志分析的检测体系,攻击者发展出多维度隐匿技术:通过内存操作隐形化消除磁盘I/O特征,利用系统进程信任链绕过权限审查,借助加密通道和协议模拟隐藏数据外传行为,构建出"无接触、无特征、无日志"的新型凭证窃取范式。
当前凭证转储匿迹技术的核心逻辑聚焦于攻击链的深度解耦与系统信任机制的逆向利用。内存驻留技术通过代码注入与动态加密,将凭证提取过程融入合法进程的生命周期;反射型注入利用无文件特性规避静态检测,同时通过API劫持实现实时凭证捕获;注册表隐蔽提取则突破存储层防护,通过离线解析消除实时监控的有效性;合法进程寄生通过滥用系统管理工具构建攻击行为的"合法外衣"。这些技术的共性在于突破传统安全监控的观测维度:在空间维度上,通过内存驻留和进程寄生模糊攻击载体边界;在时间维度上,采用异步分阶段执行打散行为特征;在数据维度上,利用系统固有协议封装敏感信息流。攻击者通过重构凭证窃取的生命周期,使其每个阶段都具备与系统正常行为的强相似性。
匿迹技术的演进导致传统基于单一日志分析或行为特征匹配的防御体系面临失效风险,防御方需构建内存完整性验证、进程行为基线建模、跨层日志关联分析等能力,并引入硬件级可信执行环境(TEE)保护核心身份认证流程,实现对隐蔽凭证转储的全链路防护。
| 效应类型 | 是否存在 |
|---|---|
| 特征伪装 | ✅ |
| 行为透明 | ✅ |
| 数据遮蔽 | ✅ |
| 时空释痕 | ❌ |
攻击者通过进程伪装和代码混淆技术,使凭证转储工具的行为特征与合法系统进程高度相似。例如将恶意代码注入具有微软数字签名的进程中,利用白名单信任机制绕过安全检测,或通过模拟系统管理工具的内存访问模式隐藏异常操作。
利用零日漏洞(如未公开的LSASS内存读取漏洞)或未文档化的系统API,实现无日志记录的凭证提取。通过直接内核对象操作或硬件虚拟化扩展(如Intel VT-x)绕过用户层监控机制,使防御方无法感知关键安全组件的异常状态。
采用运行时内存加密和传输通道加密双重机制,对窃取的凭证数据进行全生命周期保护。在内存中使用流加密算法动态加密敏感数据,外传时通过TLS隧道或DNS隐蔽信道进行传输,有效对抗内存取证和网络流量分析。
| ID | Name | Description |
|---|---|---|
| G0007 | APT28 |
APT28 regularly deploys both publicly available (ex: Mimikatz) and custom password retrieval tools on victims.[1][2][3] |
| G0050 | APT32 | |
| G0087 | APT39 |
APT39 has used different versions of Mimikatz to obtain credentials.[6] |
| G0001 | Axiom | |
| S0030 | Carbanak | |
| G1003 | Ember Bear |
Ember Bear gathers credential material from target systems, such as SSH keys, to facilitate access to victim environments.[9] |
| S0232 | HOMEFRY | |
| G0065 | Leviathan |
Leviathan has used publicly available tools to dump password hashes, including HOMEFRY.[11] |
| S1146 | MgBot |
MgBot includes modules for dumping and capturing credentials from process memory.[12] |
| S0052 | OnionDuke | |
| S0048 | PinchDuke |
PinchDuke steals credentials from compromised hosts. PinchDuke's credential stealing functionality is believed to be based on the source code of the Pinch credential stealing malware (also known as LdPinch). Credentials targeted by PinchDuke include ones associated many sources such as WinInet Credential Cache, and Lightweight Directory Access Protocol (LDAP).[13] |
| G0033 | Poseidon Group |
Poseidon Group conducts credential dumping on victims, with a focus on obtaining credentials belonging to domain and database servers.[14] |
| S0379 | Revenge RAT |
Revenge RAT has a plugin for credential harvesting.[15] |
| G0054 | Sowbug | |
| G0039 | Suckfly |
Suckfly used a signed credential-dumping tool to obtain victim account credentials.[17] |
| G0131 | Tonto Team |
Tonto Team has used a variety of credential dumping tools.[18] |
| S0094 | Trojan.Karagany |
Trojan.Karagany can dump passwords and save them into |
| ID | Mitigation | Description |
|---|---|---|
| M1015 | Active Directory Configuration |
Manage the access control list for "Replicating Directory Changes All" and other permissions associated with domain controller replication. [20] [21] Consider adding users to the "Protected Users" Active Directory security group. This can help limit the caching of users' plaintext credentials.[22] |
| M1040 | Behavior Prevention on Endpoint |
On Windows 10, enable Attack Surface Reduction (ASR) rules to secure LSASS and prevent credential stealing. [23] |
| M1043 | Credential Access Protection |
With Windows 10, Microsoft implemented new protections called Credential Guard to protect the LSA secrets that can be used to obtain credentials through forms of credential dumping. It is not configured by default and has hardware and firmware system requirements. [24] It also does not protect against all forms of credential dumping. [25] |
| M1041 | Encrypt Sensitive Information |
Ensure Domain Controller backups are properly secured. |
| M1028 | Operating System Configuration |
Consider disabling or restricting NTLM.[26] Consider disabling WDigest authentication.[27] |
| M1027 | Password Policies |
Ensure that local administrator accounts have complex, unique passwords across all systems on the network. |
| M1026 | Privileged Account Management |
Windows:Do not put user or admin domain accounts in the local administrator groups across systems unless they are tightly controlled, as this is often equivalent to having a local administrator account with the same password on all systems. Follow best practices for design and administration of an enterprise network to limit privileged account use across administrative tiers.[28] Linux:Scraping the passwords from memory requires root privileges. Follow best practices in restricting access to privileged accounts to avoid hostile programs from accessing such sensitive regions of memory. |
| M1025 | Privileged Process Integrity |
On Windows 8.1 and Windows Server 2012 R2, enable Protected Process Light for LSA.[29] |
| M1017 | User Training |
Limit credential overlap across accounts and systems by training users and administrators not to use the same password for multiple accounts. |
| ID | Data Source | Data Component | Detects |
|---|---|---|---|
| DS0026 | Active Directory | Active Directory Object Access |
Monitor domain controller logs for replication requests and other unscheduled activity possibly associated with DCSync. [30] [31] [32] Note: Domain controllers may not log replication requests originating from the default domain controller account. [33]. Monitor for replication requests [34] from IPs not associated with known domain controllers. [20] Analytic 1 - Suspicious Replication Requests
|
| DS0017 | Command | Command Execution |
Monitor executed commands and arguments that may attempt to dump credentials using tools like Mimikatz, ProcDump, NTDSUtil, or accessing /proc, /etc/passwd, and /etc/shadow. Analytic 1 - Suspicious command execution involving credential dumping tools. |
| DS0022 | File | File Access |
Monitor file accesses that may indicate attempts to dump credential data from various storage locations such as LSASS memory, SAM, NTDS.dit, LSA secrets, cached domain credentials, proc filesystem, /etc/passwd, and /etc/shadow. Analytic 1 - Unauthorized access to credential storage files.
|
| File Creation |
Monitor for the unexpected creation of memory dump files for processes that may contain credentials. Analytic 1 - Unexpected memory dump file creation.
|
||
| DS0029 | Network Traffic | Network Traffic Content |
Monitor for network protocols [30] [35] and other replication requests [34] from IPs not associated with known domain controllers. [20] Analytic 1 - Anomalous network traffic content related to credential managers
|
| Network Traffic Flow |
Monitor network data for uncommon data flows. Processes utilizing the network that do not normally have network communication or have never been seen before are suspicious. Analytic 1 - Unusual network communication patterns.
|
||
| DS0009 | Process | OS API Execution |
Monitor for API calls that may attempt to dump credentials to obtain account login and credential material, normally in the form of a hash or a clear text password, from the operating system and software. |
| Process Access |
Monitor for unexpected processes interacting with lsass.exe.[36] Common credential dumpers such as Mimikatz access the LSA Subsystem Service (LSASS) process by opening the process, locating the LSA secrets key, and decrypting the sections in memory where credential details are stored. Credential dumpers may also use methods for reflective Process Injection to reduce potential indicators of malicious activity. LinuxTo obtain the passwords and hashes stored in memory, processes must open a maps file in the /proc filesystem for the process being analyzed. This file is stored under the path Analytic 1 - Unauthorized access to credential managers.
|
||
| Process Creation |
Monitor for newly executed processes that may be indicative of credential dumping. Analytic 1 - Unexpected process creation related to credential dumping.
|
||
| DS0024 | Windows Registry | Windows Registry Key Access |
Monitor for the SAM registry key being accessed that may attempt to dump credentials to obtain account login and credential material, normally in the form of a hash or a clear text password, from the operating system and software. Analytic 1 - Unauthorized registry access to SAM key.
|