Who is behind the Tor relay attack?

happygeek 2 Tallied Votes 685 Views Share

Yesterday, Tor issued a security advisory which revealed that a group of relays had been discovered on July 4th which looked like they "were trying to deanonymize users."

The advisory states that the attack "involved modifying Tor protocol headers to do traffic confirmation attacks" with the relays having joined the network at the start of the year. This means they were potentially deanonymizing users between January 30th and July 4th when they were finally removed.

A Tor spokesperson says that they know the attack "looked for users who fetched hidden service descriptors, but the attackers likely were not able to see any application-level traffic" so no details of pages visited or whether hidden services searched for were actually visited at all for that matter. The advisory goes on to warn that it is likely that the attackers tried to learn "who published hidden service descriptors, which would allow the attackers to learn the location of that hidden service."

No evidence was found to suggest that any exit relays were being operated, so the probability of linking users to destinations on standard Tor circuits remains remote. For full technical details of the attack methodology, see the advisory which goes into this at some length.

The following steps have been taken to remediate the damage in the short term:

  • Attacking relays removed from the Tor network
  • A software update has gone out for relays in order to prevent such use of 'relay early' cells again
  • A new Tor version warns in the logs if a relay on your path injects any relay-early cells

Meanwhile, Amichai Shulman who is the CTO at security experts Imperva says "sadly the ideal of having a distributed, crowd based network for protecting free speech is largely abused by pirates (software and content) as well as evil-doers – from child pornography to drug trafficking and terrorism. This in turn makes the TOR network a target for all intelligence agencies as well as some domestic security organizations. I suspect the reported attack, targeted mostly at people who operate and access TOR hidden service, is of that origin."

Craig Young, a security researcher at Tripwire, takes a slightly different view saying "While the attacker(s) in this case are still technically anonymous, it would appear that there is most likely a connection between this incident and the recently withdrawn Black Hat presentation on deanonymizing TOR users. If this was in fact a university research project, it was conducted without appropriate regard to users of the TOR network. This attack involved manipulating TOR protocol messages to encode information about observed requests so that the information could be correlated with an identity by relays in other parts of the network. In doing so the attackers not only made it possible to themselves unmask some TOR hidden services and users but they have also created an unquantifiable risk as these messages could also be decoded by other parties either while the attack was in progress or in retrospect by analyzing stored packet captures."

Dani AI

Generated

A quick follow-up that fills gaps in the thread: later reporting and court filings made a strong circumstantial case that the 2014 “relay‑early” relays were tied to a university research group and that law enforcement used the results. The Tor Project later accused a university research institute of providing data to the FBI and said the FBI bought the research; independent reporting and the court filings that surfaced in 2015/2016 trace the same Jan–Jul 2014 window noted above. Tor Project post Motherboard report Wired coverage.

How that conclusion was reached (briefly): defense motions in at least one case referenced a “university‑based research institute” that provided IP addresses; the timing and methods matched a now‑withdrawn Black Hat submission by CMU/SEI researchers, and academic commentators flagged serious ethical problems with running active attacks against real users. See Ed Felten’s contemporaneous analysis for a clear timeline and ethics discussion. Ed Felten / Princeton CITP.

Practical, actionable guidance for hidden‑service operators (useful years later): modern Tor uses v3 onion services — create a new HiddenServiceDir and restart Tor to get a fresh address, and enable client authorization if appropriate. Example torrc fragment:

HiddenServiceDir /full/path/to/your/new/v3/directory/
HiddenServicePort 80 127.0.0.1:8080

Follow the Tor Project’s operator guidance when rotating addresses and keys, keep Tor updated, isolate the host, and preserve relevant logs if there’s legal concern. Tor support: Onion Services.

Ethics and attribution remain unresolved in public records: Tor and several reporters tied the work to CMU/SEI and raised questions about oversight; the FBI publicly disputed some payment claims. For readers wanting to go deeper, the Tor post, Motherboard reporting, Wired’s coverage, and Ed Felten’s writeup are the clearest primary sources. This update complements ’s original summary and ’s link by showing how the story evolved after July 2014.

happygeek 2,411 Most Valuable Poster Team Colleague Featured Poster

Jaime Blasco, director of AlienVault Labs, has added his thoughts:

“TOR provides anonymity, if you want to have privacy you still have to use something like a VPN in order to connect to the TOR network. You are still facing other problems like tracking and profiling or unauthorized access to your system using exploitation of the browser or any other software you are using over the TOR network. As an example the FBI used an exploit affecting Firefox to deanonymize TOR users accessing illegal content. On the other hand, governments are actively investing a huge amount of money and resources in order to compromise the TOR network. If you want to be secure you should assume TOR is compromised and use other methods to maintain your anonymity and privacy within TOR.”

Slavi 94 Master Poster Featured Poster
Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.