APEMAGA Smart 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!
APEMAGA launched without any marketing, website, or social media. Within an hour of launch, the APEMAGA smart contract was drained of $32k. It is unclear what caused the attack, and what the effect was on any users of the protocol.[1][2][3][4][5][6][7][8][9][10][11][12][13]
About APEMAGA
Contract: 0x56ff4afd909aa66a1530fe69bf94c74e6d44500c
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.
| Date | Event | Description |
|---|---|---|
| June 26th, 2024 3:56:11 AM MDT | Smart Contract Created | The APEMAGA smart contract is created. |
| June 26th, 2024 4:27:35 AM MDT | Blockchain Transaction | The blockchain transaction drains the APEMAGA liquidity pool by swapping just 0.1 ETH for 59,632,616.815636881 APEMAGA tokens. |
| June 26th, 2024 5:00:00 AM MDT | ApeMaga is featured on the "Top Trending Tokens of the Hour". | |
| June 26th, 2024 5:00:00 AM MDT | Top Trending Token | ApeMaga is featured on the "Top Trending Tokens of the Hour". |
Technical Details
$APEMAGA on #Ethereum is suspected to be attacked, with a loss of ~$32K.
Attacker: 0xb297735e9fb3e695ccce3963bfe042f318901ea0
Attack transaction: https://app.chainaegis.com/result?type=eth&search=0xb310d76120a8a1124533e49d6e91721624435b0df240b54c897307205df06105 Loss 59,632,616 $APEMAGA, Converted to 9.37 $ETH.
Total Amount Lost
"Loss 59,632,616 $APEMAGA, Converted to 9.37 $ETH."
The total amount lost has been estimated at $32,000 USD.
Immediate Reactions
"APEMAGA on Ethereum is suspected to be attacked, with a loss of ~$32K."
"Loss 59,632,616 $APEMAGA, Converted to 9.37 $ETH."
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
The total amount recovered is unknown.
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 Apr 24, 2024)
- ↑ Ethereum Transaction Hash (Txhash) Details | Etherscan (Accessed Jul 2, 2024)
- ↑ @Bilaxy_exchange Twitter (Accessed Jul 2, 2024)
- ↑ @sharkteamorg Twitter (Accessed Jul 2, 2024)
- ↑ @axon_alert Twitter (Accessed Jul 2, 2024)
- ↑ @atlantes_io Twitter (Accessed Jul 2, 2024)
- ↑ @CoinspeedrunBot Twitter (Accessed Jul 2, 2024)
- ↑ APEMAGA (APEMAGA) contract is 0x56ff4afd909aa66a1530fe69bf94c74e6d44500c on ETH | Top100Token (Accessed Jul 2, 2024)
- ↑ @ChainAegis Twitter (Accessed Jul 2, 2024)
- ↑ https://dexscreener.com/ethereum/0x45f4186a2b5a25b8783caffd0f1a68cdefb89105 (Accessed Jul 2, 2024)
- ↑ ChainAegis (Accessed Jul 2, 2024)
- ↑ Ethereum Transaction Hash (Txhash) Details | Etherscan (Accessed Jul 2, 2024)
- ↑ APEMAGA (APEMAGA) Token Tracker | Etherscan (Accessed Jul 2, 2024)