In early October 2026, Dread and Omega both moved to new .onion addresses after a flaw in GoBalance, a load-balancing tool used by onion services. The incident is no longer breaking news, but it remains one of the most important onion-service security stories of the year. It showed that an address takeover does not require breaking into a server, and that a single public descriptor can be enough to recover a long-term key.
What GoBalance is
GoBalance is a Go rewrite of Onionbalance, a tool that helps onion services stay reachable by spreading traffic across several backend servers. It is often used with EndGame, a toolkit designed to keep hidden services online during denial-of-service attacks. The original Onionbalance and Tor itself are not affected by the flaw. The problem is specific to the Go rewrite and to the way some deployments stored their keys.
The signing bug
A Tor private key is 64 bytes long. The first half is the secret scalar; the second half is a secret nonce prefix used to make each signature unique. GoBalance passed only the first 32 bytes to the signing code and dropped the rest. Without the nonce prefix, the value that should be secret becomes a fixed number that anyone can compute.
That is enough to recover the signing key from public material. A published descriptor contains the signed certificate, including the message and the blinded public key. With one certificate, an attacker can recompute the nonce, derive the challenge, and solve for the blinded private key. Multiplying by the inverse of the public blinding factor recovers the original key. The result is the ability to sign valid descriptors for the .onion address, not necessarily the original seed or every secret in the deployment.
Searchlight Cyber disclosed the issue on October 8, 2026. The company said the original Onionbalance and Tor were not affected, and that GoBalance's own setup tool writes keys in a safer format, so not every GoBalance deployment was exposed. Sites that stored their master key in Tor's native key format were at risk. Once a descriptor had been published, patching the software did not undo the exposure.
What an address takeover means
An .onion address is derived from a public key. Whoever holds the matching private key controls the address. An attacker who recovers the key can publish valid descriptors and redirect visitors to a copy of the site they control. That does not automatically give them access to the original servers, database, or stored user data. It does, however, allow impersonation, phishing, and interception of anyone who trusts the address.
Because the exposed key is the service's long-term master key, the risk does not expire when the attacker's copy goes offline. A recovered key can be used to sign new descriptors in the future unless the service rotates its address and treats the old key as burned.
The Dread timeline
Dread was the most visible victim. On October 5, one of its operators said the main onion private key had been uploaded into a GoBalance update by mistake. The first address was taken over. Two days later, a second address used for premium members was also taken over and pointed at a rival service. That second takeover was harder to explain as a simple slip and became the stronger signal that the GoBalance flaw had been used.
Dread's operators said the forum itself had not been hacked and that its servers and data were not compromised at the server level. They did warn that anyone who reached the forum through an attacker-controlled mirror may have been exposed, and advised users to change passwords. Dread moved to a new address and said the migration was permanent because of the key exposure.
Omega and other services
Omega confirmed the same problem on October 8, saying its previous address was taken offline because of the GoBalance bug and that a new address was now official. Dread's administrator said several other markets had their addresses taken over, including some that had already shut down, but did not name them or give a number. The exact scope is still unknown.
Response and patch status
As of the initial disclosure, there was no CVE in the US National Vulnerability Database and no official advisory from the Tor Project or GoBalance's maintainer. Dread said it planned to release a patched version and help affected services migrate. An independent researcher published a patch and a proof of concept that recovered a master key from a single descriptor; the demonstration used test keys and did not target a live service.
For operators, the practical lesson is that a patch alone is not enough after a key has been exposed. The address should be rotated, the old key should be treated as compromised, and users should be told to change credentials. Services that used GoBalance with Tor-format keys should assume the key may have been recoverable from any descriptor published during the exposure window.
Why it matters
The incident is a case study in supply-chain risk. The vulnerable code was a third-party dependency, not the market's own application. It also shows how AI-assisted code review is changing vulnerability discovery: the flaw was found by analysing the signing path, not by breaking Tor. And it reinforces a distinction that is easy to miss: an address takeover is not the same as a server compromise, but it can still be damaging because users trust addresses.
Timeline
- October 5, 2026: Dread's main onion key is exposed during a GoBalance update; the first address is taken over.
- October 7, 2026: Dread's second address is taken over and pointed at a rival service; Dread announces a permanent migration.
- October 8, 2026: Searchlight Cyber discloses the GoBalance flaw; Omega confirms its old address is offline and moves to a new one.
- October 9, 2026: No official CVE or vendor advisory; an independent patch and proof of concept are published.
What users should do
Change passwords on Dread and any other service that used the affected address, verify links through an independent source, and treat old bookmarks as stale. If a service has moved, use the new address published by the service itself, not a link from a search result or a third-party list.
What operators should do
Inventory GoBalance deployments, check whether master keys were stored in Tor's native format, rotate any exposed onion keys, and publish a clear migration notice. Treat the old address as compromised even if the software is patched. Review third-party signing code and monitor descriptors for unexpected changes.
The GoBalance incident is not fresh news, but it is still relevant. Address takeovers are quiet, they exploit trust rather than servers, and the recovery work can take weeks. Services that have not rotated their keys should assume the exposure is not over.