MetalwareSecurity testing

Find vulnerabilities with AI, and trust the results

Metalware doesn't overwhelm security teams with fake vulnerabilities. It provides validated exploitability, reproducible evidence, proof-of-concepts, and actionable results.

AI native

AI built for firmware, empowered with deterministic tools

Metalware uses custom agents designed specifically for firmware analysis, and gives them both guardrails and tools.

Together they push the frontier of automated firmware analysis far beyond a general-purpose AI model.

All security findings are validated against the emulator to avoid hallucinations, noise and false positives.

Dynamic analysis

Intelligent fuzz testing, no setup required

Metalware automatically fuzz tests firmware running in the emulator.

Metalware reproduced Zephyr RTOS CVE-2020-10065 in 42 seconds, without prior knowledge of the CVE.

Metalware fuzzing chart: per-run unique basic blocks rising in steps over the first hours of fuzzing, across 91,913,778 test cases.

Static analysis

Static analysis without the noise

Every static finding is reproduced in emulation, eliminating the noise common with other static scanning approaches.

Metalware defect in an Ethernet MQTT client: risk Critical, peripheral Ethernet_DMA, CWE-787, out-of-bounds write, with a one-line summary: mqtt_parse_incoming accepts an overlong MQTT Remaining Length encoding, so broker-supplied Ethernet data can write past the client's 128-byte receive array into its output ring buffer.

How it compares

No source code, hardware, or harness required

Binary firmware scanners (SCA / SBOM)Source code analyzersProtocol fuzzersManual RE & pen tests
Tests supplier code without sourceYesYesNoPartly (note 1)Yes
Finds unknown vulnerabilitiesYesNoPartly (note 2)YesYes
Automated emulationYesNoNoNoNo
Static analysisYesYesYesNoPartly
Dynamic analysisYesNoNoYesPartly
SBOM / SCANoYesNoNoNo
Tests every attacker input pathYesNoPartly (note 3)Partly (note 4)Partly
Finds hangs and resource exhaustionYesPartly (note 5)Partly (note 6)YesPartly
Every finding verified by running itYesNoNoYesYes
Root cause in the codeYesPartlyYesNoNo
Re-runnable proof of conceptYesNoNoYesPartly
Deduplicated findingsYesPartlyPartlyPartlyNo
Tests every build automaticallyYesYesYesPartlyNo
No hardware or test benchYesYesYesNoPartly
No setup workYesYesPartlyPartlyNo
  1. Note 1: Only tests code reachable from the interfaces it tests
  2. Note 2: Typically high false-positive rates and non-exploitable findings
  3. Note 3: Only with manually configured inputs
  4. Note 4: Only interfaces with a test suite
  5. Note 5: Only known CVEs in identified components
  6. Note 6: Only some classes, such as deadlocks and leaks

Compare with other testing methods

Keep reading

Questions

What kinds of defects does Metalware find?

Security testing finds out-of-bounds writes and reads, null-pointer dereferences, stack overflows, integer underflows, untrusted control-flow transfers and input that can overwrite installed firmware. Each is mapped to the closest CWE where one applies.

Does Metalware test third-party code in the binary?

Yes. It tests the vendor SDKs, radio stacks and RTOS code compiled into the binary along with your own code, and finds defects there whether or not anyone has published them as CVEs.

Can our team reproduce a finding?

Yes, for fuzzing defects: each comes with a POC that runs in GDB, Ghidra or Binary Ninja, with a full execution trace to step through. Each static finding comes with the call stack from its reproduced path.

Bring a build you want tested