https://quadrigainitiative.com/cryptocurrencyhackscamfraudwiki/index.php?action=history&feed=atom&title=HMS_HMagician_Smart_Contract_Burn_Mechanism_ExploitedHMS HMagician Smart Contract Burn Mechanism Exploited - Revision history2026-05-30T09:59:20ZRevision history for this page on the wikiMediaWiki 1.39.1https://quadrigainitiative.com/cryptocurrencyhackscamfraudwiki/index.php?title=HMS_HMagician_Smart_Contract_Burn_Mechanism_Exploited&diff=6878&oldid=prevAzoundria: Created page with "{{Imported Case Study With About|source=https://www.quadrigainitiative.com/casestudy/hmshmagiciansmartcontractburnmechanismexploited.php}} {{Unattributed Sources}} Binance Security ImageA 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 t..."2025-08-27T21:31:12Z<p>Created page with "{{Imported Case Study With About|source=https://www.quadrigainitiative.com/casestudy/hmshmagiciansmartcontractburnmechanismexploited.php}} {{Unattributed Sources}} <a href="/cryptocurrencyhackscamfraudwiki/index.php?title=File:Binancesecurity.jpg" title="File:Binancesecurity.jpg">thumb|Binance Security Image</a>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 t..."</p>
<p><b>New page</b></p><div>{{Imported Case Study With About|source=https://www.quadrigainitiative.com/casestudy/hmshmagiciansmartcontractburnmechanismexploited.php}}<br />
{{Unattributed Sources}}<br />
<br />
[[File:Binancesecurity.jpg|thumb|Binance Security Image]]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.<ref name="tenarmortweet-21059" /><ref name="bscscantransaction-21060" /><ref name="bscscanhms-21061" /><ref name="bscscanhmscreation-21062" /><br />
<br />
== About HMS ==<br />
HMS appears to be short for HMagician. The HMS smart contract was created on August 12th, 2025.<br />
<br />
== The Reality ==<br />
Unfortunately, the burn logic of the HMS smart contract burn mechanism was vulnerable.<br />
<br />
== What Happened ==<br />
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<br />
{| class="wikitable"<br />
|+Key Event Timeline - HMS HMagician Smart Contract Burn Mechanism Exploited<br />
!Date<br />
!Event<br />
!Description<br />
|-<br />
|August 12th, 2025 6:00:25 AM MDT<br />
|Smart Contract Created<br />
|The HMS/HMagician smart contract is first launched on the Binance Smart Chain.<br />
|-<br />
|August 24th, 2025 8:43:45 PM MDT<br />
|Attack Transaction<br />
|The reported attack transaction is accepted and incorporated into the BSC blockchain.<br />
|-<br />
|August 24th, 2025 9:38:00 PM MDT<br />
|TenArmor Posts Tweet<br />
|TenArmor posts a tweet about the suspicious attack. The losses are reported as approximately $94.6k.<br />
|}<br />
<br />
== Technical Details ==<br />
The issue was reportedly related to the burn mechanism of the smart contract being exploited.<br />
<br />
== Total Amount Lost ==<br />
TenArmor reports "an approximately loss of $94.6K".<br />
<br />
The total amount lost has been estimated at $95,000 USD.<br />
<br />
== Immediate Reactions ==<br />
There is no suggestion that the project has reacted to the compromise publicly.<br />
<br />
== Ultimate Outcome ==<br />
TenArmor published a report with an overview of the exploit.<br />
<br />
== Total Amount Recovered ==<br />
There is no indication that any funds have been recovered.<br />
<br />
There do not appear to have been any funds recovered in this case.<br />
<br />
== Ongoing Developments ==<br />
There could be an investigation to trace the funds, or return to users.<br />
== Individual Prevention Policies ==<br />
{{Prevention:Individuals:Placeholder}}<br />
<br />
{{Prevention:Individuals:End}}<br />
<br />
== Platform Prevention Policies ==<br />
{{Prevention:Platforms:Placeholder}}<br />
<br />
{{Prevention:Platforms:End}}<br />
<br />
== Regulatory Prevention Policies ==<br />
{{Prevention:Regulators:Placeholder}}<br />
<br />
{{Prevention:Regulators:End}}<br />
<br />
== References ==<br />
<references><ref name="tenarmortweet-21059">[https://twitter.com/TenArmorAlert/status/1959822744884814118 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)</ref><br />
<br />
<ref name="bscscantransaction-21060">[https://bscscan.com/tx/0x8a680365a2bc0a416b45eaddf9ba56582ef5a96acd0cb14cee0b68cfb20e127e Attack Transaction - BSCScan] (Accessed Aug 25, 2025)</ref><br />
<br />
<ref name="bscscanhms-21061">[https://bscscan.com/address/0xc5de6173663b050d0ac798fc94432aebecffec13 HMS Smart Contract - BSCScan] (Accessed Aug 25, 2025)</ref><br />
<br />
<ref name="bscscanhmscreation-21062">[https://bscscan.com/tx/0xe0d457a1b3973736bd1150d8b4e8b5223eedc436e641697be9881024beeb0f90 HMS Smart Contract Creation - BSCScan] (Accessed Aug 25, 2025)</ref></references></div>Azoundria