Agent Skills
› zhaoxuya520/reverse-skill
› competition-linux-credential-pivot
competition-linux-credential-pivot
GitHub用于CTF沙箱中Linux凭据横向移动分析。追踪SSH密钥、令牌及Socket信任链，复现从凭证恢复至权限提升的完整路径，区分本地提权与主机间跳转，为攻击链提供最小化可复现证据。
Trigger Scenarios
用户要求追踪Linux认证 artifacts 或接受的 token/key 重放
需要解释基于 socket 或服务账户信任边界的 Linux 挑战节点间的横向移动
Install
npx skills add zhaoxuya520/reverse-skill --skill competition-linux-credential-pivot -g -y
SKILL.md
Frontmatter
{
"name": "competition-linux-credential-pivot",
"description": "Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for Linux credential artifacts, service tokens, SSH material, cloud and container secrets, socket-level trust, and host-to-host pivot chains. Use when the user asks to trace Linux auth artifacts, accepted token or key replay, socket or service-account trust edges, sudo or capability abuse, or explain lateral movement across Linux challenge nodes. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here."
}
Competition Linux Credential Pivot
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 edge is Linux credential material and where that material is accepted.
Reply in Simplified Chinese unless the user explicitly requests English.
Quick Start
- Separate credential storage from accepted privilege.
- Record user, process, namespace, socket, key file, and service trust boundary before conclusions.
- Keep artifact recovery, replay path, and resulting capability in one chain.
- Distinguish local escalation from lateral host pivot.
- Reproduce one minimal artifact-to-accepted-access path.
Workflow
1. Map Credential And Trust Artifacts
- Record SSH keys, agent sockets, kubeconfigs, cloud tokens, service-account secrets, env vars, config files, and process memory clues.
- Note sudoers rules, capabilities, setuid binaries, systemd unit context, and namespace boundaries.
- Keep each artifact tied to owner, scope, and expected accepting service.
2. Prove Replay And Pivot
- Show where key, token, socket, or secret is accepted: SSH, API, Unix socket, container runtime, or control-plane endpoint.
- Record host target, protocol, principal, and resulting session or privilege.
- Distinguish authentication success from useful capability gain.
3. Reduce To Decisive Linux Pivot Chain
- Compress to: recovered artifact -> accepted replay path -> pivot host or privilege transition -> resulting capability.
- State whether root cause is weak key handling, token leakage, socket trust, sudo or capability abuse, or namespace crossover.
- If the chain pivots into kernel exploit boundaries, hand off to kernel container escape skill.
Read This Reference
- Load
references/linux-credential-pivot.mdfor artifact checklists, replay matrix, and evidence packaging.
What To Preserve
- Artifact path, owner, scope, accepting service, and resulting principal
- Exact pivot order with protocol and target host or namespace
- One minimal replayable chain proving capability gain
Version History
- 1bec1f2 Current 2026-07-05 18:45
