Event JSON
{
"id": "0d752c6bd1ba5ab92f8d8eea99b1aeb46bc25ffd085848646f16138c92edb6b6",
"pubkey": "1e219624404cb46159e3ec93d4ae1305535765c46a48669795d4b17ac0cbee9e",
"created_at": 1775559721,
"kind": 1,
"tags": [
[
"proxy",
"https://infosec.exchange/@trailofbits/116363081880526734",
"web"
],
[
"proxy",
"https://infosec.exchange/users/trailofbits/statuses/116363081880526734",
"activitypub"
],
[
"L",
"pink.momostr"
],
[
"l",
"pink.momostr.activitypub:https://infosec.exchange/users/trailofbits/statuses/116363081880526734",
"pink.momostr"
],
[
"-"
]
],
"content": "Before its launch, we audited WhatsApp's Private Processing TEEs and found 8 high-severity issues (patched). The enclaves yielded to injected config files, unmeasured ACPI tables, spoofed firmware levels, and stale attestation reports.\n\nTEE security is only as good as the implementation details. Four lessons and the full report: https://blog.trailofbits.com/2026/04/07/what-we-learned-about-tee-security-from-auditing-whatsapps-private-inference/",
"sig": "68ea611f19381c0befa4bd4c08beb412edb80b0f6673228d36041df343b5af2eebb13b3738dd03403c1e3baa70378cf440ff81a8e55cff920a8c914f721f9203"
}