Digital Asset
Intelligence
Security Incident · Solana Ecosystem

Solana DDoS Attack

·Historical incident record

Incident Overview

The beta version of the mainnet of the public chain Solana has been unstable since 19:52 Beijing time last night, and it has been 12 hours since the Solana chain application has not been able to operate normally. According to information released by Solana Status, the Solana validator community chose to restart the network cooperatively, and the snapshot height is slot 96542804. Solana Status recommends that the verification node be updated to Mainnet-Beta 1.6.24 version. On September 21, Solana officially released a preliminary overview of the network outage on September 14. It is reported that on September 14, Solana’s network was offline for 17 hours. There was no financial loss, and the network resumed full functionality within 24 hours. The cause of network stagnation is denial of service attacks. At 12:00 UTC time, Grape Protocol launched IDO on Raydium, and transactions generated by robots congested the network. These transactions caused a memory overflow, causing many validating nodes to crash, forcing the network to slow down and eventually stop. When the verification node network cannot agree on the current state of the blockchain, the network will go offline, preventing the network from confirming new blocks.

Sources & References

This record presents information attributed to the linked sources. Incident dates describe the original event, not a new report. Reported loss figures reflect the source record and are not current market valuations.

More Security Incidents

View All →
  1. Incident date
    Target

    Solana

    Attack methodDDoS Attack
    Reported lossNot disclosed
  2. Incident date
    Target

    Solana

    Attack methodDowntime
    Reported lossNot disclosed
  3. Incident date
    Target

    Solana

    Attack methodUnknown
    Reported loss$ 8,000,000
  4. Incident date
    Attack methodFlash loan attack
    Reported loss35,281.71 KXUSD
  5. Incident date
    Attack methodContract Vulnerability
    Reported loss$ 3,200,000