Digital Asset
Intelligence
Security Incident · Arbitrum Ecosystem

Arbitrum Contract Vulnerability

·Historical incident record

Incident Overview

According to official sources, a bug in Arbitrum's sequencer code previously caused a brief outage in the network's batch transaction submission feature, which prevented transactions from being confirmed on the main chain. The bug has since been fixed and the bulk transaction submission feature has been restored.

Sources & References

Original incident referencehttps://twitter.com/ArbitrumDevs/status/1666549893001887744 (opens in a new tab)

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

    Arbitrum

    Attack methodDNS Attack
    Reported lossNot disclosed
  2. Incident date
    Target

    EDE

    Attack methodContract Vulnerability
    Reported loss$ 580,000
  3. Incident date
    Attack methodPrice Manipulation
    Reported loss$ 1,700,000
  4. Incident date
    Target

    Franklin

    Attack methodAccount Compromise
    Reported lossNot disclosed
  5. Incident date
    Target

    USEA

    Attack methodRug Pull
    Reported loss$ 1,100,000