Pular para o conteúdo
Novo

DeepSeek V4.1 Flash grátis por 7 dias: 10M tokens por dia após recarga de $10 ou mais. Até 30/11.

Como funciona
zhaoxuya520/competition-lsass-ticket-materialAnálise de malware e 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 instalações+3 em 7 dias44,8 mil EstrelasMITsincronizado há 2 horas

Instalar

Ainda não tem a CLI da NotHoly? Instale primeiro.

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

Grava em ⁦~/.notholy/skills⁩ depois de conferir a assinatura e o SHA-256.

AssinaturaAssinado, ed25519
LR6LYx/rBx…raaO5jBg==A CLI confere o SHA-256 e a assinatura antes de gravar qualquer arquivo.
Pacote83ba89ee…c37ede07
83ba89eef180…02dfc37ede073 arquivos · ⁦2.1 KB⁩
VarreduraBaixonenhum achado
A varredura não encontrou nada para apontar nesta versão.Ver a varredura completa
Fontegithub.com/zhaoxuya520/reverse-skill/tree/main/CTF-Sandbox-Orchestrator/competition-lsass-ticket-material@cab634b

Este item ainda não foi escrito no seu idioma, então aparece em 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

Arquivos desta versão

Permissões

PermissãoDeclaradaEncontrada na varredura
Lê arquivosNãoNão
Grava arquivosNãoNão
Roda comandos no shellNãoNão
Usa a redeNãoNão
Usa conectoresNãoNão
Controla um navegadorNãoNão

Achados da varredura

Revisado em 13 de nov. de 2026

A varredura não encontrou nada para apontar nesta versão.

Uma varredura limpa reduz o risco, mas não prova que o pacote é seguro. Leia o que você instala.

VersãoPublicada emCommitSHA-256AssinaturaMudança de permissão
v2026.9.22-cab634b13 de nov. de 2026cab634b83ba89eeAssinada–

Pergunte tudo o que o seu escopo permite.

Crie a conta, adicione créditos e faça a primeira pergunta no chat ou no terminal.

  1. 1/3

    Crie a conta

    Individual ou empresa. Dá para virar empresa depois sem perder saldo nem chaves.

    Pessoa físicaEmpresa
  2. 2/3

    Adicione créditos

    No cartão. Você paga por token, sem assinatura.

    $5.00recarga mínima
  3. 3/3

    Pergunte

    No chat, ou instale o CLI e rode notholy login no terminal.

    $ notholy login