Saltar al contenido
Nuevo

DeepSeek V4.1 Flash gratis por 7 días: 10M tokens al día tras una recarga de $10 o más. Hasta el 30/11.

Cómo funciona
zhaoxuya520/competition-lsass-ticket-materialAnálisis de malware y ransomware

competition-lsass-ticket-material

⁨Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for LSASS-resident secrets, Windows logon sessions, Kerberos ticket caches, DPAPI-backed material, SSP artifacts, and replayable credential extraction. Use when the user asks to inspect LSASS memory, recover tickets or logo⁩

v2026.9.22-cab634b3 instalaciones+3 en 7 días44,8 mil EstrellasMITsincronizado hace 2 horas

Instalar

¿Aún no tienes la CLI de NotHoly? Instálala primero.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install zhaoxuya520/competition-lsass-ticket-material

Escribe en ⁦~/.notholy/skills⁩ después de comprobar la firma y el SHA-256.

FirmaFirmado, ed25519
LR6LYx/rBx…raaO5jBg==La CLI comprueba el SHA-256 y la firma antes de escribir cualquier archivo.
Paquete83ba89ee…c37ede07
83ba89eef180…02dfc37ede073 archivos · ⁦2.1 KB⁩
EscaneoBajosin hallazgos
El escaneo no encontró nada que señalar en esta versión.Ver el escaneo completo
Fuentegithub.com/zhaoxuya520/reverse-skill/tree/main/CTF-Sandbox-Orchestrator/competition-lsass-ticket-material@cab634b

Esta entrada todavía no está escrita en tu idioma, así que aparece en 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 host artifact lives in LSASS, ticket caches, or adjacent credential material and the hard part is proving what is replayable.

Reply in Simplified Chinese unless the user explicitly requests English.

Quick Start

  1. Separate raw credential material from actually usable replay edges.
  2. Record logon session, LUID, ticket cache, package, account, and target service before broad conclusions.
  3. Keep host artifact, extracted secret, replay attempt, and resulting acceptance in one chain.
  4. Distinguish password, hash, ticket, DPAPI secret, SSP residue, and token by where each can actually be used.
  5. Reproduce the smallest host-artifact-to-accepted-privilege path that proves the decisive edge.

Workflow

1. Map LSASS And Adjacent Credential State

  • Record logon sessions, LUIDs, ticket caches, package names, SSPs, DPAPI context, and any service-account material tied to the active path.
  • Note whether the decisive value is a TGT, service ticket, delegated ticket, DPAPI secret, plaintext, hash, or package-specific secret.
  • Keep host source, account context, and cache location tied together.

2. Prove Replay Or Acceptance

  • Show where the extracted material is accepted: SMB, WinRM, service ticket use, DPAPI unwrap, Schannel, or another host or service edge.
  • Record SPN, target host, logon session, ticket flags, encryption type, and resulting privilege or token change.
  • Distinguish material that is present from material that is actually replayable in this path.

3. Reduce To The Decisive Credential Chain

  • Compress the result to the smallest sequence: host artifact -> extracted material -> accepted replay or unwrap -> resulting capability.
  • State clearly whether the decisive edge lives in LSASS memory, ticket cache reuse, DPAPI context, or accepting service behavior.
  • If the task broadens into full host-to-host pivoting, hand back to the tighter Windows pivot skill.

Read This Reference

  • Load references/lsass-ticket-material.md for the session checklist, replay checklist, and evidence packaging.
  • If the task is specifically about DPAPI masterkeys, protected blobs, browser or vault stores, or proving which recovered DPAPI secret is accepted, prefer $competition-dpapi-credential-chain.

What To Preserve

  • LUIDs, session IDs, ticket types, SPNs, encryption types, package names, and cache or memory source
  • The exact accepting host or service and the resulting privilege or logon effect
  • One minimal host-artifact-to-replay sequence that proves the edge

Archivos de esta versión

Permisos

PermisoDeclaradoHallado en el escaneo
Lee archivosNoNo
Escribe archivosNoNo
Ejecuta comandos de shellNoNo
Usa la redNoNo
Usa conectoresNoNo
Controla un navegadorNoNo

Hallazgos del escaneo

Revisado el 13 nov 2026

El escaneo no encontró nada que señalar en esta versión.

Un escaneo limpio baja el riesgo, pero no prueba que el paquete sea seguro. Lee lo que instalas.

VersiónPublicadaCommitSHA-256FirmaCambio de permisos
v2026.9.22-cab634b13 nov 2026cab634b83ba89eeFirmada–

Pregunta todo lo que tu alcance permite.

Crea la cuenta, añade créditos y haz la primera pregunta en el chat o en la terminal.

  1. 1/3

    Crea la cuenta

    Individual o empresa. Puedes pasar a empresa después sin perder saldo ni claves.

    IndividualEmpresa
  2. 2/3

    Añade créditos

    Con tarjeta. Pagas por token, sin suscripción.

    $5.00recarga mínima
  3. 3/3

    Pregunta

    En el chat, o instala el CLI y ejecuta notholy login en tu terminal.

    $ notholy login