Unknown Base Smart Contract Wrapped Ethereum Attack Theft
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!
An unknown and unverified smart contract was exploited due to a vulnerability. The incident resulted in a loss of approximately $21,000–$22,000, as reported by BlockSec Phalcon and TenArmor. Despite both parties acknowledging the incident, no detailed analysis of the exploit has been published. The transaction can be viewed on BaseScan, but no additional information about the vulnerability or the victim contract is currently available, and there is no indication that any funds have been recovered. Further details may emerge in the future.[1][2][3][4][5][6]
About Victim Smart Contract
The unknown and unverified victim smart contract was created on September 21st, 2024.
The Reality
Unfortunately, the smart contract had a vulnerability.
What Happened
An unknown smart contract was exploited due to an undisclosed vulnerability, resulting in an estimated $21K–$22K loss, with no analysis or fund recovery reported.
| Date | Event | Description |
|---|---|---|
| September 21st, 2024 1:48:25 PM MDT | Victim Smart Contract Created | The victim smart contract is first launched on the Base blockchain. |
| September 21st, 2025 10:29:23 PM MDT | Attack Transaction | The attack transaction was accepted in to the Base blockchain. |
| September 21st, 2025 11:59:00 PM MDT | Bot By BlockSec Phalcon | BlockSec Phalcon makes a post about the attack incident. |
| September 22nd, 2025 12:42:00 AM MDT | Post By TenArmor | TenArmor makes a post on Twitter/X about the incident. |
Technical Details
It does not appear that any analysis of the attack has been published.
Total Amount Lost
TenArmor reported that there was "an approximately loss of $22K", while BlockSec Phalcon reported $21k. Reviewing the transaction on BaseScan suggests an amount closer to $21k.
The total amount lost has been estimated at $21,000 USD.
Immediate Reactions
The transaction was picked up and reported on by both BlockSec Phalcon and TenArmor. However, neither prepared any analysis of the exploit.
Ultimate Outcome
There does not appear to be any further details known about the exploit or victim smart contract.
Total Amount Recovered
There is no evidence that any funds have been recovered.
There do not appear to have been any funds recovered in this case.
Ongoing Developments
There may be further details available in the future.
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
- ↑ TenArmor - "Our system has detected that #unverified contract 0x506a on #BASE was attacked, resulting in an approximately loss of $22K." - Twitter/X (Accessed Sep 22, 2025)
- ↑ Initial Attack Transaction - BaseScan (Accessed Sep 22, 2025)
- ↑ Attacker Address - BaseScan (Accessed Sep 22, 2025)
- ↑ BlockSec Phalcon - "ALRET! Our system has detected a suspicious transaction targeting an unknown contract on #Base, resulting in a loss of $21K." - Twitter/X (Accessed Sep 22, 2025)
- ↑ Victim Smart Contract - BaseScan (Accessed Sep 22, 2025)
- ↑ Victim Smart Contract Creation - BaseScan (Accessed Sep 22, 2025)