Detected by `wu.keyChain.test` v2.0.3

[cxzlw]

Tests

1. Tricky Store(latest release): works fine
2. Tricky Store OSS(latest release): detected
3. TEESimulator(latest release): detected
4. TEESimulator (latest ci dba7af3): detected

Logs

(I am not sure if this is the correct way to export logs...?)

Latest CI debug:

lspbr.zip

Application

cxzlw/gh-issue-attachments/密钥认证.apk

Screenshot

[cxzlw]

Oops, sorry for this duplicate issue... I thought i have checked issues before...

Duplicate of #48, as that issue is closed I am going to keep this issue open.

(target.txt is valid)

[cxzlw]

Attached logs

[rrr333nnn333]

It is working well on my device (Latest CI dba7af3)

Android 15 OneUI 7

Tested modes:

• Generation
• Leaf Hacking

[JingMatrix]

Please flash the latest CI of my LSPosed fork, run this detector, and then export your logs via LSPosed manager.
Currently, I didn't find anything related to TEESimulator in your uploaded log.

[cxzlw]

Please flash the latest CI of my LSPosed fork, run this detector, and then export your logs via LSPosed manager. Currently, I didn't find anything related to TEESimulator in your uploaded log.

lspbr.zip

[0x7F00]

I'm using this last CI vision,and the problem still exists. This problem may only happen to devices that are TEE completely damaged after unlocking, such as OnePlus.

[0x7F00]

But there is no such problem in Tricky Store 1.4.1.

[gavdoc38]

I'm not really sure how reliable this detector is... I tried it and it didn't detect either TS original or TEE-S, but in both cases it warned that a certificate was untrusted (I think, I used translate on image), despite it being a perfectly valid keybox.

[muink]

https://www.virustotal.com/gui/file/c769b1f95ad79eef7050e4d8188fee5b4a1b17885767166326f941ccb0ca8e0e

[ssdgjjtesd255]

I also encountered this issue on teesimulator 3.0 (44)