competition-relay-coercion-chain

Name: competition-relay-coercion-chain
Author: zhaoxuya520

8.8kstars1.4kforks

How to install competition-relay-coercion-chain?

zhaoxuya520/reverse-skill/competition-relay-coercion-chain

$npx -y skills add zhaoxuya520/reverse-skill --skill competition-relay-coercion-chain

Installs into the current project.

Summary

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 pat

Files · 1

View on GitHub

SKILL.md

1	# Competition Relay Coercion Chain
2
3	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.
4
5	Use this skill when the hard part is proving the full chain from forced authentication to a service that actually accepts the relayed identity.
6
7	Reply in Simplified Chinese unless the user explicitly requests English.
8
9	## Quick Start
10
11	1. Split the chain into coercion source, captured auth, relay target, acceptance point, and resulting effect.
12	2. Record transport, protocol, and service identity at each hop.
13	3. Separate forced-auth generation from relay success and from downstream privilege.
14	4. Keep coercion trigger, relay transcript, and accepting service in one evidence chain.
15	5. Reproduce the smallest coercion-to-acceptance path that proves the decisive edge.
16
17	## Workflow
18
19	### 1. Map The Coercion Source
20
21	- Identify the service, RPC, file path, printer path, WebDAV edge, or protocol trigger that forces authentication.
22	- Record source host, coerced principal, transport, and any environmental preconditions.
23	- Keep one compact note of exactly what causes the auth to leave the source.
24
25	### 2. Trace The Relay Target
26
27	- Record where the authentication lands, how it is forwarded, and which protocol or service consumes it.
28	- Distinguish capture-only, replay-only, and actual relay acceptance.
29	- Keep service name, target host, protocol, relay transcript, and acceptance response tied together.
30
31	### 3. Reduce To The Decisive Relay Chain
32
33	- Compress the result to the smallest sequence: coercion trigger -> relayed auth -> accepted service -> resulting privilege or artifact.
34	- State clearly whether the decisive weakness lives in the coercion source, the relay target, signing settings, or the accepted downstream service.
35	- If the path ultimately becomes a certificate-enrollment issue or a pure Kerberos delegation edge, hand off to the tighter specialized skill.
36
37	## Read This Reference
38
39	- Load `references/relay-coercion-chain.md` for the coercion checklist, relay checklist, and evidence packaging.
40
41	## What To Preserve
42
43	- Coercion trigger details, source host, coerced identity, target host, accepting service, and resulting effect
44	- Relay transcripts, error or acceptance responses, and the exact protocol used at each hop
45	- The smallest replayable coercion-to-acceptance sequence

People who liked this also viewed

6 picks

Type

competition-relay-coercion-chain

8.8kstars1.4kforks

View on GitHub

How to install competition-relay-coercion-chain?

zhaoxuya520/reverse-skill/competition-relay-coercion-chain

$npx -y skills add zhaoxuya520/reverse-skill --skill competition-relay-coercion-chain

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Competition Relay Coercion Chain
2
3	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.
4
5	Use this skill when the hard part is proving the full chain from forced authentication to a service that actually accepts the relayed identity.
6
7	Reply in Simplified Chinese unless the user explicitly requests English.
8
9	## Quick Start
10
11	1. Split the chain into coercion source, captured auth, relay target, acceptance point, and resulting effect.
12	2. Record transport, protocol, and service identity at each hop.
13	3. Separate forced-auth generation from relay success and from downstream privilege.
14	4. Keep coercion trigger, relay transcript, and accepting service in one evidence chain.
15	5. Reproduce the smallest coercion-to-acceptance path that proves the decisive edge.
16
17	## Workflow
18
19	### 1. Map The Coercion Source
20
21	- Identify the service, RPC, file path, printer path, WebDAV edge, or protocol trigger that forces authentication.
22	- Record source host, coerced principal, transport, and any environmental preconditions.
23	- Keep one compact note of exactly what causes the auth to leave the source.
24
25	### 2. Trace The Relay Target
26
27	- Record where the authentication lands, how it is forwarded, and which protocol or service consumes it.
28	- Distinguish capture-only, replay-only, and actual relay acceptance.
29	- Keep service name, target host, protocol, relay transcript, and acceptance response tied together.
30
31	### 3. Reduce To The Decisive Relay Chain
32
33	- Compress the result to the smallest sequence: coercion trigger -> relayed auth -> accepted service -> resulting privilege or artifact.
34	- State clearly whether the decisive weakness lives in the coercion source, the relay target, signing settings, or the accepted downstream service.
35	- If the path ultimately becomes a certificate-enrollment issue or a pure Kerberos delegation edge, hand off to the tighter specialized skill.
36
37	## Read This Reference
38
39	- Load `references/relay-coercion-chain.md` for the coercion checklist, relay checklist, and evidence packaging.
40
41	## What To Preserve
42
43	- Coercion trigger details, source host, coerced identity, target host, accepting service, and resulting effect
44	- Relay transcripts, error or acceptance responses, and the exact protocol used at each hop
45	- The smallest replayable coercion-to-acceptance sequence

People who liked this also viewed

6 picks

Type