Digital Asset
Intelligence
Security Incident · Polygon Ecosystem

Polygon zkEVM Logic Vulnerability

·Historical incident record

Incident Overview

Blockchain security researcher iczc tweeted that a vulnerability was found in Polygon zkEVM and received a bug bounty from Immunefi L2. The vulnerability prevents asset migration from L1 to L2 by preventing assets bridged from L1 to Polygon zkEVM (L2) from being properly claimed in L2. iczc found in the code logic of processing claim tx pre-execution results that malicious attackers can bypass the "isReverted" pre-execution check on claim transactions by setting the gas fee to non-zero, allowing them to send a large number of Low-cost claims DoS attacks on sequencers and validators, increasing computational overhead. Also, transactions are not immediately removed from the pool after execution. The status is updated from Pending to Selected and continues to exist in the PostgreSQL database. Currently, there is only one trusted sequencer capable of fetching transactions from the transaction pool and executing them. Therefore, another vulnerability is to maliciously mark any deposit amount by sending a failed transaction. This will cause claim transactions that correctly use credits to be rejected because the credits are already used. This makes the L2 network unusable for new users. The Polygon zkEVM team fixed this vulnerability by removing the specific gas logic for claiming transactions, with no funds at risk.

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

    0VIX

    Attack methodOracle Attack
    Reported loss$ 2,000,000
  2. Incident date
    Target

    Galxe

    Attack methodDNS Hijacking Attack
    Reported loss$ 270,000
  3. Incident date
    Attack methodReentrancy Attack
    Reported loss$ 650,000
  4. Incident date
    Target

    Aleo

    Attack methodInflation Vulnerability
    Reported lossNot disclosed
  5. Incident date
    Attack methodContract Vulnerability
    Reported loss$ 7,500,000