Smart Bank Token (SBT) Contract Drained
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!
Smart Bank Token was a contract on the Binance Smart Chain. The contract was created and drained within 5 minutes of creation. It is unclear what the intent of the token was, and how it was promoted.[1][2][3][4]
About Smart Bank Token
https://bscscan.com/address/0x88f9e1799465655f0dd206093dbd08922a1d9e28
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 Smart Bank Token (SBT) contract on BNBChain was attacked, resulting in a loss of approximately $56,000."
Date | Event | Description |
---|---|---|
July 11th, 2024 5:19:06 AM MDT | Smart Contract Creation | The smart bank token smart contract is originally created. |
July 11th, 2024 5:24:29 AM MDT | Malicious Transaction | The malicious transaction which is responsible for draining the smart bank token smart contract on the Binance Smart Chain. |
Technical Details
"The Smart Bank Token (SBT) contract on BNBChain was attacked, resulting in a loss of approximately $56,000."
Total Amount Lost
The total amount lost has been estimated at $56,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
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
- ↑ SlowMist Hacked - SlowMist Zone (Accessed Aug 29, 2024)
- ↑ BNB Smart Chain Transaction Hash (Txhash) Details | BscScan (Accessed Aug 29, 2024)
- ↑ BNB Smart Chain Transaction Hash (Txhash) Details | BscScan (Accessed Aug 29, 2024)
- ↑ Contract Address 0x88f9e1799465655f0dd206093dbd08922a1d9e28 | BscScan (Accessed Aug 29, 2024)