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-reverse-pwnReverse engineering and fuzzing

competition-reverse-pwn

⁨Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for reverse engineering, malware, DFIR, firmware, pwnable, and native exploit challenges. Use when the user asks to reverse a binary, unpack a sample, inspect a memory dump or PCAP, recover malware behavior, debug a crash, ⁩

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-reverse-pwn

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

SignatureSigned, ed25519
ul67/3putv…pO1XalDg==The CLI checks the SHA-256 and the signature before it writes a file.
Package07d7b564…ff4e62b7
07d7b56471a5…3c85ff4e62b73 files · ⁦2.2 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-reverse-pwn@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 for binary-heavy challenges where the decisive path runs through artifacts, decoded layers, process behavior, crash state, or exploit primitives.

Reply in Simplified Chinese unless the user explicitly requests English.

Quick Start

  1. Preserve the original artifact before unpacking, patching, or instrumenting.
  2. Start with passive triage: type, headers, sections, imports, strings, entropy, resources.
  3. Decide whether the path is reverse-first, DFIR-first, or exploit-first.
  4. Tie every claim to an observable boundary: decode edge, persistence edge, crash edge, or leak edge.
  5. Reproduce the artifact or primitive from a clean baseline.

Workflow

1. Reverse Or Forensic Triage

  • Separate loader, payload, config, and post-decode behavior.
  • Correlate files, memory, logs, registry, services, tasks, IPC, and PCAPs as one graph.
  • Keep decoded or dumped artifacts separate from the pristine sample.

2. Native And Exploit Path

  • Map mitigations, loader behavior, libc or runtime, syscall and IPC surfaces, and protocol framing.
  • Record the primitive, controllable bytes, leak source, target object, and final artifact separately.
  • Compare host, libc, loader, and framing differences before doubting the primitive.

Read This Reference

  • Load references/reverse-pwn.md for triage order, exploit evidence expectations, and common failure modes.
  • If the task is specifically about staged payload boundaries, config blobs, beacon parameters, or decoded IOC fields, prefer $competition-malware-config.
  • If the task is specifically about firmware partitions, boot chains, extracted filesystems, or update-package trust boundaries, prefer $competition-firmware-layout.
  • If the task is specifically about upload parsing, previews, archive extraction, converters, or deserialization chains, prefer $competition-file-parser-chain.
  • If the task is specifically about source maps, emitted bundles, chunk registries, or reconstructing hidden runtime structure from served frontend assets, prefer $competition-bundle-sourcemap-recovery.
  • If the task is specifically about container-to-host boundary crossing, kernel exploit preconditions, namespace or cgroup crossover, or escape primitive verification, prefer $competition-kernel-container-escape.
  • If the task is specifically about reconstructing protocols, streams, or transferred artifacts from packet captures, prefer $competition-pcap-protocol.
  • If the task is specifically about a custom binary or text protocol where replay state, message order, or checksum logic is the real blocker, prefer $competition-custom-protocol-replay.
  • If the task is specifically about reconstructing chronology across EVTX, PCAP, registry, mail, or disk artifacts, prefer $competition-forensic-timeline.

What To Preserve

  • Offsets, hashes, section names, imports, config blobs, mutexes, registry keys
  • Crash offsets, registers, heap or stack shape, leak addresses, and protocol steps
  • Original, decoded, dumped, and instrumented artifacts as separate files

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

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