Espresso Systems co-founder Jill Gunter falls victim to a $30k USDC theft due to a vulnerability in a Thirdweb bridge contract, raising security concerns in theEspresso Systems co-founder Jill Gunter falls victim to a $30k USDC theft due to a vulnerability in a Thirdweb bridge contract, raising security concerns in the

Espresso Co-Founder Reports $30k Loss via Thirdweb Contract Error

2025/12/13 18:59
Security Lapse in Crypto Infrastructure Leads to $30k USDC Theft
Key Points:
  • Espresso co-founder loses $30k due to Thirdweb contract vulnerability.
  • Wallet was drained through a legacy bridge contract.
  • Funds moved through Railgun for privacy protection.

Espresso co-founder Jill Gunter had $30k in USDC stolen via a vulnerability in a Thirdweb bridge contract. This incident stemmed from a legacy contract allowing unauthorized access, highlighting risks associated with outdated contract approvals.

In a recent event, Espresso Systems co-founder Jill Gunter announced the theft of $30k in USDC from her wallet due to a vulnerability in a Thirdweb bridge contract that was not sufficiently decommissioned.

Bridge Contract Vulnerability

The incident involved notable players like Thirdweb, a prominent Web3 infrastructure provider. Thirdweb confirmed the theft resulted from a legacy contract’s inadequacy, leading to the loss. All user wallets are now secure post-contract decommissioning.

Industry Concerns About Security

In response, the market’s focus has been on wallet security practices and the dangers of legacy systems. There have been calls for strengthened protocols to prevent similar occurrences in the future. The theft’s overall market impact remains minimal, attributed to its localized nature.

Past incidents highlight Thirdweb’s recurring security challenges. The service has faced criticism for prior disclosure practices. Security experts underscore the necessity of careful contract management to fend off unauthorized access across the ecosystem.

The $30k USDC loss highlights the enduring vulnerabilities in legacy contracts, spurred industry conversations on improving crypto infrastructure security protocols. Stakeholders continue to evaluate historical data to fortify systems against future breaches.

Disclaimer: The articles reposted on this site are sourced from public platforms and are provided for informational purposes only. They do not necessarily reflect the views of MEXC. All rights remain with the original authors. If you believe any content infringes on third-party rights, please contact service@support.mexc.com for removal. MEXC makes no guarantees regarding the accuracy, completeness, or timeliness of the content and is not responsible for any actions taken based on the information provided. The content does not constitute financial, legal, or other professional advice, nor should it be considered a recommendation or endorsement by MEXC.