Topic starter
18/08/2026 2:14 pm
TL;DR: July 2026 crypto losses exceeded $240 million across 29 incidents, with private key, entropy, and hot-wallet compromise accounting for about $149.3 million and a firmware flaw in Coldcard hardware wallets contributing roughly $115 million, according to Quantstamp. The month reinforces that key custody and randomness quality are now operational risk controls, not implementation details.
Editorial analysis by NHI Mgmt Group, based on content published by Quantstamp: “July Security Beat: Keys Over Code (Again?)”.
Key questions
Q: What breaks when key generation falls back to predictable inputs?
A: The trust boundary breaks immediately because the resulting keys are no longer exclusive or unguessable.
Q: Why do compromised signing keys create outsized crypto losses?
A: Because the signer is the authority boundary.
Q: What are the signs that signing workflows are too trusted?
A: Look for workflows where one credential can approve multiple high-value actions, where bridge or oracle keys lack explicit ownership, or where revocation would be difficult to execute quickly.
Practitioner guidance
- Audit key generation entropy paths Verify that hardware wallets, signers, and key management services never silently fall back to predictable software inputs when hardware randomness is unavailable.
- Treat bridge and oracle signers as privileged identities Inventory every signing key that can authorize withdrawals, governance actions, or oracle updates, then assign explicit owners, rotation rules, and revocation procedures.
- Separate signing authority from routine operations Require policy checks, multi-party approval, or dedicated controls for any workflow that can move funds or change state, especially where hot signers are used.
Bottom line: July’s biggest losses were driven less by clever code exploits than by failures in key custody, entropy, and trusted signing paths.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
18/08/2026 3:06 pm
Key custody is now an operational risk control, not a backend detail. When a signing key or wallet seed can be recovered, copied, or reused, the security boundary collapses immediately. That is why key custody belongs alongside access governance, not only cryptography. Practitioners should treat signer stewardship as part of identity and privilege management, not as a narrow engineering task.
A question worth separating out:
Q: What should security teams do when a wallet library may have exposed seed material or private keys?
A: Immediately assume the affected secrets are no longer trustworthy. Replace the compromised package, invalidate any keys or seeds that passed through it, and migrate funds or privileges to new wallets created from clean material. Then search telemetry for the malicious domain and confirm whether any systems transmitted key data externally.
👉 Read our full editorial: Keys, randomness, and compromise drove July’s biggest crypto losses