SOCLYDE logo
Current languageEN
Cybersecurity newscybersecuritytor

Tor strengthens relay defenses against DDoS attacks

Tor 0.4.9.17 strengthens relay defenses during ongoing DDoS attacks. Operators should update while continuing to monitor availability and further releases.

Published on

By Soclyde

A small volunteer networking room with a cabinet and maintenance equipment

In summary

  • Tor released version 0.4.9.17 on November 13 to strengthen its defenses.
  • The project highlights an important IPv6-related fix in relay DoS protections.
  • Operators should update urgently; the release does not guarantee the attacks have ended.

Explore next

Soclyde resources

Article contents

On November 13, 2026, the Tor Project released Tor 0.4.9.17 in response to a DDoS attack overwhelming its relays. It asks operators to update promptly, highlighting a defense improvement related to IPv6.

Relays are the immediate target

The announcement describes a flood of client circuits affecting most relay operators. This is a network availability problem: hostile traffic consumes resources relays need to operate.

The project does not identify the attackers. It says further defenses are being evaluated and more releases may follow. Operators therefore need to keep following official communications after installing this update.

What version 0.4.9.17 changes

Tor highlights an important fix in how denial-of-service defenses handle IPv6. That provides a concrete task for operators: check the version actually running on every relay.

RedesZone places the release in the wider context of network saturation. Updated relay software and a working Internet connection remain separate requirements; a slow connection alone does not establish that your own device is compromised.

Improvement without an immediate recovery guarantee

SecurityWeek reports operator accounts of continuing trouble after upgrading, including loss of HSDir status, a role associated with the onion service directory. These accounts do not measure every relay's condition.

They do support checking availability after installation. The Tor Project announcement does not establish user deanonymization: an outage or an operator's hypothesis should not become a claim about every connection's confidentiality.

An operational check for operators

If you run a relay, install the recommended release and confirm that the restarted process is running 0.4.9.17. The Tor Project requires no further action after upgrading.

We recommend recording downtime and observed changes to track your relay's condition. If an activity depends on an onion service, arrange another way to contact the people involved during disruption.

Administrative access to relay hosts needs separate protection. Soclyde keeps those credentials in an encrypted vault on your devices, helping avoid access details scattered across notes or emails.

That organizes an operator's secrets; it does not filter hostile circuits or restore the Tor network. Software updates and relay monitoring remain operational tasks.

Key points

Update relays and follow subsequent announcements without promising a definitive end to the attack. Use the password generator to create a distinct administrative password.

Frequently asked questions

Who should act first?

Tor relay operators. The announcement asks them to upgrade to 0.4.9.17 as soon as possible and specifies no additional action after the upgrade.

Does the update end every disruption?

The project does not guarantee that and says it is evaluating further defenses. SecurityWeek also reports continuing difficulties described by relay operators.

Does this announcement prove deanonymization?

No. The Tor Project announcement addresses availability and denial-of-service defenses. It does not establish that users have been deanonymized.

References

Sources and references

Need advice?

Design your password strategy with Soclyde

Schedule a dedicated walkthrough with the team to see how local-first security adapts to your stack.

Talk with us

Keep reading