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-linux-credential-pivotLinux, cloud and containers

competition-linux-credential-pivot

⁨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 repla⁩

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-linux-credential-pivot

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

SignatureSigned, ed25519
XhzhsVrWUb…oML06SAg==The CLI checks the SHA-256 and the signature before it writes a file.
Packageab88bf5b…bab5c408
ab88bf5bd132…1f53bab5c4083 files · ⁦1.8 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-linux-credential-pivot@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 decisive edge is Linux credential material and where that material is accepted.

Reply in Simplified Chinese unless the user explicitly requests English.

Quick Start

  1. Separate credential storage from accepted privilege.
  2. Record user, process, namespace, socket, key file, and service trust boundary before conclusions.
  3. Keep artifact recovery, replay path, and resulting capability in one chain.
  4. Distinguish local escalation from lateral host pivot.
  5. 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.md for 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

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, 2026cab634bab88bf5bSigned–

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