Loading story…
Multiple reports describe Chronoforge, a claimed timing side-channel attack against non-constant-time ECDSA secp256k1 implementations running on Nordic nRF52 and nRF53 microcontrollers that use ARM TrustZone. The research says an attacker operating from the Normal World can measure microsecond-scale timing differences during signing operations and infer private-key material held in the Secure World, exploiting shared resources such as caches, branch prediction, TLBs, and performance counters rather than any flaw in secp256k1 itself. The attack is presented as especially relevant to Bitcoin wallets, BLE wallets, IoT security tokens, and embedded HSM-like devices built on affected designs.
The writeups also describe a framework called VulnCipher that allegedly collects timing traces, performs correlation-based analysis, and reconstructs private keys, with one source claiming recovery of a Bitcoin wallet key from a Nordic nRF5340 target and publishing sensitive wallet details and attack metrics. Across the references, the recommended defenses are consistent: use constant-time cryptographic implementations, apply scalar and point blinding or masking, isolate caches and PMU access between TrustZone worlds, and harden firmware so Secure World secrets cannot be inferred through timing leakage.
See affected versions and whether adversaries are exploiting it.
6 events from the most recent confirmed update back to the earliest known activity.
The research publication recommends defenses including constant-time cryptography, masking or blinding, cache and PMU isolation, and hardened firmware practices to reduce TrustZone side-channel exposure. It also highlights shared microarchitectural resources such as caches, branch prediction, TLBs, and performance counters as leakage sources requiring isolation.
The Chronoforge research also introduces VulnCipher, a framework for collecting timing traces, performing correlation-based analysis, and reconstructing private keys from leaked timing information. The publication includes proof-of-concept methodology and practical demonstrations involving Nordic nRF5340, PSA Crypto, and TF-M environments.
By 2026-03-09, a research paper describing the so-called Chronoforge Attack was published, alleging that variable-time ECDSA secp256k1 operations on Nordic nRF52/nRF53 devices with ARM TrustZone can leak private-key material through microsecond-scale timing differences. The paper frames the issue as an implementation flaw, not a weakness in secp256k1 itself.
Content published on 2026-01-01 claims the VulnCipher framework reconstructed a Bitcoin wallet private key from timing leakage on a Nordic nRF5340 using ARM TrustZone, allegedly recovering about $188,775. The writeup presents this as a practical ChronoForge side-channel compromise rather than a malware or network intrusion.
A write-up published on 2025-10-04 described the ChronoForge timing side-channel attack against variable-time secp256k1 implementations on ARM TrustZone embedded devices and presented an alleged case study recovering a Bitcoin wallet private key from a Nordic nRF5340-based BLE wallet. The article said roughly 100,000 timing traces enabled reconstruction of most key bits, with the remainder brute-forced, and recommended constant-time cryptography and side-channel audits as mitigations.
A write-up published on 2025-09-19 described the so-called Context Phantom Attack, alleging a critical secp256k1 'phantom context leak' vulnerability that could enable recovery of lost Bitcoin wallet private keys via memory disclosure. Based on the title, this was presented as a memory-leakage issue distinct from the later ChronoForge timing side-channel claims.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
13 references tracked. Mallory keeps watching after this page renders.
polynonce.ru
Open sourceattacksafe.ru
Open sourceyoutube.com
Open sourcecryptodeeptech.ru
Open sourcecryptou.ru
Open sourcekeyhunters.ru
Open sourcecryptou.ru
Open sourcekeyhunters.ru
Open sourceMap 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.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
Security researchers have demonstrated new hardware-based techniques to extract sensitive data from devices previously considered secure, including smartwatches and confidential computing servers. In one case, analysts revived the 'Blinkenlights' technique, adapting it to modern TFT screens to extract firmware from a budget smartwatch by exploiting a dial parser vulnerability. This allowed arbitrary memory content to be displayed on the device's screen, which was then captured using a high-speed Raspberry Pi Pico setup. The smartwatch, which contained fake health sensors and used a JieLi AC6958C6 system-on-chip, was found to have weak authentication and a flawed firmware parser, enabling the out-of-bounds read attack. Separately, researchers from KU Leuven University presented a low-cost hardware attack called 'Battering RAM' at Black Hat Europe 2025, which targets secure CPU enclaves such as Intel SGX and AMD SEV. By using a $50 DDR4 interposer, the researchers manipulated memory address mapping at runtime, bypassing firmware mitigations and gaining unauthorized access to encrypted memory. This allowed them to extract platform provisioning keys, forge attestation reports, and implant persistent backdoors on protected virtual machines, raising concerns about the security of cloud infrastructures relying on these technologies.
Jun 29, 2026
Multiple reports and research references describe Bitcoin wallet compromise scenarios in which weak, reused, or low-entropy ECDSA nonces allow attackers to recover private keys from public signatures. Several sources tie the risk to the so-called **Phantom Curve** and **Dark Skippy** attack patterns, claiming that malicious firmware or flawed random-number generation in hardware and software wallets can leak enough signing material for key recovery after as few as two transactions. Related writeups also connect the issue to broader entropy failures, including alleged hardware-wallet weaknesses such as `CVE-2025-27840`, and to historical examples like the PlayStation 3 signing flaw, Android OpenSSL wallet compromises, and weak web-wallet RNG implementations. The references also promote tools such as **KeySilentLeak** and other blockchain-scanning projects that purportedly analyze Bitcoin signatures for nonce bias, reuse, or reduced entropy and then apply methods including Pollard’s Kangaroo, lattice techniques, and other discrete-logarithm attacks to reconstruct wallet secrets. While some claims are framed as demonstrations involving specific Bitcoin addresses and recovered funds, the underlying security concern matches established cryptographic research showing that biased or repeated nonces can expose keys at scale from passive blockchain analysis. Recommended mitigations across the sources include adopting **RFC 6979** deterministic nonce generation, auditing PRNG and entropy sources, enforcing secure boot and firmware verification on hardware wallets, and hardening devices against nonce exfiltration and other signing-side attacks.
Jun 29, 2026
Researchers disclosed **Chypothermia**, a cryogenic physical attack that disrupts on-chip mixed-signal circuitry—including clock, clock-generation, and voltage-sensing components—to halt device clocks while evading defenses intended to detect abnormal clock stoppage. Combined with the **Chypnosis** static side-channel technique, it can leave registers and SRAM retaining secrets after digital protection logic and zeroization state machines stop operating; tests reportedly prevented key zeroization in platforms including the OpenTitan root-of-trust alert handler. The attack requires physical access, controlled cooling or power manipulation, and specialized static readout methods such as laser logic-state imaging or impedance analysis. AMD advisory `AMD-SB-8018` identifies Artix-7 and Kintex-7 FPGA exposure to this class of clock-freezing attacks and recommends programmable-logic clock monitoring paired with asynchronous reset. Researchers also proposed an FPGA-compatible self-heating sensor to help detect cryogenic conditions; organizations should assess devices holding bitstream-encryption or root-of-trust keys for asynchronous brownout, clock-loss, and temperature-response controls.
Sep 11, 2026