Neodyme built a proof-of-concept FIDO2 hardware authenticator that replaces the conventional elliptic-curve or RSA signatures used in WebAuthn/FIDO deployments with SPHINCS+, a hash-based post-quantum signature scheme. The prototype was implemented on a Nordic nRF52840 Cortex-M4 device using the OpenSK FIDO2 firmware and targets the WebAuthn/FIDO2 ecosystem defined by the W3C Web Authentication standard.
The researchers said they adapted SPHINCS+ for the FIDO2 use case by reducing the allowed-signatures-per-key parameter q, which helped signatures fit within CTAP2 frame-size limits and improved signing performance. In benchmarking, the design slightly outperformed Google’s Dilithium-hybrid FIDO2 hardware-key approach for MakeCredential and, in several configurations, GetAssertion, while avoiding hybrid cryptography; Neodyme stressed that the token remains a research prototype and is not production-ready.

Track how attackers are adapting to this technology.
1 event from the most recent confirmed update back to the earliest known activity.
Neodyme published a blog post describing a proof-of-concept FIDO2 hardware authenticator built on OpenSK and a Nordic nRF52840 that uses the SPHINCS+ post-quantum signature scheme. The write-up says the team tuned parameters for CTAP2 constraints and benchmarked the design against Google's Dilithium-hybrid approach, while noting it is not production-ready.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
Follow how adversaries are adapting to this technology, and where it touches your stack today.
2 references tracked. Mallory keeps watching after this page renders.
Map indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.