Vai al contenuto
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
zhaoxuya520/competition-dpapi-credential-chainAnalisi di malware e ransomware

competition-dpapi-credential-chain

⁨Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for DPAPI masterkeys, vault blobs, browser credential stores, protected secrets, domain backup keys, and secret-to-acceptance replay chains. Use when the user asks to inspect DPAPI blobs or masterkeys, recover browser or va⁩

v2026.9.22-cab634b3 installazioni+3 in 7 giorni44,8K StelleMITsincronizzato 2 ore fa

Installa

Non hai ancora la CLI di NotHoly? Installala prima.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install zhaoxuya520/competition-dpapi-credential-chain

Scrive in ⁦~/.notholy/skills⁩ dopo aver controllato la firma e lo SHA-256.

FirmaFirmato, ed25519
6UEUH+Trad…mLOdcLCg==La CLI controlla lo SHA-256 e la firma prima di scrivere qualsiasi file.
Pacchettoa0adf5d7…7b68f99d
a0adf5d7e163…aab97b68f99d3 file · ⁦2.1 KB⁩
ScansioneBassonessuna segnalazione
La scansione non ha trovato nulla da segnalare in questa versione.Vedi la scansione completa
Sorgentegithub.com/zhaoxuya520/reverse-skill/tree/main/CTF-Sandbox-Orchestrator/competition-dpapi-credential-chain@cab634b

Questa voce non è ancora scritta in italiano, quindi è mostrata in un'altra lingua: English.

Use this skill only as a downstream specialization after $ctf-sandbox-orchestrator is already active and has established sandbox assumptions, node ownership, and evidence priorities. If that has not happened yet, return to $ctf-sandbox-orchestrator first.

Use this skill when the decisive Windows secret is DPAPI-protected and the hard part is proving which context unwraps it and where the plaintext is accepted.

Reply in Simplified Chinese unless the user explicitly requests English.

Quick Start

  1. Separate protected blob, masterkey, decrypting context, and final accepting service.
  2. Record SID, user or machine context, masterkey path, vault or browser store, and target replay point before broad conclusions.
  3. Keep DPAPI source artifact, unwrap step, plaintext secret, and acceptance edge in one chain.
  4. Distinguish local user DPAPI, machine DPAPI, domain backup key use, and application-specific wrapping.
  5. Reproduce the smallest DPAPI-to-accepted-access path that proves the decisive edge.

Workflow

1. Map Protected Secret And DPAPI Context

  • Record blob source, masterkey location, SID, protector scope, profile path, credential store, and any application wrapper such as browser encryption or vault metadata.
  • Note whether the decisive value lives in Credential Manager, Vault, browser cookies, browser passwords, Wi-Fi profiles, RDP files, or custom app storage.
  • Keep protected artifact, masterkey candidate, and account or machine context tied together.

2. Prove Unwrap And Acceptance

  • Show how the secret is decrypted: user logon material, machine context, domain backup key, or another recovered protector.
  • Record plaintext type, target host or service, replay method, and resulting session, token, or data access.
  • Distinguish successful blob decryption from actual accepted access.

3. Reduce To The Decisive DPAPI Chain

  • Compress the result to the smallest sequence: protected artifact -> masterkey or unwrap context -> plaintext secret -> accepted replay or access -> resulting capability.
  • State clearly whether the decisive edge lives in masterkey recovery, DPAPI scope confusion, application wrapper handling, or the service that accepts the recovered secret.
  • If the task broadens into generic LSASS ticket material or full Windows pivoting, hand back to the tighter host or pivot skill.

Read This Reference

  • Load references/dpapi-credential-chain.md for the blob checklist, masterkey checklist, and evidence packaging.

What To Preserve

  • Blob paths, masterkey paths, SIDs, protector scope, store names, and application wrapper details
  • The exact accepting service or dataset unlocked by the recovered plaintext
  • One minimal protected-artifact-to-accepted-access sequence that proves the edge

File di questa versione

Permessi

PermessoDichiaratoTrovato dalla scansione
Legge fileNoNo
Scrive fileNoNo
Esegue comandi shellNoNo
Usa la reteNoNo
Usa i connettoriNoNo
Controlla un browserNoNo

Segnalazioni della scansione

Rivisto il 13 nov 2026

La scansione non ha trovato nulla da segnalare in questa versione.

Una scansione pulita abbassa il rischio, ma non prova che il pacchetto sia sicuro. Leggi quello che installi.

VersionePubblicataCommitSHA-256FirmaCambio di permessi
v2026.9.22-cab634b13 nov 2026cab634ba0adf5d7Firmata–

Chiedi tutto quello che il tuo perimetro consente.

Crea un account, aggiungi crediti e fai la prima domanda in chat o nel terminale.

  1. 1/3

    Crea l'account

    Privato o azienda. Puoi passare ad azienda in seguito senza perdere saldo o chiavi.

    PrivatoAzienda
  2. 2/3

    Aggiungi crediti

    Con carta. Paghi a token, senza abbonamento.

    $5.00ricarica minima
  3. 3/3

    Chiedi

    In chat, oppure installa la CLI ed esegui notholy login nel terminale.

    $ notholy login