HMS HMagician Smart Contract Burn Mechanism Exploited
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!
A recently deployed HMS (short for HMagician) smart contract contained a vulnerability in its burn mechanism. This flaw was exploited, leading to an estimated loss of approximately $94.6K, according to a report by TenArmor. The project does not appear to have a public presence, and there is no indication that any of the stolen funds have been recovered. TenArmor has published a detailed overview of the exploit, and while no official recovery efforts have been confirmed, an investigation may be underway to trace or return the funds.[1][2][3][4]
About HMS
HMS appears to be short for HMagician. The HMS smart contract was created on August 12th, 2025.
The Reality
Unfortunately, the burn logic of the HMS smart contract burn mechanism was vulnerable.
What Happened
The recently deployed HMS (HMagician) smart contract was exploited due to a vulnerability in its burn mechanism, resulting in a loss of approximately $94.6K
Date | Event | Description |
---|---|---|
August 12th, 2025 6:00:25 AM MDT | Smart Contract Created | The HMS/HMagician smart contract is first launched on the Binance Smart Chain. |
August 24th, 2025 8:43:45 PM MDT | Attack Transaction | The reported attack transaction is accepted and incorporated into the BSC blockchain. |
August 24th, 2025 9:38:00 PM MDT | TenArmor Posts Tweet | TenArmor posts a tweet about the suspicious attack. The losses are reported as approximately $94.6k. |
Technical Details
The issue was reportedly related to the burn mechanism of the smart contract being exploited.
Total Amount Lost
TenArmor reports "an approximately loss of $94.6K".
The total amount lost has been estimated at $95,000 USD.
Immediate Reactions
There is no suggestion that the project has reacted to the compromise publicly.
Ultimate Outcome
TenArmor published a report with an overview of the exploit.
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
There could be an investigation to trace the funds, or return to users.
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
- ↑ Ten Armor - "Our system has detected a suspicious attack involving #HMS on #BSC, resulting in an approximately loss of $94.6K. It appears that the #HMS token's burn mechanism was exploited." - Twitter/X (Accessed Aug 25, 2025)
- ↑ Attack Transaction - BSCScan (Accessed Aug 25, 2025)
- ↑ HMS Smart Contract - BSCScan (Accessed Aug 25, 2025)
- ↑ HMS Smart Contract Creation - BSCScan (Accessed Aug 25, 2025)