EMBA

EMBA team (Michael Messner, Pascal Eckmann, Benedikt Kühne and contributors) · also known as EMBA - The firmware security analyzer; Embedded Linux Analyzer

Open sourceActive

Latest GitHub release v2.0.4-summer_edition (2026-09-21); commits to master on 2026-10-29. Not tested. Included for completeness as a firmware tool, not a phone-forensics tool.

EMBA is a command-line firmware security analyser for embedded devices. Its README describes firmware extraction, static analysis, dynamic analysis through emulation, software bill of materials (SBOM) generation and a web-based vulnerability report, aimed at penetration testers, product security teams and developers. It is a firmware security tool, not a phone-forensics tool: the README describes no mobile-device acquisition or evidence-handling workflow, though its module list includes an Android OTA update extractor.

Facts

Websitegithub.com
VendorEMBA team (Michael Messner, Pascal Eckmann, Benedikt Kühne and contributors)
LicenceOpen source (GPL-3.0 (GPLv3 text in LICENSE; the README header states EMBA is licensed under GPLv3))
CategoryAnalysis
FunctionsAnalysis, Reporting
TargetsIoT
Runs onLinux
PricingFree
UsersResearch, Open-source DFIR community
Last activity2026-10-29 · Latest commit to master (merge of PR #2181, workflow-docker-build); latest release v2.0.4-summer_edition (2026-09-21) [github.com]
GitHub activitye-m-b-a/emba · 3,757 stars · last push 2026-11-10 · latest release v2.0.5-ice-edt (2026-11-03) · checked 2026-11-10

Capabilities

  • The README states that EMBA supports the security analysis process from firmware extraction through static analysis and dynamic analysis via emulation, builds the SBOM, and generates a web-based vulnerability report; it is a command-line tool with an optional web report. [github.com]
  • The README states that EMBA automatically discovers possible weak spots such as insecure binaries, outdated software components, potentially vulnerable scripts and hard-coded passwords, and that the tester decides on focus areas and is responsible for verifying and interpreting the results. [github.com]
  • The feature overview lists pre-modules that extract firmware from archives and images, including a module for Android OTA update files (using payload_dumper) and a package extractor for .deb, .ipk and .apk archives. [github.com]
  • The feature overview lists user-mode emulation with qemu to identify software versions (activated separately with the -E switch), system emulation of the embedded device, and a CycloneDX SBOM converter that writes a JSON SBOM from the identified software inventory. [github.com]

Limitations

  • The project's security policy states that EMBA's Docker container runs in privileged mode, that it executes untrusted code from the firmware and builds and boots a firmware image, and that it should be used only on test systems and not on production systems. [github.com]
  • The installation wiki states that EMBA is designed only for x86-64 (not ARM), recommends a virtual machine with current Kali Linux or Ubuntu 22.04/24.04, 16 GB of RAM or more, and 30 to 100 GB of free disk space, and notes the default Docker image is around 20 GB. [github.com]
  • The README describes security analysis of embedded-device firmware images; it lists no phone acquisition, mobile-app artefact parsing or evidence-handling features. [github.com]

Related tools

Sources

  1. GitHub: e-m-b-a/emba (README) (github.com)
  2. EMBA LICENSE (GPLv3) (github.com)
  3. EMBA wiki: Feature overview (github.com)
  4. EMBA wiki: Installation (github.com)
  5. EMBA SECURITY.md (github.com)
  6. GitHub: EMBA releases (v2.0.4-summer_edition, 2026-09-21) (github.com)
  7. GitHub: EMBA master commit history (github.com)

Reviewed . Spotted an error? See the corrections policy.