What exactly happened?
The Bitcoin Core team, which develops the reference software used by most nodes in the Bitcoin network, has published details on three security bugs. According to the developers, all of them are already fixed.
Bitcoin Core is the most widely used implementation of the software that runs the network's nodes. A node is a computer that keeps a copy of the blockchain and verifies transactions. Because most of the network runs this software, bugs in it have a potentially network-wide impact.
According to Decrypt, there were two types of problems: node overload (technically denial-of-service, an attack that floods a system until it stops working normally) and privacy issues. These were not bugs that would let an attacker steal coins or create them "out of nothing." That is an important distinction: based on the available information, Bitcoin's economic rules remained untouched.
Why is there talk about mining being halted?
The most serious of the three bugs was classified as high-severity by both Decrypt and CoinDesk. It could have caused a miner to lose the ability to assemble new blocks until someone restarted the software.
It is worth being precise about what this does and does not mean:
- This was not a permanent "shutdown" of Bitcoin mining as such.
- It was a state in which a specific affected miner could get stuck and stop producing blocks until a restart.
Both Czech and Slovak outlets (Kryptonovinky.cz and Kryptonovinky.sk) describe this bug as a situation that "could have halted mining." So the wording in the headlines describes the bug's potential, not that an outage actually occurred.
What was that Tor bug?
CoinDesk pointed to a separate bug that, according to the outlet, the developers fixed back in October 2025 and kept quiet about publicly until Tuesday's disclosure. This bug affected thousands of nodes connected via the Tor network (a tool for anonymous communication) and led to those nodes being able to "trust" practically any stranger.
This falls into the category of privacy problems, not theft of funds. The detailed technical scope of the impact (how many nodes were actually exposed and for how long) does not clearly follow from the available sources.
Were the bugs ever exploited?
According to the Bitcoin Core developers, there is so far no evidence that any of these bugs was exploited in practice. Kryptonovinky.cz, Kryptonovinky.sk, and both foreign sources all state this consistently.
That does not mean definitive certainty that no attempt ever occurred. It means the developers have no proof of exploitation. In security, the difference between "was not exploited" and "we have no proof of exploitation" is fundamental.
Timeline according to the sources
| Event | Source | Note |
|---|---|---|
| Fix of the Tor bug | CoinDesk | states October 2025 |
| Public disclosure of details on three bugs | CoinDesk, Decrypt | described as "Tuesday" |
| Summary for Czech and Slovak readers | Kryptonovinky.cz, Kryptonovinky.sk | draws on information from Decrypt |
The exact disclosure date (the specific day) and the complete technical identifiers of the individual bugs do not clearly follow from the summaries provided, which is why we do not present them here as verified.
Why watch this from a local perspective too?
For the Czech and Slovak scene, what is especially interesting is how quickly and in what way this information carried over into domestic media. Both Kryptonovinky.cz and Kryptonovinky.sk published their summaries essentially in parallel, and in both cases they drew on Decrypt. This is a common pattern: more serious security topics reach Czech readers through foreign primary sources with a certain delay and simplification.
What to watch with this type of news:
- Whether node operators and miners actually updated to the fixed version (the fix itself does not help until people deploy it).
- Whether an independent technical analysis of the scope of the Tor bug later appears.
- Whether the developers change their position on the absence of evidence of exploitation.
What follows from this
This is an example of how so-called responsible disclosure works: the bug is first fixed quietly, and the details are published only after some time so that it cannot be exploited. For readers, the key point is that we are talking about an operational and privacy-related weakness, not an attack on the money in the network. That in itself is not advice to take any action, just a description of what happened and what we do not yet know.