Urgent.News

What's breaking now, across thousands of outlets.

Tech

Smart Contract Vulnerability Surface Analysis: Bitfinex

Smart Contract Vulnerability Surface Analysis: Bitfinex Target Protocol : Bitfinex (TVL: $18684.6M) Smart Contract Vulnerability Surface Analysis – Bitfinex Protocol: Bitfinex (TVL: $18.68 B on Ethereum & L2) Date: 15 September 2026 Prepared by: Senior DeFi Security Researcher – Confidential 1. Executive Summary Bitfinex operates a hybrid ecosystem that combines a centralised exchange (CEX) with…

Bitfinex runs an ecosystem that blends a centralized exchange with various on-chain services like lending, staking and tokenized assets. This system is built mainly on Ethereum's mainnet and the Optimism and Arbitrum Layer 2 chains. This exposes Bitfinex to a broad attack surface that safeguards around $18.7 billion worth of user funds and protocol assets. The research focused on the contracts released by Bitfinex and how they interact with each other.

Key issues were found in several areas. Access control and governance had four high-severity problems, including an unauthorized ownership transfer in the BitfinexDAOProxyAdmin contract, a lack of multi-signature checks in the LendingPool contract, and an open function to set a bridge operator in the BitfinexBridge. Upgradeability and proxy patterns had three high-severity issues, such as an uninitialized implementation slot in the StakingPool proxy, a public upgrade function in the LendingPool contract, and a storage collision between the proxy and its implementation in the BitfinexVault contract.

Reentrancy and call-stack abuse had two medium-severity issues, like a missing checks-effects-interactions in the LendingPool withdraw function and an external call in the StakingPool claimRewards function. Oracle manipulation had two medium-severity issues, involving a single-source price feed in the LendingPool and stale timestamp checks in the BitfinexBridge.

Cross-chain bridge logic had two high-severity problems, including a double-spend scenario in the BitfinexBridge and a potential asset-locking failure. Finally, there were two low-to-medium severity issues in the token contract and denial-of-service vectors.

In summary, Bitfinex's moderately complex protocol poses a considerable risk, with several critical design choices that could be exploited by a skilled adversary. Immediate action is needed to address the high-severity issues and bring the risk level down to a low-to-medium status.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

One Read Core, and the Code That Proves It

A generic core is easy to describe and hard to show. So here it is, with the parts I would not put in a talk. 👋 I'm Anton - a software engineer working mostly in PHP/Symfony and Go, carving a live…

  • Core is a single, generic type handling any data type through a type parameter
  • Spec struct defines identity, payload, and version column groups, fixed and unchanged
  • Append method ensures every change is a new version row, preserving historical facts

I expected hexagonal architecture to help my coding agent. It didn't.

I am a principal engineer, and I started this experiment trying to defend something I have believed for years: invest in a good structure now, and later changes should get easier.

  • Hexagonal architecture implementation was 38% slower than flat version.
  • Flat version reached acceptance faster despite architectural investment.
  • Experiment questioned architectural habits and benefits of clean code.

We scheduled a question for an hour when nobody could answer it

The run was fully unattended. That was the point. Everything upstream of the final step had been automated for weeks, and the last remaining human touch was an approval — a request sent out, a wait, a…

  • Automated question pipeline experienced unexpected timeout glitch
  • Log entry provided no differentiation between rejection types
  • Gate assumed human presence without monitoring availability

More from Tuesday 15 September →