MeshProof Forge

Independent device assurance

Know every device
before it ships.

Security assessment for Meshtastic-compatible hardware batches and firmware releases. Test identity consistency, key hygiene and security configuration with reproducible evidence.

Request a pilot Read baseline v0.1

One model. One release. One batch. No private-key collection.

Batch identityKey hygieneConfiguration reviewRelease evidence
Why this exists

A firmware patch cannot repair an untraceable production process.

In 2025, a disclosed Meshtastic vulnerability documented duplicated public and private keys created by several hardware vendors' flashing procedures. Affected direct messages could be captured and decrypted by an attacker with the compromised keys.

The MeshProof Forge pilot tests the release process around the firmware: which build reached which device, whether public-key identities are unique, and whether the submitted security configuration matches an explicit baseline.

Source: NVD CVE-2025-52464

Assessment coverage

From physical batch
to defensible evidence.

Protocol-specific review for manufacturers, assemblers, resellers and integrators shipping preconfigured devices.

01

Key uniqueness

Compare device public-key fingerprints across the batch and flag duplicates or known-compromised public keys.

02

Firmware identity

Record the exact firmware version, build identity, hardware revision and regional radio configuration.

03

Security baseline

Review administrative keys, managed mode, serial access, debug behavior and legacy control paths.

04

Advisory regression

Test the submitted release against applicable disclosed Meshtastic security advisories and failure modes.

05

Batch evidence

Link each tested device to reproducible evidence without collecting or retaining its private key.

06

Remediation retest

Verify agreed fixes once, against the same evidence model and original assessment scope.

Engagement

One controlled assessment.
Three clear stages.

01 / INTAKE

Bind the scope

Define the model, firmware release, sample batch, interfaces, expected configuration and authorized test boundary.

02 / ASSESS

Test the evidence chain

Inspect each submitted device, map applicable advisories and reproduce findings against the exact release.

03 / VERIFY

Remediate and retest

Review fixes with engineering, repeat the affected checks once and issue the final evidence package.

What you receive

Evidence tied to a device, a build and a batch.

A scoped technical record for engineering and product-security decisions. Findings distinguish observed results, inferred risks and untested boundaries.

Open methodology

The assessment standard is public.

Review the control model, evidence requirements, stop conditions, maintenance policy, and an illustrative sample assessment before discussing an engagement.

Open the canonical baseline page
PUBLIC REVIEW DRAFT

Meshtastic Security Baseline v0.1

Core and Enhanced controls across fleet governance, keys, channels, administration, MQTT, monitoring, and response.

Download PDF ↘SAMPLE ASSESSMENT

Sample Fleet Security Assessment

A complete example of evidence language, findings, remediation sequencing, and retest requirements using illustrative data. It is not a client audit.

Download PDF ↘

Design-partner pilot

Test the release before
you build the program.

Fixed scope for a manufacturer or integrator that can provide authorized access to one device model, one firmware release and a representative batch.

1 model1 release1 batch1 retest

Fixed pilot

$15,000
Final scope confirmed after intake.Discuss your batch

Deliberately narrow claims.

MeshProof Forge does not certify Meshtastic, guarantee legal compliance, endorse sensitive or life-critical use, or describe signed provisioning evidence as hardware attestation without a supported root of trust.