Back to catalog
Static reviewDevelopment

Skill dossier

abusing-shadow-credentials-for-privesc

Source declaration

Take over Active Directory accounts by writing attacker-controlled public keys to msDS-KeyCredentialLink (Shadow Credentials) with pyWhisker, Whisker, or Certipy, then authenticate via PKINIT to recover the target's NT hash without a password reset. Use when BloodHound shows GenericWrite/GenericAll/AddKeyCredentialLink over a target, as a stealthier alternative to ForceChangePassword, during authorized red-team engagements.

The author's original description, preserved in English. It describes intent, not verified performance.

Take over Active Directory accounts by writing attacker-controlled public keys to msDS-KeyCredentialLink (Shadow Credentials) with pyWhisker, Whisker, or Certipy, then authenticate via PKINIT to recover the target's NT hash without a password reset. Use when BloodHound shows GenericWrite/GenericAll/AddKeyCredentialLink over a target, as a stealthier alternative to ForceChangePassword, during authorized red-team engagements.

developmentreferencesscripts

Research summary

Machine-generated analysis; pending human review

These observations come from deterministic source parsing, not a human security review or controlled task evaluation.

Take over Active Directory accounts by writing attacker-controlled public keys to msDS-KeyCredentialLink (Shadow Credentials) with pyWhisker, Whisker, or Certipy, then authenticate via PKINIT to recover the target's NT hash without a password reset. Use when BloodHound shows GenericWrite/GenericAll/AddKeyCredentialLink over a target, as a stealthier alternative to ForceChangePassword, during authorized red-team engagements. This bilingual summary is generated deterministically from collected source text and file structure; it is pending human editorial review.

Review scope

Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.

Observable capabilities

  • Workflow [Source statement; provisional, not tested. Evidence: skills/abusing-shadow-credentials-for-privesc/SKILL.md:L73]
  • Step 1: Confirm the write primitive [Source statement; provisional, not tested. Evidence: skills/abusing-shadow-credentials-for-privesc/SKILL.md:L75]
  • Step 2: Add a Shadow Credential with pyWhisker [Source statement; provisional, not tested. Evidence: skills/abusing-shadow-credentials-for-privesc/SKILL.md:L83]
  • Step 3: Request a TGT via PKINIT [Source statement; provisional, not tested. Evidence: skills/abusing-shadow-credentials-for-privesc/SKILL.md:L97]
  • Step 4: Recover the NT hash [Source statement; provisional, not tested. Evidence: skills/abusing-shadow-credentials-for-privesc/SKILL.md:L106]
  • Step 5: One-shot alternative with Certipy [Source statement; provisional, not tested. Evidence: skills/abusing-shadow-credentials-for-privesc/SKILL.md:L115]
  • Step 6: Use the recovered credential [Source statement; provisional, not tested. Evidence: skills/abusing-shadow-credentials-for-privesc/SKILL.md:L126]
  • Step 7: Chain computer takeover into RBCD (optional) [Source statement; provisional, not tested. Evidence: skills/abusing-shadow-credentials-for-privesc/SKILL.md:L137]
  • Step 8: Clean up [Source statement; provisional, not tested. Evidence: skills/abusing-shadow-credentials-for-privesc/SKILL.md:L146]

Limitations & scope

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Relevant for

  • Practitioners evaluating whether to inspect and install the source skill; this audience is inferred from the product context, not measured usage. [Evidence: skills/abusing-shadow-credentials-for-privesc/SKILL.md:L1-L22]

What ships with the skill

The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.

files
5
Markdown files
3
scripts
1
references
2
Size
29.3 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/abusing-shadow-credentials-for-privesc/LICENSEOther11 KB
skills/abusing-shadow-credentials-for-privesc/references/api-reference.mdReference2.5 KB
skills/abusing-shadow-credentials-for-privesc/references/standards.mdReference1.2 KB
skills/abusing-shadow-credentials-for-privesc/scripts/agent.pyScript5.3 KB
skills/abusing-shadow-credentials-for-privesc/SKILL.mdInstruction9.3 KB

SKILL.md frontmatter

{
  "name": "abusing-shadow-credentials-for-privesc",
  "description": "Take over Active Directory accounts by writing attacker-controlled public keys to msDS-KeyCredentialLink (Shadow Credentials) with pyWhisker, Whisker, or Certipy, then authenticate via PKINIT to recover the target's NT hash without a password reset. Use when BloodHound shows GenericWrite/GenericAll/AddKeyCredentialLink over a target, as a stealthier alternative to ForceChangePassword, during authorized red-team engagements.",
  "domain": "cybersecurity",
  "subdomain": "red-teaming",
  "tags": [
    "red-team",
    "active-directory",
    "shadow-credentials",
    "pywhisker",
    "certipy",
    "pkinit",
    "key-credential-link",
    "privilege-escalation"
  ],
  "version": "1.0",
  "author": "mahipal",
  "license": "Apache-2.0",
  "nist_csf": [
    "PR.AA-05"
  ],
  "mitre_attack": [
    "T1098.005"
  ]
}

A reading of the operating sequence

This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.

  1. 01
    Action

    Overview

    Source-described action candidate under “Overview”; not verified execution.

  2. 02
    Decision

    When to Use

    Source-described decision candidate under “When to Use”; not verified execution.

  3. 03
    Action

    Objectives

    Source-described action candidate under “Objectives”; not verified execution.

  4. 04
    Action

    MITRE ATT&CK Mapping

    Source-described action candidate under “MITRE ATT&CK Mapping”; not verified execution.

  5. 05
    Action

    Workflow

    Source-described action candidate under “Workflow”; not verified execution.

  6. 06
    Output

    Step 1: Confirm the write primitive

    Source-described output candidate under “Step 1: Confirm the write primitive”; not verified execution.

Inspect all extracted workflow candidates (21 candidate steps)
  1. 07
    Action

    Step 2: Add a Shadow Credential with pyWhisker

    Source-described action candidate under “Step 2: Add a Shadow Credential with pyWhisker”; not verified execution.

  2. 08
    Output

    Generate a certificate/key pair and write it into the target's `msDS-KeyCredentialLink`. pyWhisker outputs a PFX you control.

    Source-described output candidate under “Step 2: Add a Shadow Credential with pyWhisker”; not verified execution.

  3. 09
    Decision

    Use Kerberos auth instead of a password if you only hold a ticket:

    Source-described decision candidate under “Step 2: Add a Shadow Credential with pyWhisker”; not verified execution.

  4. 10
    Action

    Step 3: Request a TGT via PKINIT

    Source-described action candidate under “Step 3: Request a TGT via PKINIT”; not verified execution.

  5. 11
    Action

    Use the generated PFX with PKINITtools to obtain a Kerberos TGT for the target.

    Source-described action candidate under “Step 3: Request a TGT via PKINIT”; not verified execution.

  6. 12
    Action

    Step 4: Recover the NT hash

    Source-described action candidate under “Step 4: Recover the NT hash”; not verified execution.

  7. 13
    Action

    Extract the target's NT hash from the AS-REP using the session key from Step 3 (`getnthash.py` reads the AS-REP encryption key, displayed by `gettgtpkinit.py`).

    Source-described action candidate under “Step 4: Recover the NT hash”; not verified execution.

  8. 14
    Action

    Step 5: One-shot alternative with Certipy

    Source-described action candidate under “Step 5: One-shot alternative with Certipy”; not verified execution.

  9. 15
    Action

    Step 6: Use the recovered credential

    Source-described action candidate under “Step 6: Use the recovered credential”; not verified execution.

  10. 16
    Action

    Step 7: Chain computer takeover into RBCD (optional)

    Source-described action candidate under “Step 7: Chain computer takeover into RBCD (optional)”; not verified execution.

  11. 17
    Decision

    When the target is a computer, the recovered key/hash lets you configure Resource-Based Constrained Delegation to impersonate any user to that host.

    Source-described decision candidate under “Step 7: Chain computer takeover into RBCD (optional)”; not verified execution.

  12. 18
    Action

    Step 8: Clean up

    Source-described action candidate under “Step 8: Clean up”; not verified execution.

  13. 19
    Action

    Tools and Resources

    Source-described action candidate under “Tools and Resources”; not verified execution.

  14. 20
    Action

    Detection and Remediation Notes

    Source-described action candidate under “Detection and Remediation Notes”; not verified execution.

  15. 21
    Action

    Validation Criteria

    Source-described action candidate under “Validation Criteria”; not verified execution.

Potential risk surfaces

Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.

Items warrant review

26 deterministic lexical finding(s) require review across the collected text. Findings can occur in documentation and do not prove execution or exploitability; binary-only files were not scanned.

Network accessObserved
File writesObserved
Credential useNot observed
Medium

Network access is mentioned

17 occurrences

A URL or network client appears in this source line. Review destinations, data sent, and trust boundaries; static text cannot establish actual network activity. This rule matched 17 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Note

File modification is described or implemented

9 occurrences

This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 9 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Where context can be spent

Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.

Exact token counts unavailable

All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.

No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.

Controlled evaluation

No controlled evaluation

This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.

Not tested

Use with the source in view

Install command
Inspect the pinned source at https://github.com/mukul975/Anthropic-Cybersecurity-Skills/blob/54a798831d2266a3ca61ce68a7acb80b81160d57/skills/abusing-shadow-credentials-for-privesc/SKILL.md and follow the source repository's installation instructions. No installation was performed or verified by this static analyzer. Source license: Apache-2.0.

Prerequisites

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Example prompts

Not provided

A decision, with its limits attached

Strengths

  • The snapshot contains 5 collected file(s), 3 Markdown file(s), and 1 script file(s), enabling source-level inspection. [Evidence: skills/abusing-shadow-credentials-for-privesc/SKILL.md:L1]

Considerations

  • No functional, security, or model-quality result has been established. Human review must inspect source context and all cited findings before installation or publication.
Research conclusion

Provisional deterministic static inventory only; pending human editorial review and, separately, controlled evaluation. No install recommendation, security assurance, or effectiveness claim is made.

Traceable by construction

The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.

mukul975Anthropic-Cybersecurity-Skillsskills/abusing-shadow-credentials-for-privesc
Source type
Community
Commit
54a798831d2266a3ca61ce68a7acb80b81160d57
Collected
20 Nov 2026
Last checked
20 Nov 2026
Upstream license
Apache-2.0
Repository stars
36,446
Content basis

Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.