All Posts Next

Tor DoS Defenses have been patched again in Tor 0.4.9.17 as a DDoS attack continues to strain relay operators, an ongoing disruption with lessons for regulated businesses.

SecurityWeek reported the story on the Tor 0.4.9.17 release, announced November 13, in an article by senior managing editor Eduard Kovacs. The piece draws on announcements from Tor developer David Goulet and on reports from relay operators in the Tor community forums. Business and IT leaders in regulated industries should pay attention even if they never run a Tor relay: the incident is a live case study in how a sustained, adaptive denial-of-service campaign plays out against volunteer infrastructure, and in how a project communicates about an attack it has not yet stopped.

Key Takeaways

  • Tor 0.4.9.17, announced on November 13, patches several security issues, including one fix related to how relays' built-in DoS protections deal with IPv6.
  • The Tor Project described the release as coming "in rapid response to the ongoing DDoS attack on the network, which has affected most relay operators," with relays overwhelmed by a massive flood of client circuits.
  • Tor 0.4.9.17 arrived less than three weeks after Tor 0.4.9.15, which introduced three DoS protections against what the project called a "thunderstorm" of directory requests.
  • Relay operator reports suggest the latest update has not ended the disruption. One operator reported that roughly ten minutes after upgrading, the attack on their relay took on a new form, with traffic plunging and the relay repeatedly becoming unresponsive.
  • The Tor Project has said more defenses are under consideration and that new versions should follow shortly, and it has urged anyone running a relay to update without delay.

What happened: the facts in detail

A rapid-response release on November 13

On November 13, the Tor Project released Tor 0.4.9.17, a new version of its core software that patches several security issues. The project singled out one fix related to how relays' built-in DoS protections deal with IPv6. The release was framed by the project itself as an emergency measure: developer David Goulet said in the announcement that the release "comes in rapid response to the ongoing DDoS attack on the network, which has affected most relay operators."

Goulet was direct about the difficulty of the problem. "This is not an easy problem to address, as relays across the network are being overwhelmed by a massive flood of client circuits," he said in the announcement. The Tor Project also stated that more defenses are under consideration and that new versions should follow shortly. Anyone running a relay has been urged to update without delay.

The earlier release: Tor 0.4.9.15 and the directory request "thunderstorm"

The new version came less than three weeks after Tor 0.4.9.15, which introduced three DoS protections against what the project described as a "thunderstorm" of directory requests. Writing to relay operators at the time, Goulet noted that a single relay could be hit with hundreds of circuits per second. He cautioned that relays would remain under heavy load for as long as the attack lasted.

That caution proved accurate. The attack did not stop with the earlier release, which is why the project shipped another fix so soon after.

Operator reports: the disruption continues after the update

Reports from relay operators suggest the latest update has not ended the disruption. In a forum post on November 14, one operator said two of their relays had lost HSDir status due to attacks before the update, and that another was being targeted when 0.4.9.17 was released and installed.

What happened next is the most instructive detail in the reporting. Roughly ten minutes after that relay was upgraded, the attack took on a new form, according to the operator. Its traffic plunged and it kept becoming unresponsive. "Relay unresponsiveness ultimately caused loss of HSDIR. Attack ceased immediately on loss of HSDIR," the operator wrote.

In the operator's view, 0.4.9.17 does not do enough to shield HSDir relays, and the attacker changes techniques while an attack is underway. The operator also warned that the attacker could be capable of deanonymizing and tracking onion services. The Tor Project has issued no such warning in its release announcements.

Tor DoS Defenses: how the protections work and why it matters technically

To read this story correctly, a business reader needs three pieces of context about how Tor operates and what the attack is targeting.

First, the Tor network is made up of volunteer-run relays. The project's own announcement describes relays across the network being overwhelmed by a massive flood of client circuits, and Goulet's message to operators described a single relay being hit with hundreds of circuits per second. A relay has finite capacity. When that capacity is consumed by attack traffic, the relay's ability to carry legitimate traffic suffers, and in the case documented by the November 14 forum post, the relay became unresponsive entirely.

Second, the software now carries layered defenses. Tor 0.4.9.15 introduced three DoS protections aimed at a "thunderstorm" of directory requests. Tor 0.4.9.17 followed less than three weeks later with several security fixes, including one related to how the relays' built-in DoS protections deal with IPv6. The project has not published, in the materials cited here, a detailed technical explanation of the IPv6 issue or of exactly how the fix changes relay behavior. What is established is that the built-in protections had a gap related to IPv6, and that closing it was considered urgent enough to warrant a rapid-response release.

Third, the attack is not static. The operator report from November 14 describes an attacker who changes techniques while an attack is underway: after the relay was upgraded, the attack took on a new form within roughly ten minutes. That is the defining characteristic of this incident. Defenders ship a fix, and the attacker's behavior shifts. This is a pattern any organization that operates internet-facing infrastructure will recognize, and it is why the Tor Project has said more defenses are under consideration rather than declaring the problem solved.

For regulated businesses, the technical lesson is about resilience of shared infrastructure. Tor is used by many organizations, including some in security-sensitive fields, for anonymity and for reaching onion services. When the relays that carry that traffic are degraded or lose their network roles, availability suffers for everyone depending on the network. The incident is also a reminder that DoS defenses are iterative: one release of protections rarely ends a determined campaign, and defenders should plan for adaptation on the other side.

What the evidence does and does not show

Precision about the limits of the reporting matters here, because several claims circulating around this story go beyond what the sources establish.

What is established

The following facts come directly from the SecurityWeek report and the announcements it cites. Tor 0.4.9.17 was announced on November 13 and patches several security issues, with the project singling out one fix related to how relays' built-in DoS protections deal with IPv6. The release was a rapid response to an ongoing DDoS attack that has affected most relay operators, with relays overwhelmed by a massive flood of client circuits. Tor 0.4.9.15, released less than three weeks earlier, introduced three DoS protections against a "thunderstorm" of directory requests, and Goulet noted at the time that a single relay could be hit with hundreds of circuits per second. A relay operator reported on November 14 that two relays had lost HSDir status due to attacks before the update, that a third was under attack when the update was installed, and that roughly ten minutes after the upgrade the attack took on a new form, with traffic plunging and the relay repeatedly becoming unresponsive until it lost HSDIR status, at which point the attack ceased immediately.

What is reported but not confirmed by the Tor Project

The operator's assessment that 0.4.9.17 does not do enough to shield HSDir relays is the operator's view, published in a community forum post. It is not a finding from the Tor Project. Likewise, the operator's warning that the attacker could be capable of deanonymizing and tracking onion services is the operator's own statement. The Tor Project has issued no such warning in its release announcements. Readers should treat the deanonymization concern as an unverified claim from one operator, not as an established capability of the attacker.

What remains unknown

Several important questions are open. The sources do not identify who is behind the attack or state a motive. The sources do not describe the precise technical mechanism of the IPv6-related gap or exactly how the 0.4.9.17 fix closes it. The sources do not say how many relays have been affected beyond the project's statement that the attack has affected most relay operators, and they do not quantify the overall impact on network performance. The sources also do not establish how long the attack will continue; Goulet cautioned that relays would remain under heavy load for as long as the attack lasted, and the project has said new versions should follow shortly, which signals that the defensive work is ongoing.

There is also an open question about attribution of effects. The operator observed that the attack ceased immediately when their relay lost HSDIR status, and that the attack changed form shortly after the relay was upgraded. Those observations are documented, but the sources do not explain why the attacker behaved this way, and no conclusion about the attacker's targeting logic can be drawn from the reporting alone.

For leaders weighing what this means for their own environments, the honest summary is this: a volunteer-run anonymity network is under a sustained, adaptive denial-of-service campaign; its developers are shipping fixes in rapid succession; the latest fix has not, per operator reports, ended the disruption; and the most alarming claim in circulation, about deanonymization of onion services, comes from a single operator rather than from the project itself. Prudent planning starts from that evidence, not from the stronger versions of the story. In Part Two of this analysis, we will look at what this pattern of sustained, adaptive attack means for organizations in regulated industries, including defense contractors and healthcare entities that depend on infrastructure they do not control, and what practical steps follow from the evidence.

Why This Matters for Regulated Organizations

At first glance, a denial-of-service campaign against the Tor network looks like someone else's problem. Tor is volunteer-run infrastructure, not something most regulated businesses operate. But the story carries three lessons that apply directly to organizations bound by contractual and regulatory security obligations, and each of them is actionable now.

First, the attacker is adapting faster than the defenders can ship fixes. The Tor Project released Tor 0.4.9.15 with three DoS protections against what it described as a "thunderstorm" of directory requests, then followed less than three weeks later with Tor 0.4.9.17 on November 13, patching additional security issues including one related to how relays' built-in DoS protections deal with IPv6. According to the project, more defenses are under consideration and new versions should follow shortly. That cadence, rapid successive releases against a shifting attack, is exactly the environment regulated organizations are required to plan for under incident response expectations such as those described in NIST SP 800-61 Rev. 3, which frames incident response as an ongoing part of cybersecurity risk management rather than a one-time exercise.

Second, the disruption affected "most relay operators," in the words of Tor developer David Goulet, and relays would remain under heavy load for as long as the attack lasted. Availability is a security property. Frameworks your organization answers to, whether NIST SP 800-171 for controlled unclassified information, the HIPAA Security Rule at 45 CFR Part 164, or PCI DSS across cardholder data environments, all treat the availability and integrity of systems as obligations, not conveniences. A sustained flood that degrades a service you depend on is an availability event even if no data is stolen.

Third, one relay operator reported in a public forum post on November 14 that the attack took on a new form roughly ten minutes after that relay was upgraded to 0.4.9.17, with traffic plunging and the relay repeatedly becoming unresponsive. The operator viewed 0.4.9.17 as insufficient to shield HSDir relays and warned that the attacker could be capable of deanonymizing and tracking onion services. The Tor Project has issued no such warning in its release announcements. When a vendor's public posture and an operator's observed experience diverge, a regulated organization should treat the more conservative reading as its planning assumption and verify independently.

What This Means for Regulated Industries

Defense Contractors

The most direct connection is operational: if your organization uses Tor for any purpose, anonymous browsing by staff, research into threat actor infrastructure, or any tooling that routes traffic through the network, you should assume degraded reliability and heightened risk while the attacks continue. The Tor Project has urged anyone running a relay to update without delay; if your environment includes a relay, that applies to you, and the update should be treated as an urgent change control item with documentation to match.

The deeper connection is contractual. DFARS 252.204-7012 requires reporting a cyber incident affecting covered defense information to DoD within 72 hours of discovery via dibnet.dod.mil, and requires preserving affected system images and monitoring data for at least 90 days afterward. A denial-of-service condition on infrastructure you rely on can qualify as an incident worth evaluating against those obligations, particularly if it coincides with other anomalous activity. The operator report in this story is a useful reminder that attackers who study a target's behavior and change techniques mid-campaign are not limited to any one sector. Our overview of DFARS compliance covers the reporting and safeguarding requirements in detail, and our guide to CUI versus FCI helps contractors determine which obligations attach to which data.

Healthcare

Healthcare organizations rarely operate Tor infrastructure, but many have staff or business associates who use it, and the HIPAA Security Rule requires a risk analysis under 45 CFR 164.308(a)(1)(ii)(A) that accounts for threats to the confidentiality, integrity, and availability of electronic protected health information. If anonymized browsing is part of your security research or compliance workflow, its degradation is a minor but real operational risk worth a line in your risk register. More broadly, the pattern here, an attacker overwhelming shared infrastructure with junk traffic to exhaust capacity, mirrors the availability threats healthcare entities face from commodity DDoS and from ransomware's pre-encryption staging. The IBM 2026 figure that the average healthcare breach costs $6.64M is a reminder that availability and confidentiality failures are priced together by regulators and insurers alike.

Business associates should take particular note: business associates accounted for about 66% of breached healthcare records in 2024, which means your vendor's visibility into attacks on shared infrastructure is part of your own risk picture.

Legal

Law firms use Tor more than most regulated businesses, whether for research, source contact, or client matters involving sensitive investigations. The operator's warning that the attacker could be capable of deanonymizing and tracking onion services, a warning the Tor Project itself has not issued in its release announcements, deserves attention from anyone advising clients on anonymity. The prudent posture is to treat Tor-based anonymity as degraded until the project states otherwise, to avoid routing anything privileged or client-identifying through the network during this period, and to document that decision. Our guide to cybersecurity compliance for law firms addresses the broader duty to protect client information against reasonably foreseeable threats.

Financial Services

Financial institutions face the availability dimension most acutely. Regulators in this sector expect firms to demonstrate operational resilience, meaning the ability to deliver critical services through disruption. The Tor story is a clean case study for your resilience program: a distributed infrastructure under sustained, adaptive attack, with defenders shipping successive mitigations and operators reporting mixed results. Ask whether your own third-party dependencies include shared or community-run infrastructure, and whether you would detect a slow degradation of that dependency the way this relay operator detected plunging traffic and repeated unresponsiveness. Monitoring that distinguishes "the service is down" from "the service is being degraded" is the difference between a fast response and a late one.

An Action Plan for This Month

Each of these steps can be completed within weeks, and most within days, by a security or IT leader acting on this story.

  1. Inventory any use of Tor in your environment. Check egress rules, proxy configurations, and installed software for Tor clients or relays. You cannot assess risk to a dependency you have not enumerated.
  2. If you operate a relay, update immediately. The Tor Project has urged anyone running a relay to update without delay, and Tor 0.4.9.17 was released on November 13 specifically in rapid response to the ongoing DDoS attack. Treat the update as a prioritized, documented change.
  3. Re-evaluate whether Tor is necessary for any current workflow. If anonymized access is not a hard requirement, suspend it until the project reports the attack contained. If it is a requirement, add compensating controls and monitoring.
  4. Review your incident response plan against a sustained availability attack. NIST SP 800-61 Rev. 3 frames incident response across the NIST Cybersecurity Framework 2.0 functions, including GOVERN and DETECT. Confirm your plan covers degradation events, not just breaches.
  5. Verify your monitoring would catch slow degradation. The relay operator in this story noticed plunging traffic and repeated unresponsiveness. Confirm you have equivalent visibility into the services your organization depends on, including third-party ones.
  6. Confirm your 72-hour reporting readiness if you are a defense contractor. DFARS 252.204-7012 reporting through dibnet.dod.mil requires a DoD-approved medium assurance certificate obtained in advance. If you do not hold one, obtain it now; you cannot meet a 72-hour clock by starting the certificate process after discovery.
  7. Check your evidence preservation posture. After a reported incident, DFARS 252.204-7012 requires preserving affected system images and monitoring data for at least 90 days. Confirm your logging retention and backup practices support that.
  8. Update your risk register and vendor assessments. Add shared-infrastructure availability risk as a named category, and ask critical vendors whether they depend on community-run networks or services.
  9. Brief leadership in plain English. A two-page executive summary covering what happened, what you depend on, and what you changed is sufficient. The point is a documented, informed decision, not a technical treatise.
  10. Schedule a control review against your governing framework. Whether your baseline is NIST SP 800-171, the HIPAA Security Rule, or PCI DSS, walk the incident response and availability controls with fresh eyes in light of this attack pattern.

How Petronella Technology Group, Inc. Helps

Petronella Technology Group, Inc. has served regulated businesses since 2002, and the issues this story raises map directly onto services we deliver every day.

For organizations that need continuous visibility into degradation and attack activity, our managed detection and response service combines 24/7 threat monitoring, AI-powered analytics, and human-led investigation, with full coverage operational within 30 days of contract signing. The service scales from 25-endpoint small businesses to 5,000-endpoint enterprises, and its reporting is designed to provide the evidence auditors need for HIPAA, CMMC, PCI DSS, SOC 2, and NIST 800-171 verification. Our AI-augmented hybrid SOC runs on the company's private AI cluster, which matters for defense industrial base and healthcare clients that cannot send CUI or PHI to a public-cloud SOC. Guardrails are explicit: the AI never closes a ticket on its own and never touches production systems without human authorization, and every action is logged for audit.

For incident response obligations, our broader cybersecurity services cover the 24/7 monitoring, threat detection, and incident response that frameworks expect, and our compliance practice maps your controls to the frameworks that govern you. Defense contractors can go deeper with our dedicated resources for defense contractors, including guidance on DFARS incident reporting and on what the recent suspension of the CMMC Phase II deadline means for planning, covered in our analysis of CMMC Phase II suspension.

Every practitioner on our compliance team holds the CMMC-RP designation, and Petronella Technology Group, Inc. is a Cyber AB Registered Provider Organization, RPO #1449. Craig Petronella, the firm's founder, holds CMMC-RP, CCNA, CWNE, North Carolina Licensed Digital Forensic Examiner license #604180, and an MIT AI certificate, with more than 30 years of experience.

Related reading

Sources

Frequently Asked Questions

Should my business stop using Tor because of these attacks?

For most routine business purposes, yes, at least temporarily. The Tor Project says the ongoing DDoS attack has affected most relay operators and that relays are being overwhelmed by a massive flood of client circuits, and one operator has reported the attack adapting after the latest fix. If your use of Tor is essential, treat its reliability and anonymity properties as degraded until the project reports otherwise, and document that assessment.

Is the Tor attack a risk to my data?

The confirmed impact in the sources is availability: relays overwhelmed by a flood of client circuits, with operators reporting lost HSDir status and unresponsive relays. One relay operator warned in a public forum post that the attacker could be capable of deanonymizing and tracking onion services, but the Tor Project has issued no such warning in its release announcements. Treat the operator's warning as a reason for caution, not as an established data compromise.

Does a DDoS attack on infrastructure I use count as a reportable incident?

It depends on your obligations and the facts. For defense contractors, DFARS 252.204-7012 requires reporting a cyber incident affecting covered defense information to DoD within 72 hours of discovery. Whether an availability event affecting third-party infrastructure meets that threshold depends on whether covered defense information systems were affected, which is a determination you should make against your incident response plan and document either way.

Why did Tor release two security updates so close together?

Because the attack kept evolving. Tor 0.4.9.15 introduced three DoS protections against a "thunderstorm" of directory requests, and Tor 0.4.9.17 followed less than three weeks later, on November 13, with additional fixes including one related to how relays' built-in DoS protections deal with IPv6. The project says more defenses are under consideration and new versions should follow shortly.

What should a defense contractor do first in response to this story?

Confirm two things this week: that you hold the DoD-approved medium assurance certificate needed to report through dibnet.dod.mil, and that your logging retention supports the 90-day preservation requirement that follows a reported incident. Both are prerequisites you must have in place before an incident, not after.

How does this relate to our compliance audits?

Auditors assess whether your incident response and availability controls are operational, not merely documented. NIST SP 800-171's incident response requirements, for example, call for an operational incident handling capability and for tracking, documenting, and reporting incidents. A current, adaptive attack like this one is a timely prompt to test whether your controls would actually detect and respond to a sustained degradation event.

If you want help turning any of this into a concrete plan, call Penny, our AI assistant, at 919-348-4912, or reach Petronella Technology Group, Inc. through our contact form. The first call is a free 30-minute scoping consultation, delivered remote-first across all 50 states.

Free online course from the Petronella Technology Group, Inc. Training Academy

Unhackable and Compliant

Free crash course: 5 practical steps to protect your data and meet HIPAA, CMMC, PCI-DSS, and FTC Safeguards compliance standards.

Price: Free

Start the free course Cybercrime and Identity Theft Defense Mastery ($997)

Get the 2026 Cybersecurity Survival Guide

Free, practical, and specific to regulated environments. We will email it to you.

No spam. Unsubscribe anytime.

Need help implementing these strategies? Our cybersecurity experts can assess your environment and build a tailored plan. Prefer to write? Send us a message.
Call Penny 919-348-4912

About the Author

Craig Petronella, CEO and Founder of Petronella Technology Group
CEO, Founder & AI Architect, Petronella Technology Group

Craig Petronella founded Petronella Technology Group in 2002 and has spent 30+ years professionally at the intersection of cybersecurity, AI, compliance, and digital forensics. He holds the CMMC Registered Practitioner credential issued by the Cyber AB and leads Petronella as a Cyber AB Registered Provider Organization (RPO #1449). Craig is an NC Licensed Digital Forensics Examiner (License #604180-DFE) and completed MIT Professional Education programs in AI, Blockchain, and Cybersecurity. He also holds CompTIA Security+, CCNA, and Hyperledger certifications.

He is an Amazon #1 Best-Selling Author of 15+ books on cybersecurity and compliance, host of the Encrypted Ambition podcast (95+ episodes on Apple Podcasts, Spotify, and Amazon), and a cybersecurity keynote speaker with 200+ engagements at conferences, law firms, and corporate boardrooms. Craig serves as Contributing Editor for Cybersecurity at NC Triangle Attorney at Law Magazine and is a guest lecturer at NCCU School of Law. He serves as a digital forensics expert witness for law firms on matters involving cybercrime, cryptocurrency fraud, SIM-swap attacks, and data breaches.

Under his leadership, Petronella Technology Group has served hundreds of regulated SMB clients across NC and the southeast since 2002, earned a BBB A+ rating every year since 2003, and been featured as a cybersecurity authority on CBS, ABC, NBC, FOX, and WRAL. The company leverages SOC 2 Type II certified platforms and specializes in AI implementation, managed cybersecurity, CMMC/HIPAA/SOC 2 compliance, and digital forensics for businesses across the United States.

CMMC-RP NC Licensed DFE MIT Certified CompTIA Security+ Expert Witness 15+ Books
Related Service
Protect Your Business with Our Cybersecurity Services

Our proprietary 39-layer ZeroHack cybersecurity stack defends your organization 24/7.

Explore Cybersecurity Services
All Posts Next
Questions about this topic? Talk to our team. Call Penny 919-348-4912 Message us