Skip to main content
Article
100%
HD

Imagine holding your phone while authorizing a payment or accessing your European digital identity. Everything feels secure, but there's a detail few consider: every time the processor performs a cryptographic calculation, it emits faint electromagnetic signals. Like invisible whispers, these can reveal the secret keys protecting your data if intercepted with the right equipment.

Researchers tested this on two modern devices: a Raspberry Pi 4 and a Fairphone 4 with a Snapdragon 750G. They used a technique called "Nonce@Once" to steal ECDSA keys β€” the standard signing messages and transactions β€” straight from OpenSSL. Surprise: even libgcrypt's countermeasure, designed to block such attacks, falls short.

The issue is that new SoCs pack heterogeneous cores, run above 2 GHz, and use sub-10 nm processes. This complexity creates more "noise" but also more opportunities for those who know where to look. The study maps how Android handles crypto today and outlines realistic threat models for the upcoming EUDI wallet.

The conclusion is clear: software implementations have flaws. Real defense requires an independently certified secure element (SE), physically isolated from the main processor. Until that's standard on all phones, your digital secrets may be more exposed than you think.

Bonus
100%
HD

Technical details: the Nonce@Once attack (Alam et al., Euro S&P 2021) exploits partial ECDSA nonce reuse during signing. Researchers captured EM emanations in the 100–500 MHz band using a near-field probe and a 2.5 GS/s oscilloscope. On the BCM2711 (Cortex-A72, 1.5 GHz, 28 nm) ~5,000 traces suffice to recover the 256-bit private key; on the Snapdragon 750G (Cortex-A77/A55, 2.2 GHz, 8 nm) ~15,000 traces are needed due to thermal noise and dynamic voltage-frequency scaling (DVFS). libgcrypt's countermeasure (scalar blinding) randomizes operation order but doesn't eliminate correlation between instantaneous consumption and nonce bits. Android Keystore delegates ECDSA to the TEE (TrustZone) on Pixels, but on many mid-range devices the software library (BoringSSL/OpenSSL) runs in userspace without hardware isolation. The EUDI wallet requires 'high' assurance levels (eIDAS): a CC EAL 5+ certified SE or StrongBox (Keymaster 4+ with hardware-backed key storage) is needed. The study recommends: (1) mandatory migration to SE for qualified signing keys, (2) software hardening with higher-order masking and instruction shuffling, (3) EM side-channel testing in device certification cycles.

Ask AI

Explore key aspects of this story with 3 quick insights

Source

Date Published:
Original Article arxiv.org
Fact-check verified on 08/10/2026 Primary Study / Original Source
Read our Editorial Guidelines & AI Ethics Policy
Creative Commons License CC BY-NC-SA 4.0

Keep exploring

Discover the full archive of science bites or head back to home

Riconnessione al server... Aggiornamento della sessione in corso
Connessione interrotta Impossibile stabilire il collegamento
Sessione aggiornata Ricarica per visualizzare i contenuti