S05
Signing certificate mismatchValidated
A wrong expected certificate raises tamper_signature_mismatch.
Validatedandroid
How to read this page
A scenario is one test case: prepare the environment, run the steps, then compare the expected result (written before the run) with the observed result (copied from the run, with screenshots).
- S05 · S
- Run on a simulator or emulator — a virtual device on a computer.
- Validated
- Run, and the result matched what was expected.
Why it matters
A re-packaged app is signed with a different key. This is the main signal for repackaging.
Environment
- App
- Example app (Expo SDK 57, React Native 0.86)
- Device
- Pixel 9 Pro emulator (sdk_gphone16k_arm64), API 37
- Build
- Debug, installed with adb
- Library
- 0.2.0
Setup
Prepare the environment.Then run the steps.
- 01Turn on the example app’s Android tamper demo, which expects a certificate of all zeros.
Steps
What to run.What to read.
- 01Read the status and signals.
Expected result · written before the run
Status: compromised1 signal.
Observed result · copied from the run
Status: compromisedObserved 2026-09-30.
evidence
tamper_signature_mismatch: App signing certificate does not match the expected certificateChecks this scenario covers
Every check this test case touches — including ones that aren't expected to fire here. The expected and observed results above say which ones should and did. Each links to how the check works.