# JingMatrix/TEESimulator

Software simulation for Android hardware-backed key pairs with key attestation

Repository: https://github.com/JingMatrix/TEESimulator
Canonical: https://ross.abutalabs.com/products/teesimulator
Language: C++
License Family: other
Topics: android, hardware-simulation, playintegrity, tee, trickystore
Last push: 2026-08-21T16:02:03+00:00

## Health v2 (maintenance only)
Score: 83/100 (v2, computed 2026-09-02T17:46:02.011165+00:00)
- activity 98, release rhythm 97, longevity 26
- inputs: {"age_days": 369, "days_push": 12, "days_rel": 22, "gap_med": 28.5, "n_releases_24m": 7}
- flags: no_license
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 2307, forks 294 (observed 2026-08-28T04:06:35.762810+00:00)

## What it is
TEESimulator is an Android module that defeats hardware-backed key attestation by running AOSP's reference KeyMint trusted application inside the keystore daemon, signing attestations with a user-provided keybox. It selectively intercepts attestation requests for targeted apps while leaving all other keys on the device's real hardware TEE.

## Use cases
- pass Play Integrity checks on a rooted Android device
- simulate hardware-backed key attestation in software
- sign Android key attestation certificates with a custom keybox
- bypass key attestation for specific apps while keeping hardware keys intact
- spoof device identity and patch levels in attestation chains
- make software keys look like TEE-generated keys

## When to choose
- you need per-app control over which apps receive simulated vs real hardware attestation
- you want internally consistent attestation certificates generated the same way a real TEE would
- you need profile-based configuration with different keyboxes and device identities per app
- you want a fail-safe setup where a missing keybox makes the module inert

## When to avoid
- you have no valid keybox to sign attestations with
- you need to spoof the verified boot state or root of trust, which is deliberately not configurable
- you run Android versions older than 10
- you want a simple certificate-patching approach rather than an in-daemon KeyMint simulation

## Facets
- artifact type: plugin
- maturity: active
- function: security, cryptography, middleware
- domain: android-tools, security, privacy
- platform: cpp
- tags: magisk-module, key-attestation, play-integrity, keymint, tee-simulation, keystore, root-detection-bypass, tricky-store, android

## Member repositories
- JingMatrix/TEESimulator (main) score 83

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:06:35.762810+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T02:39:38.834687+00:00, confidence not recorded.
  - readme: https://github.com/JingMatrix/TEESimulator (fetched 2026-08-28T04:06:35.762810+00:00, sha b94f569b96a5)
- Data as of 2026-08-30T08:39:29.467469+00:00.