Skip to content
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-chainMalware and ransomware analysis

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 installs+3 in 7 days44.8K StarsMITsynced 2 hours ago

Install

No NotHoly CLI yet? Install it first.

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

Writes to ⁦~/.notholy/skills⁩ after checking the signature and the SHA-256.

SignatureSigned, ed25519
1kM3p1r1z0…oK3vfzAg==The CLI checks the SHA-256 and the signature before it writes a file.
Package8660575a…e2e456ba
8660575a4abd…6f38e2e456ba3 files · ⁦1.9 KB⁩
ScanLowno findings
The scan found nothing to flag in this version.See the full scan
Sourcegithub.com/zhaoxuya520/reverse-skill/tree/main/CTF-Sandbox-Orchestrator/competition-relay-coercion-chain@cab634b

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

Files in this version

Permissions

PermissionDeclaredFound by the scan
Reads filesNoNo
Writes filesNoNo
Runs shell commandsNoNo
Uses the networkNoNo
Uses connectorsNoNo
Drives a browserNoNo

Scan findings

Reviewed on Nov 13, 2026

The scan found nothing to flag in this version.

A clean scan lowers the risk but does not prove a package is safe. Read what you install.

VersionPublishedCommitSHA-256SignaturePermission change
v2026.9.22-cab634bNov 13, 2026cab634b8660575aSigned–

Ask anything your scope allows.

Create an account, add credits and ask the first question in the chat or the terminal.

  1. 1/3

    Create the account

    Individual or company. You can switch to a company later without losing balance or keys.

    IndividualCompany
  2. 2/3

    Add credits

    By card. Pay per token, no subscription.

    $5.00minimum deposit
  3. 3/3

    Ask

    In the chat, or install the CLI and run notholy login in your terminal.

    $ notholy login