Azoundria at 22:26, 16 January 2025

2025-01-16T22:26:57Z

Azoundria: Created page with "{{Imported Case Study With About|source=https://www.quadrigainitiative.com/casestudy/mfttokencontractflawedtransferlogic.php}} {{Unattributed Sources}} Binance Smart ChainMFT was a smart contract in the Binance Smart Chain. On November 17th, a vulnerability in the smart contract was exploited. The attacker ultimately transferred their gains into another token trading pair that they created.
2025-01-10T20:32:21Z

Created page with "{{Imported Case Study With About|source=https://www.quadrigainitiative.com/casestudy/mfttokencontractflawedtransferlogic.php}} {{Unattributed Sources}} thumb|Binance Smart ChainMFT was a smart contract in the Binance Smart Chain. On November 17th, a vulnerability in the smart contract was exploited. The attacker ultimately transferred their gains into another token trading pair that they created.<ref name="bscscan-17099" /><ref name="Malicio..."

New page
{{Imported Case Study With About|source=https://www.quadrigainitiative.com/casestudy/mfttokencontractflawedtransferlogic.php}}
{{Unattributed Sources}}

[[File:Binancesecurity.jpg|thumb|Binance Smart Chain]]MFT was a smart contract in the Binance Smart Chain. On November 17th, a vulnerability in the smart contract was exploited. The attacker ultimately transferred their gains into another token trading pair that they created.<ref name="bscscan-17099" /><ref name="Malicious Smart Contract-17100" /><ref name="bscscan-17101" /><ref name="tenarmoralerttwitter-17102" /><ref name="bscscan-17103" />

== About MFT ==
MFT is a smart contract in the Binance Smart Chain.

== The Reality ==
This sections is included if a case involved deception or information that was unknown at the time. Examples include:

* When the service was actually started (if different than the "official story").
* Who actually ran a service and their own personal history.
* How the service was structured behind the scenes. (For example, there was no "trading bot".)
* Details of what audits reported and how vulnerabilities were missed during auditing.

== What Happened ==
"The MFT (MFT) on BSC is suspected to have been attacked, resulting in a loss of approximately $33.7K."
{| class="wikitable"
|+Key Event Timeline - MFT Token Contract Flawed Transfer Logic
!Date
!Event
!Description
|-
|November 17th, 2024 1:13:49 PM MST
|Malicious Smart Contract Created
|The malicious smart contract used by the attacker is created.
|-
|November 17th, 2024 1:17:16 PM MST
|Binance Smart Chain Transaction
|The exploit transaction happens on the Binance Smart Chain.
|}

== Technical Details ==
"The root cause is in the flawed logic of transfer(), which will burn token from the pool when user trys to sell token.

so attacker first makes a few transfers to the pair to trigger the sell in the MFT transfer(), this setup makes sure the MFT balance of MFT token itself will not interfere the subsequent attack, and then buy a large amount of MFT, making the MFT balance of the pair really low, and then selling an equal amount of MFT again, and due to burn [mechanism], the pool is drained.

interestingly the attacker transfers all profit to a self-created pair of another token for no obvious reason, we have seen similar way of this handling a couple of times, indicating it is very likely from a seasoned attacker."

== Total Amount Lost ==
The total amount lost has been estimated at $34,000 USD.

How much was lost and how was it calculated? If there are conflicting reports, which are accurate and where does the discrepancy lie?

== Immediate Reactions ==
How did the various parties involved (firm, platform, management, and/or affected individual(s)) deal with the events? Were services shut down? Were announcements made? Were groups formed?

== Ultimate Outcome ==
"Our system has detected a suspicious attack involving #MFT on #BSC, resulting in an approximately loss of $33.7K."

== Total Amount Recovered ==
There do not appear to have been any funds recovered in this case.

What funds were recovered? What funds were reimbursed for those affected users?

== Ongoing Developments ==
What parts of this case are still remaining to be concluded?
== Individual Prevention Policies ==
{{Prevention:Individuals:Placeholder}}

{{Prevention:Individuals:End}}

== Platform Prevention Policies ==
{{Prevention:Platforms:Placeholder}}

{{Prevention:Platforms:End}}

== Regulatory Prevention Policies ==
{{Prevention:Regulators:Placeholder}}

{{Prevention:Regulators:End}}

== References ==
<references><ref name="bscscan-17099">[https://bscscan.com/tx/0xe24ee2af7ceee6d6fad1cacda26004adfe0f44d397a17d2aca56c9a01d759142 BNB Smart Chain Transaction Hash (Txhash) Details | BscScan] (Accessed Jan 8, 2025)</ref>

<ref name="Malicious Smart Contract-17100">[https://bscscan.com/address/0x6e088c3dd1055f5dd1660c1c64de2af8110b85a8 Contract Address 0x6e088c3dd1055f5dd1660c1c64de2af8110b85a8 | BscScan] (Accessed Jan 8, 2025)</ref>

<ref name="bscscan-17101">[https://bscscan.com/tx/0xeff6335a5918bcc5d03b747c24e6eacc9f76805167aa9f8ba6faf27fbf70b4c7 BNB Smart Chain Transaction Hash (Txhash) Details | BscScan] (Accessed Jan 8, 2025)</ref>

<ref name="tenarmoralerttwitter-17102">[https://twitter.com/TenArmorAlert/status/1858351609371406617 @TenArmorAlert Twitter] (Accessed Jan 8, 2025)</ref>

<ref name="bscscan-17103">[https://bscscan.com/address/0x84b45294404c165e9cc60b69fc9be3ac97db1aab Contract Address 0x84b45294404c165e9cc60b69fc9be3ac97db1aab | BscScan] (Accessed Jan 8, 2025)</ref></references>

MFT Token Contract Flawed Transfer Logic - Revision history

Azoundria at 22:26, 16 January 2025