Vai al contenuto
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-chainAnalisi di malware e ransomware

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 installazioni+3 in 7 giorni44,8K StelleMITsincronizzato 2 ore fa

Installa

Non hai ancora la CLI di NotHoly? Installala prima.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install zhaoxuya520/competition-file-parser-chain

Scrive in ⁦~/.notholy/skills⁩ dopo aver controllato la firma e lo SHA-256.

FirmaFirmato, ed25519
JeZJb73YX2…zDzgL8Bw==La CLI controlla lo SHA-256 e la firma prima di scrivere qualsiasi file.
Pacchetto306a33b5…5b3166f5
306a33b51e07…65ff5b3166f53 file · ⁦2.0 KB⁩
ScansioneBassonessuna segnalazione
La scansione non ha trovato nulla da segnalare in questa versione.Vedi la scansione completa
Sorgentegithub.com/zhaoxuya520/reverse-skill/tree/main/CTF-Sandbox-Orchestrator/competition-file-parser-chain@cab634b

Questa voce non è ancora scritta in italiano, quindi è mostrata in un'altra lingua: English.

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

File di questa versione

Permessi

PermessoDichiaratoTrovato dalla scansione
Legge fileNoNo
Scrive fileNoNo
Esegue comandi shellNoNo
Usa la reteNoNo
Usa i connettoriNoNo
Controlla un browserNoNo

Segnalazioni della scansione

Rivisto il 13 nov 2026

La scansione non ha trovato nulla da segnalare in questa versione.

Una scansione pulita abbassa il rischio, ma non prova che il pacchetto sia sicuro. Leggi quello che installi.

VersionePubblicataCommitSHA-256FirmaCambio di permessi
v2026.9.22-cab634b13 nov 2026cab634b306a33b5Firmata–

Chiedi tutto quello che il tuo perimetro consente.

Crea un account, aggiungi crediti e fai la prima domanda in chat o nel terminale.

  1. 1/3

    Crea l'account

    Privato o azienda. Puoi passare ad azienda in seguito senza perdere saldo o chiavi.

    PrivatoAzienda
  2. 2/3

    Aggiungi crediti

    Con carta. Paghi a token, senza abbonamento.

    $5.00ricarica minima
  3. 3/3

    Chiedi

    In chat, oppure installa la CLI ed esegui notholy login nel terminale.

    $ notholy login