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-relay-coercion-chainAnálisis de malware y ransomware

competition-relay-coercion-chain

⁨Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for forced-auth coercion, relay chains, target selection, NTLM or related acceptance paths, and coercion-to-privilege transitions. Use when the user asks to trace a coercion primitive, follow a relay path, analyze forced au⁩

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-relay-coercion-chain

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

FirmaFirmado, ed25519
1kM3p1r1z0…oK3vfzAg==La CLI comprueba el SHA-256 y la firma antes de escribir cualquier archivo.
Paquete8660575a…e2e456ba
8660575a4abd…6f38e2e456ba3 archivos · ⁦1.9 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-relay-coercion-chain@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 hard part is proving the full chain from forced authentication to a service that actually accepts the relayed identity.

Reply in Simplified Chinese unless the user explicitly requests English.

Quick Start

  1. Split the chain into coercion source, captured auth, relay target, acceptance point, and resulting effect.
  2. Record transport, protocol, and service identity at each hop.
  3. Separate forced-auth generation from relay success and from downstream privilege.
  4. Keep coercion trigger, relay transcript, and accepting service in one evidence chain.
  5. Reproduce the smallest coercion-to-acceptance path that proves the decisive edge.

Workflow

1. Map The Coercion Source

  • Identify the service, RPC, file path, printer path, WebDAV edge, or protocol trigger that forces authentication.
  • Record source host, coerced principal, transport, and any environmental preconditions.
  • Keep one compact note of exactly what causes the auth to leave the source.

2. Trace The Relay Target

  • Record where the authentication lands, how it is forwarded, and which protocol or service consumes it.
  • Distinguish capture-only, replay-only, and actual relay acceptance.
  • Keep service name, target host, protocol, relay transcript, and acceptance response tied together.

3. Reduce To The Decisive Relay Chain

  • Compress the result to the smallest sequence: coercion trigger -> relayed auth -> accepted service -> resulting privilege or artifact.
  • State clearly whether the decisive weakness lives in the coercion source, the relay target, signing settings, or the accepted downstream service.
  • If the path ultimately becomes a certificate-enrollment issue or a pure Kerberos delegation edge, hand off to the tighter specialized skill.

Read This Reference

  • Load references/relay-coercion-chain.md for the coercion checklist, relay checklist, and evidence packaging.

What To Preserve

  • Coercion trigger details, source host, coerced identity, target host, accepting service, and resulting effect
  • Relay transcripts, error or acceptance responses, and the exact protocol used at each hop
  • The smallest replayable coercion-to-acceptance sequence

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 2026cab634b8660575aFirmada–

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