Nostr Web Client

#GrapheneOS is still not vulnerable to Cellebrite device exploitation as of the February 2025 support matrix. Appears the documents have leaked online in multiple places. I'll make a larger post summarizing it when I have time.

Here is what you came to see:

Pixels with GrapheneOS remain the only device explicitly mentioned by Cellebrite as being unaffected by their exploits, and remains the only third-party operating system in their documentation entirely. We are the leading contender for mobile security and this is a great real world example.

Here is a blog post that summarises the big pages for Android devices already:

https://osservatorionessuno.org/blog/2025/03/a-deep-dive-into-cellebrite-android-support-as-of-february-2025/#the-february-2025-support-matrix

Contra 9mo ago

Is this in a locked or unlocked state? And do the documents state if the “brute force” unlock will break it? I assume this all depends on the last OS update….

This is what I was able to pull up👇🏻

Reply to this note

Please Login to reply.

Discussion

Final 9mo ago

Locked and unlocked are specified separately in the docs. The image you are describing is for Stock OS pixels that are locked. BFU extraction type means extractions of data available in BFU state and nothing protected by a user credential.

Brute force support isn't a guarantee of breaking the device alone. It just means it is capable of making a quick amount of PIN/password attempts at a short rate of time without throttling or other restrictions. You could use a very secure passphrase that would be impossible to brute force for example.

Contra 9mo ago

Gotcha