Azoundria: Created page with "{{Imported Case Study|source=https://www.quadrigainitiative.com/casestudy/gputokentransfervulnerability.php}} {{Unattributed Sources}} Generic ImageA smart contract token named GPU on the Binance Smart Chain (with no relation to the similarly named GPU token by NodeAI) was launched and catastrophically failed on May 8th, 2024. The token had a vulnerability which allowed the user to double any amount of the token which they sent to them..."

2024-09-17T19:24:15Z

Created page with "{{Imported Case Study|source=https://www.quadrigainitiative.com/casestudy/gputokentransfervulnerability.php}} {{Unattributed Sources}} thumb|Generic ImageA smart contract token named GPU on the Binance Smart Chain (with no relation to the similarly named GPU token by NodeAI) was launched and catastrophically failed on May 8th, 2024. The token had a vulnerability which allowed the user to double any amount of the token which they sent to them..."

New page

{{Imported Case Study|source=https://www.quadrigainitiative.com/casestudy/gputokentransfervulnerability.php}}
{{Unattributed Sources}}

[[File:Binancesecurity.jpg|thumb|Generic Image]]A smart contract token named GPU on the Binance Smart Chain (with no relation to the similarly named GPU token by NodeAI) was launched and catastrophically failed on May 8th, 2024. The token had a vulnerability which allowed the user to double any amount of the token which they sent to themselves. The massive supply inflation caused a quick collapse of the token price.

This is a global/international case not involving a specific country.<ref name="slowmisthackedarchive-14042" /><ref name="slowmistteamtwitter-14043" /><ref name="bscscan-14044" /><ref name="bscscan-14045" /><ref name="peckshieldalerttwitter-14046" /><ref name="exvulsectwitter-14047" /><ref name="defisecuritytwitter-14048" /><ref name="metatrustalerttwitter-14049" /><ref name="chainaegistwitter-14050" /><ref name="web3watchdogtwitter-14051" /><ref name="cryptomeechietwitter-14052" /><ref name="dunkerkongethtwitter-14053" /><ref name="nodeaiethtwitter-14054" />

== About None ==
"We detected that $GPU was exploited due to an incorrect balance update."

"GPU on BNBChain was attacked, with a loss of about $32,000. There is a logic vulnerability in the _transfer function of the contract. When transferring money to yourself, the balance will increase by the amount of the transfer."

"classic self-transfer problem, user transfer himself will increase token balance, in this transfer code , if sender=recipient , balance of sender will add the transfer amount"

This is a global/international case not involving a specific country.

The background of the exchange platform, service, or individuals involved, as it would have been seen or understood at the time of the events.

Include:

* Known history of when and how the service was started.
* What problems does the company or service claim to solve?
* What marketing materials were used by the firm or business?
* Audits performed, and excerpts that may have been included.
* Business registration documents shown (fake or legitimate).
* How were people recruited to participate?
* Public warnings and announcements prior to the event.

Don't Include:
* Any wording which directly states or implies that the business is/was illegitimate, or that a vulnerability existed.
* Anything that wasn't reasonably knowable at the time of the event.
There could be more than one section here. If the same platform is involved with multiple incidents, then it can be linked to a main article page.

== 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 specific events of the loss and how it came about. What actually happened to cause the loss and some of the events leading up to it.
{| class="wikitable"
|+Key Event Timeline - GPU Token Transfer Vulnerability
!Date
!Event
!Description
|-
|May 8th, 2024 12:47:56 AM MDT
|Smart Contract Created
|The GPU smart contract is first created.
|-
|May 8th, 2024 4:01:39 AM MDT
|SlowMist Transaction Referenced
|The transaction which is referenced by SlowMist.
|-
|May 8th, 2024 4:26:00 AM MDT
|Report By SlowMist
|SlowMist reports on the GPU incident being attacked.
|-
|May 8th, 2024 4:27:00 AM MDT
|PeckShield Tweet Post
|PeckShield posts a tweet about the exploit.
|-
|May 8th, 2024 8:02:00 AM MDT
|ExVul Tweet Posted
|ExVul Security posts an analysis of the exploit.
|}

== Technical Details ==
This section includes specific detailed technical analysis of any security breaches which happened. What specific software vulnerabilities contributed to the problem and how were they exploited?

== Total Amount Lost ==
The total amount lost has been estimated at $32,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 ==
What was the end result? Was any investigation done? Were any individuals prosecuted? Was there a lawsuit? Was any tracing done?

== 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="slowmisthackedarchive-14042">[https://web.archive.org/web/20240530174927/https://hacked.slowmist.io/?c=&page=2 SlowMist Hacked - SlowMist Zone] (May 30, 2024)</ref>

<ref name="slowmistteamtwitter-14043">[https://twitter.com/SlowMist_Team/status/1788153412019978733 @SlowMist_Team Twitter] (May 30, 2024)</ref>

<ref name="bscscan-14044">[https://bscscan.com/address/0xf51cbf9f8e089ca48e454eb79731037a405972ce GPU | Address 0xf51cbf9f8e089ca48e454eb79731037a405972ce | BscScan] (May 30, 2024)</ref>

<ref name="bscscan-14045">[https://bscscan.com/tx/0x2c0ada695a507d7a03f4f308f545c7db4847b2b2c82de79e702d655d8c95dadb BNB Smart Chain Transaction Hash (Txhash) Details | BscScan] (May 30, 2024)</ref>

<ref name="peckshieldalerttwitter-14046">[https://twitter.com/PeckShieldAlert/status/1788153869987611113 @PeckShieldAlert Twitter] (May 30, 2024)</ref>

<ref name="exvulsectwitter-14047">[https://twitter.com/EXVULSEC/status/1788207789057425859 @EXVULSEC Twitter] (May 30, 2024)</ref>

<ref name="defisecuritytwitter-14048">[https://twitter.com/De_FiSecurity/status/1788168361383280652 @De_FiSecurity Twitter] (May 30, 2024)</ref>

<ref name="metatrustalerttwitter-14049">[https://twitter.com/MetaTrustAlert/status/1788158735720030367 @MetaTrustAlert Twitter] (May 30, 2024)</ref>

<ref name="chainaegistwitter-14050">[https://twitter.com/ChainAegis/status/1788190415914725858 @ChainAegis Twitter] (May 30, 2024)</ref>

<ref name="web3watchdogtwitter-14051">[https://twitter.com/web3_watchdog/status/1788155192715677943 @web3_watchdog Twitter] (May 30, 2024)</ref>

<ref name="cryptomeechietwitter-14052">[https://twitter.com/CryptoMeechie/status/1788175656037322864 @CryptoMeechie Twitter] (May 30, 2024)</ref>

<ref name="dunkerkongethtwitter-14053">[https://twitter.com/dunkerkongeth/status/1787965275997892622 @dunkerkongeth Twitter] (May 30, 2024)</ref>

<ref name="nodeaiethtwitter-14054">[https://twitter.com/NodeAIETH/status/1788362050889994307 @NodeAIETH Twitter] (May 30, 2024)</ref></references>

GPU Token Transfer Vulnerability - Revision history