TokenVault Old Smart Contract Exploited Similarly To Bankroll

From Quadriga Initiative Cryptocurrency Hacks, Scams, and Frauds Repository
Jump to navigation Jump to search

Notice: This page is a freshly imported case study from an original repository. While the original content had a similar format, some sections may not have been fully completed. Please help fill in any empty sections or any missing information you can find. If you are new here, please read General Tutorial on Wikis or Anatomy of a Case Study for help getting started.

Notice: This page contains sources which are not attributed to any text. The unattributed sources follow the initial description. Please assist by visiting each source, reviewing the content, and placing that reference next to any text it can be used to support. Feel free to add any information that you come across which isn't present already. Sources which don't contain any relevant information can be removed. Broken links can be replaced with versions from the Internet Archive. See General Tutorial on Wikis, Anatomy of a Case Study, and/or Citing Your Sources Guide for additional information. Thanks for your help!

Binance Security Image

A 2021 smart contract named TokenVault, created by "donfunction.bnb" was deployed with a critical vulnerability. Similar to the Bankroll exploit, this flaw allowed attackers to drain funds from users who had granted the contract unlimited token permissions. The exploit resulted in a reported loss of $16.4k. The incident was reported by TenArmor and BlockThreat, with no signs of ongoing project activity, fund recovery, or pending investigations.

[1][2][3][4][5][6][7]

About TokenVault

The TokenVault smart contract was originally created by an entity called "donfunction.bnb" on June 29th, 2021.

Address: 0xe968d2e4adc89609773571301abec3399d163c3b

The Reality

Unfortunately, the smart contract contained a vulnerability.

What Happened

The TokenVault smart contract, created in June 2021 by "donfunction.bnb," was exploited due to a vulnerability similar to the Bankroll exploit, resulting in a $16.4k loss.

Key Event Timeline - TokenVault Old Smart Contract Exploited Similarly To Bankroll
Date Event Description
June 29th, 2021 6:03:42 PM MDT Smart Contract Created The vulnerable smart contract is originally created.
June 20th, 2025 5:19:36 AM MDT Exploit Transaction The exploit transaction is processed by the Binance Smart Chain.
June 20th, 2025 9:09:00 PM MDT TenArmor Tweet Posted TenArmor posts a tweet to notify that their system has detected a suspicious attack. They compare the attack to the Bankroll attack.

Technical Details

The attack was similar to the Bankroll exploit. In the Bankroll exploit, assets of any users who had approved the smart contract with unlimited permissions could be taken.

Exploit Transaction: 0xf34e59e4fe2c9b454d2b73a1a3f3aaf07d484a0c71ff8278b1c068cdedc4b64d

Victim Contract Address: 0xe968d2e4adc89609773571301abec3399d163c3b

Total Amount Lost

The loss amount was reported by TenArmor as $16.4k.

The total amount lost has been estimated at $16,000 USD.

Immediate Reactions

The attack appears to have only been detected and reported on by TenArmor and BlockThreat.

Ultimate Outcome

There is no indication that this project is still active.

Total Amount Recovered

There is no indication that any funds have been recovered.

There do not appear to have been any funds recovered in this case.

Ongoing Developments

It is unclear if any investigation will be undertaken or any recovery is available.

Individual Prevention Policies

No specific policies for individual prevention have yet been identified in this case.

For the full list of how to protect your funds as an individual, check our Prevention Policies for Individuals guide.

Platform Prevention Policies

Policies for platforms to take to prevent this situation have not yet been selected in this case.

For the full list of how to protect your funds as a financial service, check our Prevention Policies for Platforms guide.

Regulatory Prevention Policies

No specific regulatory policies have yet been identified in this case.

For the full list of regulatory policies that can prevent loss, check our Prevention Policies for Regulators guide.

References