Incident: Title: Massive Cryptocurrency Theft via Exploit on Wormhole Blockchain Bridge

Published Date: 2022-02-03

Postmortem Analysis
Timeline 1. The software failure incident of hackers stealing over $324 million in cryptocurrency from Wormhole happened on an unspecified date before the article was published on February 3, 2022 [Article 124516].
System 1. Wormhole platform 2. DeFi service 3. Solana blockchain 4. Ethereum blockchain 5. Certus One [Article 124516]
Responsible Organization 1. Hackers [Article 124516]
Impacted Organization 1. Wormhole platform 2. Certus One 3. Users of the platform who had funds stolen [CNET Article 124516]
Software Causes 1. The software failure incident was caused by a hack where hackers exploited a vulnerability in the Wormhole platform, allowing them to steal over $324 million in cryptocurrency [Article 124516].
Non-software Causes 1. The hackers exploited a vulnerability in the platform that allowed them to steal cryptocurrency [Article 124516]. 2. The theft was facilitated by a security flaw in the system that enabled the minting and transfer of wrapped ETH [Article 124516]. 3. The incident led to the platform being taken offline for maintenance, indicating potential infrastructure issues [Article 124516].
Impacts 1. Loss of over $324 million in cryptocurrency due to the hack on Wormhole, making it one of the largest crypto thefts of all time [124516]. 2. The platform's network was taken offline for maintenance as a result of the incident [124516].
Preventions 1. Implementing stricter security measures such as multi-factor authentication, encryption, and regular security audits to prevent unauthorized access by hackers [124516]. 2. Conducting thorough code reviews and penetration testing to identify and fix vulnerabilities in the software that could be exploited by attackers [124516]. 3. Enhancing monitoring and alert systems to quickly detect any unusual or suspicious activities on the platform, enabling a rapid response to potential security breaches [124516].
Fixes 1. Implementing stronger security measures to prevent future hacks, such as multi-factor authentication, encryption, and regular security audits [124516].
References 1. Wormhole, the developers behind the popular blockchain bridge [Article 124516] 2. Blockchain analysis firm Elliptic [Article 124516] 3. Certus One, the developers of Wormhole [Article 124516] 4. Elliptic's Tom Robinson [Article 124516]

Software Taxonomy of Faults

Category Option Rationale
Recurring one_organization (a) The software failure incident having happened again at one_organization: - The incident involving the theft of cryptocurrency from Wormhole is a significant event that occurred within the organization itself [124516]. - This incident highlights a vulnerability in the platform that was exploited by hackers, leading to the theft of a large amount of cryptocurrency. - Wormhole's response included offering a bug bounty to the hacker and eventually restoring all the funds that were stolen. (b) The software failure incident having happened again at multiple_organization: - There is no information in the provided article indicating that a similar incident has happened at other organizations or with their products and services.
Phase (Design/Operation) design, operation (a) The software failure incident in Article 124516 can be attributed to the design phase. The incident occurred due to an exploit that allowed the attacker to mint wrapped ETH on the Solana blockchain, which was then transferred to the Ethereum blockchain. This exploit was a result of a vulnerability or flaw in the design of the system, allowing the theft of cryptocurrency worth $324 million [124516]. (b) Additionally, the incident also involved operation-related factors. The platform's network was taken offline for maintenance following the theft, indicating operational issues that arose as a response to the security breach. The operation of the system was impacted by the need to address the security incident and restore the stolen funds, highlighting operational challenges faced by the developers [124516].
Boundary (Internal/External) within_system, outside_system (a) within_system: The software failure incident in this case was primarily due to factors originating from within the system. The incident involved hackers exploiting a vulnerability within the Wormhole platform, allowing them to steal a significant amount of cryptocurrency. The exploit enabled the attackers to mint wrapped ETH on the Solana blockchain and transfer a portion of it to the Ethereum blockchain [124516]. (b) outside_system: Additionally, the incident involved external factors as the hackers were able to breach the system's security measures from outside. The hackers were able to successfully execute the theft, indicating a breach in the system's defenses against external threats [124516].
Nature (Human/Non-human) non-human_actions, human_actions (a) The software failure incident in Article 124516 was primarily due to non-human actions. Specifically, hackers exploited a vulnerability in the Wormhole platform, allowing them to steal a significant amount of cryptocurrency. This exploit enabled the attackers to mint wrapped ETH on the Solana blockchain and transfer a portion of it to the Ethereum blockchain. The incident led to the theft of $324 million in cryptocurrency and the platform being taken offline for maintenance. Certus One, the developers of Wormhole, even offered a bug bounty to the hacker for the exploit details and return of the stolen funds. Ultimately, all funds were restored, and the services were brought back online [124516]. (b) Human actions were also involved in the response to the software failure incident. Certus One, the developers of Wormhole, offered a $10 million bug bounty to the hacker in exchange for the exploit details and the return of the stolen cryptocurrency. This action was taken in an attempt to mitigate the impact of the hack and recover the funds. Additionally, the developers promised to share a full incident report following the incident, indicating a human response to the software failure [124516].
Dimension (Hardware/Software) software (a) The software failure incident in this case was not attributed to hardware issues. The incident involved hackers stealing cryptocurrency from the Wormhole platform, indicating a breach in the software security rather than a hardware failure [124516]. (b) The software failure incident was primarily due to a security breach caused by hackers exploiting a vulnerability in the software of the Wormhole platform. The hackers were able to steal a significant amount of cryptocurrency, leading to the platform being taken offline for maintenance. This incident highlights a software failure related to security issues rather than inherent software bugs or faults [124516].
Objective (Malicious/Non-malicious) malicious (a) The software failure incident in Article 124516 was malicious. The incident involved hackers stealing over $324 million in cryptocurrency from Wormhole, a blockchain bridge, through an exploit that allowed them to mint wrapped ETH on the Solana blockchain and transfer it to the Ethereum blockchain. This theft was described as one of the largest crypto thefts of all time and the second-largest theft from a DeFi service, indicating malicious intent to harm the system and exploit vulnerabilities for financial gain [124516].
Intent (Poor/Accidental Decisions) poor_decisions (a) The intent of the software failure incident related to poor_decisions: - The incident involved hackers stealing over $324 million in cryptocurrency from Wormhole, a blockchain bridge platform [Article 124516]. - The exploit allowed the attacker to mint 120,000 wrapped ETH on the Solana blockchain, with a significant portion transferred to the Ethereum blockchain [Article 124516]. - Certus One, the developers of Wormhole, offered the hacker a $10 million "bug bounty" for the exploit details and return of the cryptocurrency [Article 124516]. (b) The intent of the software failure incident related to accidental_decisions: - There is no specific mention in the articles indicating that the software failure incident was due to accidental decisions or unintended mistakes.
Capability (Incompetence/Accidental) accidental (a) The software failure incident related to development incompetence is not explicitly mentioned in the provided article. Therefore, it is unknown whether the incident was caused by factors introduced due to lack of professional competence by humans or the development organization. (b) The software failure incident related to accidental factors is evident in the article. The incident involved hackers stealing over $324 million in cryptocurrency from Wormhole, a popular blockchain bridge. This theft was described as an exploit that allowed the attacker to mint wrapped ETH on the Solana blockchain and transfer a significant amount to the Ethereum blockchain [124516].
Duration temporary (a) The software failure incident in this case was temporary. The incident involved hackers stealing a significant amount of cryptocurrency from Wormhole, leading to the platform being taken offline for maintenance [124516]. However, the platform later confirmed that all funds had been restored and its services were back up, indicating that the failure was not permanent.
Behaviour value, other (a) crash: The software failure incident in the article did not involve a crash where the system lost state and did not perform any of its intended functions. [124516] (b) omission: The software failure incident did not involve omission where the system omitted to perform its intended functions at an instance(s). [124516] (c) timing: The software failure incident did not involve timing issues where the system performed its intended functions correctly but too late or too early. [124516] (d) value: The software failure incident involved a value issue where the system performed its intended functions incorrectly. Specifically, hackers stole more than $324 million in cryptocurrency from Wormhole due to an exploit that allowed the attacker to mint wrapped ETH on the Solana blockchain and transfer a significant amount to the Ethereum blockchain. [124516] (e) byzantine: The software failure incident did not exhibit byzantine behavior where the system behaved erroneously with inconsistent responses and interactions. [124516] (f) other: The software failure incident involved a security breach where hackers exploited a vulnerability in the system to steal a large amount of cryptocurrency. The incident led to the platform being taken offline for maintenance and the developers offering a bug bounty for exploit details and the return of the stolen funds. [124516]

IoT System Layer

Layer Option Rationale
Perception None None
Communication None None
Application None None

Other Details

Category Option Rationale
Consequence property (d) property: People's material goods, money, or data was impacted due to the software failure The software failure incident involving hackers stealing over $324 million in cryptocurrency from Wormhole resulted in a significant impact on people's property. The thieves made off with 120,000 wETH, worth nearly $324 million, from the platform. Additionally, the exploit allowed the attacker to mint 120,000 wrapped ETH on the Solana blockchain, with a portion of it being transferred to the Ethereum blockchain. Certus One, the developers of Wormhole, even offered the hacker a $10 million "bug bounty" for the exploit details and return of the cryptocurrency, indicating the substantial financial impact of the incident on the platform and its users [124516].
Domain finance (a) The failed system was related to the finance industry as it involved the theft of cryptocurrency worth over $324 million from Wormhole, a blockchain bridge platform used for transferring cryptocurrency between different decentralized finance blockchain networks [Article 124516].

Sources

Back to List