Pular para o conteúdo
Novo

DeepSeek V4.1 Flash grátis por 7 dias: 10M tokens por dia após recarga de $10 ou mais. Até 30/11.

Como funciona
zhaoxuya520/competition-firmware-layoutMobile, firmware e hardware

competition-firmware-layout

⁨Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for firmware images, partition tables, boot chains, update packages, extracted filesystems, embedded configs, and device-facing trust boundaries. Use when the user asks to unpack firmware, map partition layout, inspect boot⁩

v2026.9.22-cab634b3 instalações+3 em 7 dias44,8 mil EstrelasMITsincronizado ontem

Instalar

Ainda não tem a CLI da NotHoly? Instale primeiro.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install zhaoxuya520/competition-firmware-layout

Grava em ⁦~/.notholy/skills⁩ depois de conferir a assinatura e o SHA-256.

AssinaturaAssinado, ed25519
3xwgqS83Um…fQ6QnbBg==A CLI confere o SHA-256 e a assinatura antes de gravar qualquer arquivo.
Pacote892c8dea…bc1f9ffc
892c8dea852b…eac5bc1f9ffc3 arquivos · ⁦2.0 KB⁩
VarreduraBaixonenhum achado
A varredura não encontrou nada para apontar nesta versão.Ver a varredura completa
Fontegithub.com/zhaoxuya520/reverse-skill/tree/main/CTF-Sandbox-Orchestrator/competition-firmware-layout@cab634b

Este item ainda não foi escrito no seu idioma, então aparece em 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 understanding how a firmware image is structured, booted, updated, and turned into reachable device behavior.

Reply in Simplified Chinese unless the user explicitly requests English.

Quick Start

  1. Preserve the original image, extracted partitions, unpacked filesystems, and patched copies as separate artifacts.
  2. Map outer container, partition table, bootloader, kernel, rootfs, config, and update metadata before editing anything.
  3. Track the boot or update chain in order instead of jumping straight to the most interesting file.
  4. Record keys, signatures, offsets, partition boundaries, and init entrypoints in one compact evidence chain.
  5. Reproduce the decisive secret, branch, or reachable service from the smallest extracted path.

Workflow

1. Establish Image Layout

  • Identify container type, partition headers, compression, filesystem type, and any appended or nested images.
  • Record offsets, sizes, hashes, mount points, and partition names before extraction mutates anything.
  • Separate bootloader, kernel, initramfs, rootfs, config blobs, and update metadata as different layers.

2. Trace Boot Or Update Flow

  • Map how control moves from bootloader to kernel to init to services, or from update package to verifier to installer.
  • Note which credentials, certificates, passwords, seeds, or config files are consumed at each stage.
  • Distinguish checked-in firmware intent from the live behavior the extracted files actually support.

3. Reduce To The Decisive Path

  • Show the smallest chain from image boundary to service exposure, auth bypass, debug interface, credential recovery, or flag artifact.
  • Keep extracted filesystems, derived configs, and patch experiments separate from pristine inputs.
  • If the challenge becomes mostly about native crash behavior or exploit primitives after extraction, switch back to the broader reverse skill.

Read This Reference

  • Load references/firmware-layout.md for the layout checklist, boot-chain checklist, and evidence packaging.

What To Preserve

  • Partition offsets, hashes, filesystem types, mount paths, boot entrypoints, and update metadata
  • Extracted secrets, config paths, init scripts, service units, and credentials tied to the stage that consumes them
  • Original images, extracted layers, mounted views, and patched copies as separate artifacts

Arquivos desta versão

Permissões

PermissãoDeclaradaEncontrada na varredura
Lê arquivosNãoNão
Grava arquivosNãoNão
Roda comandos no shellNãoNão
Usa a redeNãoNão
Usa conectoresNãoNão
Controla um navegadorNãoNão

Achados da varredura

Revisado em 13 de nov. de 2026

A varredura não encontrou nada para apontar nesta versão.

Uma varredura limpa reduz o risco, mas não prova que o pacote é seguro. Leia o que você instala.

VersãoPublicada emCommitSHA-256AssinaturaMudança de permissão
v2026.9.22-cab634b13 de nov. de 2026cab634b892c8deaAssinada–

Pergunte tudo o que o seu escopo permite.

Crie a conta, adicione créditos e faça a primeira pergunta no chat ou no terminal.

  1. 1/3

    Crie a conta

    Individual ou empresa. Dá para virar empresa depois sem perder saldo nem chaves.

    Pessoa físicaEmpresa
  2. 2/3

    Adicione créditos

    No cartão. Você paga por token, sem assinatura.

    $5.00recarga mínima
  3. 3/3

    Pergunte

    No chat, ou instale o CLI e rode notholy login no terminal.

    $ notholy login