Skip to content
KitploitKITPLOIT
ツールエクスプロイトブログ
Log in
提出
ツールエクスプロイトブログ
提出

ハッキング、侵入テスト、サイバーセキュリティツールをあなたのセキュリティアーセナルに!

Kitploitはハッキング、サイバーセキュリティ、ペネトレーションテストのツールディレクトリです。最新のプロジェクトアップデートを見つけて、脆弱性の発見、システム分析、テストの自動化、セキュリティの強化を行いましょう。

フィードお問い合わせプライバシー© 2026 Kitploit

ツールディレクトリ

カテゴリ

すべてのカテゴリを見る
Loading categories
ツール/GitHubGitHub/attify/firmware-analysis-toolkit
Embedded Systems SecurityIoT SecurityVulnerability AnalysisReverse EngineeringBinary AnalysisLearning & EducationFirmware Analysis
GitHubattify/firmware-analysis-toolkit

firmware-analysis-toolkit

Firmware security research platform combining binary analysis, taint tracing, and emulation across IoT, edge AI, mobile devices, and robotics.

リポジトリを見る
1.6k2831297日前Kitploit レビュー済み

人気

すべて見る →

コミュニティで最も使われているツールを見つけましょう。

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 究極のOSINTツールキット:調査グラフ、信頼度スコアリング、エイリアスファミリー、マップ、タイムライン、レポート。49個のモジュール、400以上のサイト、APIキー不要。

    891
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    GhostLock ワンタップ実行アプリ(CVE-2026-43499)

    547
  • 3

    ARTEX

    baarai/artex

    プランナー/ワーカーエージェント、資産グラフと探索グラフ、MITMトラフィック記録、脆弱性の再テストを備えたLLMマルチエージェント自律ペネトレーションテストプラットフォーム。

    369
  • 4

    redforge

    cybersecurity91/redforge

    ブラウザ側のレッドチームツールキット。偵察、ペイロード生成、認証情報攻撃、暗号、エンコーディング、エンゲージメントレポート向けの102のオフラインツールを備えています。

    366
  • 5

    looking-glass

    anonghosty/looking-glass

    ShadowserverレポートをMongoDBに取り込み、インタラクティブなマップ、分析、調査結果、アドバイザリ、エグゼクティブダッシュボードとして再生するCSIRTプラットフォーム。

    309
  • 6

    CyberStrikeAI

    ed1s0nz/cyberstrikeai

    AIネイティブなサイバーセキュリティのためのアクションシステム。意図がガバナンスされた実行に変わり、証拠が運用記憶となり、すべての操作が次の操作を改善する。

    282

すべてのツールを探索

ツールコレクションを閲覧

すべてのツールを見る →
共有
要求された言語のコンテンツは利用できません。英語版を表示しています。

FAT — Firmware Analysis Toolkit

FAT release Download the latest release · Changelog · Installation

Firmware Analysis Toolkit is a security research toolkit for investigating firmware security for IoT, Physical AI, Mobile Devices & Robotics. It is primarily built for the "Offensive IoT Exploitation" training conducted by Attify.

It has been built based on actual hands-on field experience of what really matters when it comes to real firmware security investigations that matter.

FAT's goal is not just to build an exceptional world-class cutting-edge toolkit for Firmware Security Research, but also forge professionals and practitioners who operate at their peak, where the tool becomes a cognitive superpower if used in certain ways, while being easy enough to be used by those who are new to the field.

Some of the features include classifying unknown firmware, extracts filesystems, maps trust-relevant code, traces taint, and coordinating QEMU emulation.

What FAT can analyze

  • Unknown blobs and directories: containers, compressed members, high-entropy regions, MCU signals, and candidate firmware files
  • Firmware images: headers, update envelopes, partitions, bootloaders, and image-to-image differences
  • BMC flash images: FIT hash/signature metadata, OpenBMC/MegaRAC markers, CRC-valid U-Boot environments, native JFFS2 recovery, and explicit full-flash/vendor-kernel emulation profiles
  • Extracted Linux filesystems: inventory, startup intent, trust-bearing binaries, crypto material, and string evidence
  • ELF binaries: imports, exports, handler tables, stripped-code sinks, decompilation, and source-to-sink taint
  • Bare-metal and MCU images: vector tables, memory maps, peripheral hints, flash-write authority, and boot handoff evidence
  • Edge AI artifacts: MAGIK/JZDL, TFLite, ONNX, and Qualcomm DLC files plus visible inference runtimes
  • Android applications: APK inventory, discovery leads, locality, capability chains, and handoff boundaries
  • Source repositories: invariant queries, patch guidance, and nearby variant searches

Quick start

Download a binary bundle from Releases, which already contains the matching share/fat runtime data, or install the executable from crates.io with Cargo:

# Fast path: fetch the prebuilt archive for this platform (requires cargo-binstall).
cargo binstall firmware-analysis-toolkit

# From source: compiles the full dependency tree (Rust 1.91 or newer plus a C compiler).
cargo install --locked firmware-analysis-toolkit

Cargo installs only the fat executable. Install the runtime-data bundle for the installed version once; --release downloads the matching fat-data-<version>.zip, verifies its SHA-256, and activates it:

fat data install --release
fat doctor

Building this checkout (development, or for the features listed under Unreleased):

git clone --branch v2.1.0 --depth 1 https://github.com/attify/firmware-analysis-toolkit.git
cd firmware-analysis-toolkit
cargo build --release --locked
cargo install --path crates/fat_cli --locked
python3 scripts/build-runtime-data-bundle.py --output ./dist/fat-data.zip
fat data install --archive ./dist/fat-data.zip
fat doctor

On Arch Linux or Omarchy, start with the Arch installation steps for prerequisite packages and optional tools.

One-Shot Installer for supported hosts:

./scripts/install.sh --install-system-deps

See INSTALL.md for installer options and optional tools.

For features listed under Unreleased, use --branch master in the clone command above. BMC inspection and native JFFS2 recovery were added after v2.0.1.

Quick Command Ref.

  • Help : fat -h
  • Identify a firmware: fat $firmware or fat identify --file $firmware
  • Inspect BMC flash: fat inspect bmc --file $firmware
  • New Project : fat new $firmware
  • Extract file system : fat extract $firmware
  • Analyze : fat analyze $firmware
  • Emulation : fat emulate --project $firmware

First contact with an unknown file

fat ./firmware.bin
fat inspect update --file ./firmware.bin --rootfs ./rootfs --reference ./older.bin

fat ./firmware.bin is shorthand for fat identify --file ./firmware.bin. It gives a compact overview of the file's identity and structure. Add --details for supporting tables. For raw MCU images, inspect the mapping, startup, interrupts, and hardware:

fat inspect mcu --file ./firmware.bin
fat inspect mcu --file ./firmware.bin --details

For BMC flash images, inspect layout, FIT authentication metadata, and stored environments:

fat inspect bmc --file ./flash.mtd
fat inspect bmc --file ./flash.mtd --details

Both inspection workflows support --json for the full structured analysis report. BMC inspection also supports --sarif --fail-on-warning for CI. FIT signatures are reported as stored metadata; cryptographic validity and hardware boot enforcement are not tested.

Run supported BMC services with fat emulate --project <project> --pack bmc-romulus or the explicit ASUS vendor-kernel profile. List profiles with fat rehost profiles list; see BMC emulation for input hashes, adaptations, Redfish checks and debugging.

For disposable lab accounts, fat debug redfish-session checks ReadOnly role enforcement and session revocation with an administrator positive control. fat debug process attaches to a guest daemon through SSH and records its identity and cleanup. See BMC session and process debugging for setup and the Romulus/ASUS results.

Native extraction reconstructs JFFS2 files before inspecting nested compressed content. See Inspecting BMC firmware for the extraction workflow, case-sensitive storage requirements, SARIF output, and environment overrides.

Image to Runtime

The pipeline from Quick start, end to end:

fat new ./firmware.bin
fat extract .fat-projects/firmware
fat analyze .fat-projects/firmware
fat preflight .fat-projects/firmware
fat emulate --project .fat-projects/firmware

Binary triage and data flow

fat r2-triage --file ./usr/sbin/httpd --json
fat taint --file ./www/cgi-bin/diag.cgi --summary
fat taint-query --file ./www/cgi-bin/diag.cgi
fat taint-cross --rootfs ./rootfs
fat taint-cross --rootfs ./rootfs --source-profile ./my-target-models.yaml --state-profile ./my-target-state.yaml

Shell script data flow

fat taint --lang shell --file ./app/init/wifi.sh --summary
fat taint --lang shell --rootfs ./extracted-rootfs --json
fat taint --lang shell --rootfs ./extracted-rootfs --source-profile ./my-target-shell.yaml --severity high

Stripped binaries

Find sinks statically, then prepare runtime hooks for the same addresses:

ツールをダウンロード