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-relay-coercion-chainAnalisi di malware e 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 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-relay-coercion-chain

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

FirmaFirmato, ed25519
1kM3p1r1z0…oK3vfzAg==La CLI controlla lo SHA-256 e la firma prima di scrivere qualsiasi file.
Pacchetto8660575a…e2e456ba
8660575a4abd…6f38e2e456ba3 file · ⁦1.9 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-relay-coercion-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 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

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

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