BNB Chain developers have identified Allbridge’s hacker
The Allbridge team offered the attacker a reward for returning the funds
03.04.2023 - 15:00
638
1 min
0
The BNB Chain team announced on Twitter that it identified the individual behind the recent exploit on Allbridge — which caused an estimated loss of $570,000.
"BNB Chain has pinpointed the Allbridge attacker through on-chain analysis," the BNB Chain team stated, adding: "We are actively assisting the Allbridge project in recovering the stolen funds." The team declined to comment on further details of the attacker.
As a cross-chain bridge, Allbridge enables the transfer of digital assets from one blockchain network to another via liquidity pools. On Sunday, an attacker drained funds after manipulating the prices in Allbridge's liquidity pools on BNB Chain using a flash loan, security firm PeckShield first noted.
Allbridge quickly suspended its bridge protocol and offered an undisclosed bounty to the attacker — giving them a chance to avoid legal repercussions if the assets were returned. The attacker's response to this proposition is currently unknown.
At the same time, the project is also focusing on tracking down the culprit — working with teams from BNB Chain and others. "With the help of our partners and community, we are tracking the hacker through social networks like Twitter," Allbridge stated.
The project also plans to compensate affected users by establishing a "recovery fund." Allbridge said it intends to resume operations once the issue is resolved. In the meantime, a separate web interface was created for liquidity providers to withdraw their assets from its liquidity pools.
This material is taken from the website https://www.theblock.co.
Useful material?
Incidents
Developers warned of potential risks to bridges across the ecosystem and asked exchanges for assistance.
Jun 22, 2026
Incidents
The defendant helped move funds stolen through investment scams and earned at least $4 million for his role in the operation.
Jun 10, 2026
Incidents
The company is linking the incident to a compromised private key on a service wallet, rather than a smart contract exploit
May 22, 2026
Incidents
Following the incident, the project temporarily halted trading operations and node activity.
May 15, 2026
Incidents
The user spent weeks unsuccessfully trying to guess the password until Claude helped find an old wallet backup file
May 14, 2026
Crypto regulations
Authorities are introducing mandatory registration for companies handling cross-border crypto transactions
May 8, 2026
Telegram
Twitter