Z123 Smart Contract Vulnerability - Revision history

Azoundria: COMPLETE 30 minutes. Added many additional sources from Twitter. Inquiring to get more information from security researchers. Attempted to better integrate technical analysis from Nick.

2024-05-14T16:48:03Z

COMPLETE 30 minutes. Added many additional sources from Twitter. Inquiring to get more information from security researchers. Attempted to better integrate technical analysis from Nick.

← Older revision		Revision as of 10:48, 14 May 2024
Line 4:		Line 4:
	[[File:Binancesecurity.jpg\|thumb\|Generic Image]]Z123 was a popular token with over 3,000 holders. Unfortunately the smart contract was vulnerable to price manipulation, which allowed an attacker to take $136k from the liquidity pools.		[[File:Binancesecurity.jpg\|thumb\|Generic Image]]Z123 was a popular token with over 3,000 holders. Unfortunately the smart contract was vulnerable to price manipulation, which allowed an attacker to take $136k from the liquidity pools.

	This is a global/international case not involving a specific country.<ref name="slowmisthackedarchive-13740" /><ref name="slowmistteamtwitter-13746" /><ref name="bscscan-13747" /><ref name="slowmistteamtwitter-13748" /><ref name="cube3aimedium-13749" /><ref name="certikalerttwitter-13750" /><ref name="coinmonksmedium-13751" /><ref name="bscscan-13752" /><ref name="bscscan-13753" /><ref name="cube3blog-13754" /><ref name="sunweb3secgithub-13755" />		This is a global/international case not involving a specific country.<ref name="slowmisthackedarchive-13740" /><ref name="slowmistteamtwitter-13746" /><ref name="bscscan-13747" /><ref name="slowmistteamtwitter-13748" /><ref name="cube3aimedium-13749" /><ref name="certikalerttwitter-13750" /><ref name="coinmonksmedium-13751" /><ref name="bscscan-13752" /><ref name="bscscan-13753" /><ref name="cube3blog-13754" /><ref name="sunweb3secgithub-13755" /><ref>https://twitter.com/PeckShieldAlert/status/1782322484911784385</ref><ref>https://twitter.com/BLOCKCHAINALETS/status/1782326194790146451</ref><ref>https://twitter.com/MetaTrustAlert/status/1782335252410818926</ref><ref>https://twitter.com/CyversAlerts/status/1782332201805206000</ref><ref>https://twitter.com/web3_watchdog/status/1782324228231987249</ref><ref>https://twitter.com/ChainAegis/status/1790221555999617207</ref>

	== About Z123 ==		== About Z123 ==
Line 60:		Line 60:
	\|April 4th, 2024 10:25:24 AM MDT		\|April 4th, 2024 10:25:24 AM MDT
	\|Wall Street Memes Attack		\|Wall Street Memes Attack
	\|The same attacker attacks the Wall Street Memes token.		\|The same attacker [[Wall Street Memes Pre-Sale Flash Loan Attack\|attacks the Wall Street Memes token]].
	\|-		\|-
	\|April 22nd, 2024 2:02:00 AM MDT		\|April 22nd, 2024 2:02:00 AM MDT
	\|Z123 Smart Contract Attack		\|Z123 Smart Contract Attack
	\|The Z123 smart contract is attacked.		\|The Z123 smart contract is attacked<ref name="bscscan-13753" />.
	\|-		\|-
	\|April 22nd, 2024 2:22:00 AM MDT		\|April 22nd, 2024 2:22:00 AM MDT
	\|SlowMist Tweet		\|SlowMist Tweet
	\|SlowMist publishes a tweet reporting on the vulnerability being exploited.		\|SlowMist publishes a tweet reporting on the vulnerability being exploited<ref name="slowmistteamtwitter-13746" />.
			\|-
			\|April 22nd, 2024 2:40:00 AM MDT
			\|Nick L Franklin Analysis
			\|Nick L Franklin performs a technical analysis of the smart contract exploit. He reports that the smart contract appears to be a uniswap router, and burns tokens each time. This mechanism formed the core of the exploit, according to his analysis<ref name=":0">[https://twitter.com/0xNickLFranklin/status/1782328709321752799 0xNickLFranklin - "Every time swap function of 0x6125c... is called, Z123 tokens in the QiaoLP are burned. I decompiled 0x6125c... contract, it was a uniswap router like contract, but it calls "update" function of Z123 token, which burns tokens of pair." - Twitter] (Accessed May 14, 2024)</ref>.
	\|-		\|-
	\|April 23rd, 2024 7:40:06 AM MDT		\|April 23rd, 2024 7:40:06 AM MDT
	\|CUBE3 Technical Analysis		\|CUBE3 Technical Analysis
	\|CUBE3 publishes a technical analysis of the exploit on Medium.		\|CUBE3 publishes a technical analysis of the exploit on Medium<ref name="cube3blog-13754" />.
	\|-		\|-
	\|April 29th, 2024 9:17:00 PM MDT		\|April 29th, 2024 9:17:00 PM MDT
	\|Weekly Security Report		\|Weekly Security Report
	\|Included in SlowMist weekly security report.		\|Included in SlowMist weekly security report<ref name="slowmistteamtwitter-13748" />.
	\|}		\|}

	== Technical Details ==		== 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?		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?

			Analysis By <ref name=":0" /><blockquote>Every time swap function of 0x6125c... is called, Z123 tokens in the QiaoLP are burned. I decompiled 0x6125c... contract, it was a uniswap router like contract, but it calls "update" function of Z123 token, which burns tokens of pair.</blockquote>

	== Total Amount Lost ==		== Total Amount Lost ==

Azoundria: Created page with "{{Imported Case Study|source=https://www.quadrigainitiative.com/casestudy/z123smartcontractvulnerability.php}} {{Unattributed Sources}} Generic ImageZ123 was a popular token with over 3,000 holders. Unfortunately the smart contract was vulnerable to price manipulation, which allowed an attacker to take $136k from the liquidity pools. This is a global/international case not involving a specific country.
2024-05-13T21:22:18Z

Created page with "{{Imported Case Study|source=https://www.quadrigainitiative.com/casestudy/z123smartcontractvulnerability.php}} {{Unattributed Sources}} thumb|Generic ImageZ123 was a popular token with over 3,000 holders. Unfortunately the smart contract was vulnerable to price manipulation, which allowed an attacker to take $136k from the liquidity pools. This is a global/international case not involving a specific country.<ref name="slowmisthackedarchive-..."

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

[[File:Binancesecurity.jpg|thumb|Generic Image]]Z123 was a popular token with over 3,000 holders. Unfortunately the smart contract was vulnerable to price manipulation, which allowed an attacker to take $136k from the liquidity pools.

This is a global/international case not involving a specific country.<ref name="slowmisthackedarchive-13740" /><ref name="slowmistteamtwitter-13746" /><ref name="bscscan-13747" /><ref name="slowmistteamtwitter-13748" /><ref name="cube3aimedium-13749" /><ref name="certikalerttwitter-13750" /><ref name="coinmonksmedium-13751" /><ref name="bscscan-13752" /><ref name="bscscan-13753" /><ref name="cube3blog-13754" /><ref name="sunweb3secgithub-13755" />

== About Z123 ==
"Token holders count: 3,331"

"In April 2024, a seemingly new hacker emerged, targeting Wall Street Memes and Z123 projects in quick succession with flash loan attacks, resulting in losses of $18,000 and $144,000 respectively."

"Z123 on BSC was attacked by a hacker due to a contract vulnerability, resulting in a loss of approximately $136k. The .update() function of Z123 was repeatedly called which burned extra tokens and inflated the price."

"Today, attacker activate itself again and deployed a new contract which was picked by ML service again (2024-04-22 07:55:32): 0x61Dd07Ce0cEcF0d7BaCf5EB208C57D16bBdEE168

Very soon (2024-04-22 10:02 AM), malicious transaction was detected (Mixer Malicious Contract): 0xc0c4e99a76da80a4cf43d3110364840151226c0a197c1728bb60dc3f1b3a6a27

Victim losses: $140K"

"Malicious actor using Flash loan to manipulate the price of the token in pool."

"By doing 81 iterations of token swaps and calling the ‘Update’ function of the pool, the price was manipulated."

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 - Z123 Smart Contract Vulnerability
!Date
!Event
!Description
|-
|April 4th, 2024 10:25:24 AM MDT
|Wall Street Memes Attack
|The same attacker attacks the Wall Street Memes token.
|-
|April 22nd, 2024 2:02:00 AM MDT
|Z123 Smart Contract Attack
|The Z123 smart contract is attacked.
|-
|April 22nd, 2024 2:22:00 AM MDT
|SlowMist Tweet
|SlowMist publishes a tweet reporting on the vulnerability being exploited.
|-
|April 23rd, 2024 7:40:06 AM MDT
|CUBE3 Technical Analysis
|CUBE3 publishes a technical analysis of the exploit on Medium.
|-
|April 29th, 2024 9:17:00 PM MDT
|Weekly Security Report
|Included in SlowMist weekly security report.
|}

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

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

<ref name="bscscan-13747">[https://bscscan.com/address/0xb000f121a173d7dd638bb080fee669a2f3af9760 SesameCloudToken | Address 0xb000f121a173d7dd638bb080fee669a2f3af9760 | BscScan] (May 13, 2024)</ref>

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

<ref name="cube3aimedium-13749">[https://medium.com/@CUBE3AI/warning-cube3-ai-detects-multiple-price-manipulations-by-same-address-7fabf4216268 CUBE3.AI Detects Multiple Price Manipulations by Same Address | by CUBE3.AI | Apr, 2024 | Medium] (May 13, 2024)</ref>

<ref name="certikalerttwitter-13750">[https://twitter.com/CertiKAlert/status/1782329325766795441 @CertiKAlert Twitter] (May 13, 2024)</ref>

<ref name="coinmonksmedium-13751">[https://medium.com/coinmonks/67m-rug-pulls-new-serial-crypto-hacker-and-the-zkasino-debacle-april-2024-crypto-crime-report-2457f4b703c0 67m Rug Pulls New Serial Crypto Hacker And The Zkasino Debacle April 2024 Crypto Crime Report] (May 13, 2024)</ref>

<ref name="bscscan-13752">[https://bscscan.com/token/0xb000f121a173d7dd638bb080fee669a2f3af9760?a=0x4e0451c281d1b008326983bcf2029b1968b7d06f Z123 (Z123) Token Tracker | BscScan] (May 13, 2024)</ref>

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

<ref name="cube3blog-13754">[https://blog.cube3.ai/2024/04/23/cube3-ai-detects-multiple-crypto-price-manipulations-by-same-address/ CUBE3.AI Detects Multiple Price Manipulations by Same Address - CUBE3.AI] (May 13, 2024)</ref>

<ref name="sunweb3secgithub-13755">[https://github.com/SunWeb3Sec/DeFiHackLabs?tab=readme-ov-file#20240422-z123---price-manipulation GitHub - SunWeb3Sec/DeFiHackLabs: Reproduce DeFi hacked incidents using Foundry.] (May 13, 2024)</ref></references>