Hijacking bitcoin routing attacks on cryptocurrencies

51% attack refers to an attack on a blockchain in which a group of miners controls more than 50% of the network's mining hash rate or.
Table of contents

Upload Log in.


  1. Hijacking Bitcoin: Routing Attacks on Cryptocurrencies : netsec?
  2. bitcointalk verge hack.
  3. Nombre de citations par an.
  4. Hijacking Bitcoin: Routing attacks on cryptocurrencies.

My presentations Profile Feedback Log out. Log in. Auth with social network: Registration Forgot your password? Download presentation. Cancel Download. Presentation is loading. Please wait. Copy to clipboard. Download ppt "Hijacking Bitcoin: Routing attacks on cryptocurrencies". Forum Informatyki Teoretycznej, Warsaw By Andy Brodie. Functions of Money.

Highlights

About project SlidePlayer Terms of Service. Feedback Privacy Policy Feedback. All rights reserved. To make this website work, we log user data and share it with processors. To use this website, you must agree to our Privacy Policy , including cookie policy. I agree. In our recent paper Hijacking Bitcoin: Routing Attacks on Cryptocurrencies to appear at the IEEE Symposium on Security and Privacy, we shed light on these aspects by studying the security of Bitcoin from an Internet routing perspective and quantify the potential disruptive effects of network attackers.

‪Maria Apostolaki‬ - ‪Google Scholar‬

Among others, we show that:. In this post, we take a closer look at these issues. We start by describing the two possible network attacks which we consider, namely partitioning and delay attacks, along with their potential impact on Bitcoin. We then discuss some short and long-term countermeasures that would increase Bitcoin's robustness against network attackers. More details on our work can be found on our website.

Delay attacks

With partitioning attacks, an attacker aims at splitting the Bitcoin network into at least two disjoint components such that no information e. To partition the network into two components, a network attacker intercepts all the traffic destined to all the Bitcoin nodes contained within one of the component and drops any connection to the other component.

To intercept traffic, a network attacker relies on vulnerabilities in the Border Gateway Protocol BGP , the only Internet routing protocol used today, which does not validate the origin of routing announcements.

These attacks, commonly referred to as BGP hijacks , involve getting a router to falsely announce that it has a better route to some IP prefix. By hijacking all the IP prefixes pertaining to the nodes in one component, the attacker can effectively intercept all the traffic exchanged between the two components. Once on path, the attacker can sever all these connections effectively disconnecting the two components.

An animation of the attacks can be found on our website.

Blockchain meets Internet Routing

The extreme centralization of Bitcoin from an Internet viewpoint makes partition attacks particularly effective as few IP prefixes need to be hijacked. While intercepting Bitcoin traffic using BGP hijacking is effective, any un-intercepted Bitcoin connection bridging the two components would quickly render the partition ineffective.

Due to factors such as multi-homing, some nodes cannot be prevented from exchanging information, forming some kind of persistent connections. The presence of such connections makes partitioning attacks more challenging for the attacker, but not impossible. In our paper , we elaborate on how an attacker can provably identify and mitigate these persistent rogue connections by reducing the size of the partition she is trying to achieve. By partitioning the network, the attacker forces the creation of two parallel blockchains. Moreover, discarded transactions will be irrecoverably canceled if there exist other transactions in the prevailing branch of the chain which spent the exact same Bitcoins conflicting transactions.

Want to add to the discussion?

Bitcoin nodes are designed to request blocks from only a single peer to avoid overtaxing the network with excessive block transmissions. The block is requested again from another peer only if the request is not answered after 20 minutes. This design decision, coupled with the fact that Bitcoin traffic is unencrypted, allows for a powerful attack in which anyone intercepting Bitcoin traffic can delay block propagation on the corresponding connections.

To do so, the attacker performs simple modification to the content of the Bitcoin messages she intercepts. As Bitcoin messages are not protected against tampering, neither the receiver nor the sender have any indication that the message has been modified, allowing the attacker to stay under the radar. The actual impact of such an attack depends on the victim and ranges from double spending for merchant nodes to wasted computation power for miners.

An animation of the attack can be found here. Illustration of how an AS-level adversary AS8 which naturally intercepts a part of the victim's traffic node C can delay the delivery of a block to it for 20 minutes. Like for partition attacks, the centralization of Bitcoin nodes in few networks and prefixes, combined with the centralization of mining power in few pools, make delay attacks practical.