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-file-parser-chainMalware and ransomware analysis

competition-file-parser-chain

⁨Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for file uploads, imports, previews, archive extraction, format conversion, parser invocation, and deserialization chains. Use when the user asks to inspect an upload or import path, trace archive extraction, preview or con⁩

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-file-parser-chain

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

SignatureSigned, ed25519
JeZJb73YX2…zDzgL8Bw==The CLI checks the SHA-256 and the signature before it writes a file.
Package306a33b5…5b3166f5
306a33b51e07…65ff5b3166f53 files · ⁦2.0 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-file-parser-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 following a file from ingress through every parser, extractor, converter, or deserializer boundary that matters.

Reply in Simplified Chinese unless the user explicitly requests English.

Quick Start

  1. Preserve the original upload and every derived artifact separately.
  2. Map the chain in order: ingress, temp storage, archive extraction, format conversion, parser call, deserialization, and final consumer.
  3. Record filenames, MIME guesses, extensions, temp paths, and parser choices before mutating anything.
  4. Separate client-visible validation from backend parser behavior.
  5. Reproduce the smallest file-processing chain that yields the decisive branch or artifact.

Workflow

1. Map File Ingress And Derivation

  • Record request shape, multipart names, content type, filename, temp paths, upload staging, and storage keys.
  • Note every derived artifact: extracted archive member, converted preview, generated thumbnail, temp document, or deserialized object.
  • Keep original file and each derivative labeled separately.

2. Trace Parser And Conversion Boundaries

  • Show which parser, converter, extractor, or deserializer runs at each step.
  • Record parser-specific decisions driven by extension, MIME, magic bytes, schema, archive member names, or embedded metadata.
  • Distinguish parsing success, preview success, conversion success, and business-logic acceptance.

3. Reduce To The Decisive File Chain

  • Compress the result to the smallest sequence: upload -> derived artifact -> parser boundary -> resulting effect.
  • State clearly whether the decisive weakness lives in archive handling, MIME inference, file conversion, path resolution, or deserialization.
  • If the chain becomes mostly a generic async worker problem after enqueue, hand off to the tighter queue or worker skill.

Read This Reference

  • Load references/file-parser-chain.md for the ingress checklist, parser checklist, and evidence packaging.

What To Preserve

  • Original uploads, derived files, temp paths, storage keys, parser names, and conversion steps
  • The exact boundary where backend behavior diverges from user-visible validation
  • One minimal replayable file-processing sequence that reaches the decisive effect

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

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