The $100 million hit
The Coldcard exploit alone accounted for more than 40% of July's losses. The remaining $147 million came from other incidents. The exploit's mechanics haven't been publicly detailed, but the scale of the damage is clear.
July's place in 2026
July's $247 million total makes it the second-highest month for crypto thefts this year. Only one other month in 2026 has seen more stolen. That's a sobering reminder that thefts remain a persistent problem for the industry.
That's short. We can add a bit more. But we must not invent. We can say "The figures underscore the ongoing security challenges facing the crypto market." That's a general statement. But we need to avoid AI tells like "underscores". So we can say "The numbers are a blunt reminder." But that's also a bit cliché. Let's write more naturally. Maybe add a paragraph about the fact that July was the second-worst, and that the worst month is unknown. We can say "What the worst month was isn't specified in the data, but July's tally is a close second." That's a bit awkward. I'll rewrite. Lead: The Coldcard exploit caused more than $100 million in losses last month, a single incident that helped push July's crypto thefts to $247 million — the second-worst monthly total of 2026. Section 1: The exploit's weight The Coldcard exploit accounts for a large share of July's total. At over $100 million, it's more than 40% of the month's losses. The rest, roughly $147 million, came from other thefts. The exploit's details haven't been disclosed, but the financial impact is undeniable. Section 2: A rough month July's $247 million is the second-highest monthly theft total in 2026. Only one other month this year saw more stolen. That's a stark contrast to any hopes of a quiet summer. That's better. But "quiet summer" is a bit editorial but fine. We can end with a sentence: "The industry will be watching to see if August can avoid a similar fate." But that's speculative. We can end with "For now, the numbers stand as a reminder that crypto thefts remain a serious problem." That's a summary. I'll write a proper ending: "The full extent of the Coldcard exploit's fallout is still being assessed, but the July figures make one thing clear: the industry's security problems are far from over." That's a bit dramatic but okay. I'll go with that. Now we need to output JSON. The content should be HTML inside article tag. Word count: let's count. Lead: 30 words. Section 1: about 60. Section 2: about 40. Total ~130. That's too short. We need 450-700. So we need to expand. But we only have these facts. We can elaborate on the implications without inventing specifics. We can talk about the fact that July was second-worst, and that the worst month is unknown, but we can say "The worst month of 2026 so far remains unnamed in the available data, but July's tally is a close second." That's fine. We can also discuss that the $247 million is a lot, and that the exploit is a single point of failure. But we must avoid speculation. We can add a section about how the industry is reacting, but we don't have that. So we can't. We can add a section about the importance of security, but that's generic. Maybe we can write a longer article by describing the data more. For example: "The July total is a significant jump from typical months, though specific comparisons aren't available." But we don't know typical. I think we need to accept a shorter article. The rules say 450-700, but if we can't fill, we can go shorter? The instruction says "Total length 450-700 words." So we need to hit that. But we only have a few facts. We can expand by writing about the context of thefts in general, but we must not invent. We can say "Crypto thefts have been a persistent issue throughout 2026, with July marking one of the worst months yet." That's based on the fact that July is second-worst. We can say "The fact that July is second-worst means there is at least one other month with higher losses, but the data doesn't specify which." That's a bit meta. We can write a section about the Coldcard exploit itself: we know it's called Coldcard, but we don't know if it's a hardware wallet. We can say "The Coldcard exploit refers to an incident involving a product or service named Coldcard, though the specifics of the vulnerability remain unclear." That's safe. We can also talk about the broader implications for users: "For users, the incident is a reminder that even seemingly secure products can be compromised." That's a general statement but not an AI tell. Let's write a longer article with three sections: Lead (2-3 sentences): The Coldcard exploit caused more than $100 million in losses in July, helping push the month's crypto thefts to $247 million — the second-worst monthly total of 2026. The incident is a stark reminder of the financial toll that a single vulnerability can take. Section 1: The $100 million hole The Coldcard exploit alone accounted for more than 40% of July's losses. That's a substantial share, leaving about $147 million in other thefts. The exploit's specifics haven't been made public, but the scale of the damage is clear. For context, a single incident of this size would be notable in any month, but in July it was the dominant driver. Section 2: July's grim tally July's $247 million makes it the second-worst month for crypto thefts in 2026. Only one other month this year has seen more stolen, though that month isn't identified in the available data. The figure underscores the persistent threat of cybercrime in the crypto space. It also suggests that the industry's security measures are struggling to keep pace with attackers. Section 3: What the numbers mean The July data paints a worrying picture. Theft losses are running high, and a single exploit can wipe out a significant chunk of a month's total. For users, the Coldcard incident is a reminder that even products designed for security can fail. The industry will need to focus on preventing similar breaches if it wants to reduce these numbers. That's about 250 words. We need more. We can add a section about the year-to-date, but we don't have that. We can say
