BZx Exchange Price Manipulation - Revision history

Azoundria at 19:23, 1 May 2023

2023-05-01T19:23:29Z

← Older revision		Revision as of 13:23, 1 May 2023
Line 1:		Line 1:
	{{Imported Case Study\|source=https://www.quadrigainitiative.com/casestudy/bzxexchangepricemanipulation.php}}		{{Imported Case Study 2\|source=https://www.quadrigainitiative.com/casestudy/bzxexchangepricemanipulation.php}}
	{{Unattributed ~~Citations~~}}		{{Unattributed Sources}}

	[[File:Bzx.jpg\|thumb\|bZx]]The original bZx exchange platform contained a vulnerability which would allow an attacker to manipulate prices, which could have been used to steal platform assets.		[[File:Bzx.jpg\|thumb\|bZx]]The original bZx exchange platform contained a vulnerability which would allow an attacker to manipulate prices, which could have been used to steal platform assets.
Line 6:		Line 6:
	The vulnerability was fixed before it was able to be exploited.		The vulnerability was fixed before it was able to be exploited.

	This is a global/international case not involving a specific country.		This is a global/international case not involving a specific country.<ref name="openzeppelinforum-1155" /><ref name="ddexmedium-2019" /><ref name="b0xnetmedium-2023" /><ref name="samczsun-2020" /><ref name="bzxnetwork-2024" /><ref name="developer-2025" /><ref name="whitepaper-2026" /><ref name="etherscan-2027" />
	<ref name="openzeppelinforum-1155" /><ref name="ddexmedium-2019" /><ref name="b0xnetmedium-2023" /><ref name="samczsun-2020" /><ref name="bzxnetwork-2024" /><ref name="developer-2025" /><ref name="whitepaper-2026" /><ref name="etherscan-2027" />

	== About BZx ==		== About BZx ==
Line 55:		Line 54:
	!Description		!Description
	\|-		\|-
	\|September 3rd, 2019 ~~12:00:00 AM~~		\|September 3rd, 2019
	\|Main Event		\|Main Event
	\|Expand this into a brief description of what happened and the impact. If multiple lines are necessary, add them here.		\|Expand this into a brief description of what happened and the impact. If multiple lines are necessary, add them here.
Line 63:		Line 62:
	\|		\|
	\|}		\|}

			== 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 ==		== Total Amount Lost ==
Line 82:		Line 84:
	== Ongoing Developments ==		== Ongoing Developments ==
	What parts of this case are still remaining to be concluded?		What parts of this case are still remaining to be concluded?
			== General Prevention Policies ==
			There were no user funds lost in this case.
			== 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 ~~Policies ==~~		{{Prevention:Regulators:End}}
	~~There were no user funds lost in this case.~~

	== References ==		== References ==
	<references><ref name="openzeppelinforum-1155">[https://forum.openzeppelin.com/t/list-of-ethereum-smart-contracts-post-mortems/1191 List of Ethereum Smart Contracts Post-Mortems - Security - OpenZeppelin Community] (Jun 22, 2021)</ref>		<references><ref name="openzeppelinforum-1155">[https://forum.openzeppelin.com/t/list-of-ethereum-smart-contracts-post-mortems/1191 List of Ethereum Smart Contracts Post-Mortems - Security - OpenZeppelin Community] (Jun 23, 2021)</ref>

	<ref name="ddexmedium-2019">[https://medium.com/ddex/fixed-potential-vulnerability-in-contract-used-during-private-beta-217c0ed6f694 Fixed Potential Vulnerability In Contract Used During Private Beta] (Jun 22, 2021)</ref>		<ref name="ddexmedium-2019">[https://medium.com/ddex/fixed-potential-vulnerability-in-contract-used-during-private-beta-217c0ed6f694 Fixed Potential Vulnerability In Contract Used During Private Beta] (Jun 23, 2021)</ref>

	<ref name="b0xnetmedium-2023">[https://medium.com/@b0xNet/your-funds-are-safe-d35826fe9a87 Your Funds are Safe.. On Tuesday September 3rd, samczun, the… \| by bZx Team \| Medium] (Jun 22, 2021)</ref>		<ref name="b0xnetmedium-2023">[https://medium.com/@b0xNet/your-funds-are-safe-d35826fe9a87 Your Funds are Safe.. On Tuesday September 3rd, samczun, the… \| by bZx Team \| Medium] (Jun 23, 2021)</ref>

	<ref name="samczsun-2020">[https://samczsun.com/taking-undercollateralized-loans-for-fun-and-for-profit/ Taking undercollateralized loans for fun and for profit] (Jun 22, 2021)</ref>		<ref name="samczsun-2020">[https://samczsun.com/taking-undercollateralized-loans-for-fun-and-for-profit/ Taking undercollateralized loans for fun and for profit] (Jun 23, 2021)</ref>

	<ref name="bzxnetwork-2024">[https://bzx.network/ bZx - A Protocol For Tokenized Margin Trading and Lending] (Jun 23, 2021)</ref>		<ref name="bzxnetwork-2024">[https://bzx.network/ bZx - A Protocol For Tokenized Margin Trading and Lending] (Jun 24, 2021)</ref>

	<ref name="developer-2025">[https://developer.kyber.network/docs/Reserves-Intro/ Overview · KyberDeveloper · Powering Liquidity for the Ecosystem] (Jun 23, 2021)</ref>		<ref name="developer-2025">[https://developer.kyber.network/docs/Reserves-Intro/ Overview · KyberDeveloper · Powering Liquidity for the Ecosystem] (Jun 24, 2021)</ref>

	<ref name="whitepaper-2026">[https://whitepaper.io/document/43/kyber-network-whitepaper Kyber Network whitepaper - whitepaper.io] (Jun 23, 2021)</ref>		<ref name="whitepaper-2026">[https://whitepaper.io/document/43/kyber-network-whitepaper Kyber Network whitepaper - whitepaper.io] (Jun 24, 2021)</ref>

	<ref name="etherscan-2027">[https://etherscan.io/tx/0xce7df57e6b6d5589f19125b9298bbb36e672d373196d7610073540f59220c318 Ethereum Transaction Hash (Txhash) Details \| Etherscan] (Jun 23, 2021)</ref></references>		<ref name="etherscan-2027">[https://etherscan.io/tx/0xce7df57e6b6d5589f19125b9298bbb36e672d373196d7610073540f59220c318 Ethereum Transaction Hash (Txhash) Details \| Etherscan] (Jun 24, 2021)</ref></references>

Azoundria at 08:12, 17 February 2023

2023-02-17T08:12:10Z

← Older revision		Revision as of 02:12, 17 February 2023
Line 1:		Line 1:
	{{Imported Case Study\|source=https://www.quadrigainitiative.com/casestudy/bzxexchangepricemanipulation.php}}		{{Imported Case Study\|source=https://www.quadrigainitiative.com/casestudy/bzxexchangepricemanipulation.php}}
			{{Unattributed Citations}}

	[[File:Bzx.jpg\|thumb\|~~BZx~~]]The original bZx exchange platform contained a vulnerability which would allow an attacker to manipulate prices, which could have been used to steal platform assets.		[[File:Bzx.jpg\|thumb\|bZx]]The original bZx exchange platform contained a vulnerability which would allow an attacker to manipulate prices, which could have been used to steal platform assets.

	The vulnerability was fixed before it was able to be exploited.		The vulnerability was fixed before it was able to be exploited.

	This is a global/international case not involving a specific country.		This is a global/international case not involving a specific country.
			<ref name="openzeppelinforum-1155" /><ref name="ddexmedium-2019" /><ref name="b0xnetmedium-2023" /><ref name="samczsun-2020" /><ref name="bzxnetwork-2024" /><ref name="developer-2025" /><ref name="whitepaper-2026" /><ref name="etherscan-2027" />

	== About BZx ==		== About BZx ==
Line 33:		Line 35:

	Don't Include:		Don't Include:

	* Any wording which directly states or implies that the business is/was illegitimate, or that a vulnerability existed.		* 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.		* Anything that wasn't reasonably knowable at the time of the event.
Line 55:		Line 56:
	\|-		\|-
	\|September 3rd, 2019 12:00:00 AM		\|September 3rd, 2019 12:00:00 AM
	\|~~First~~ Event		\|Main Event
	\|~~This is an expanded~~ description of what happened and the impact. If multiple lines are necessary, add them here.		\|Expand this into a brief description of what happened and the impact. If multiple lines are necessary, add them here.
	\|-
	\|
	\|
	\|
	\|-		\|-
	\|		\|
Line 68:		Line 65:

	== Total Amount Lost ==		== Total Amount Lost ==
	~~The total amount~~ lost ~~is unknown~~.		No funds were lost.

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

	== Total Amount Recovered ==		== Total Amount Recovered ==
	~~It is unknown how much was~~ 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?		What funds were recovered? What funds were reimbursed for those affected users?
Line 90:		Line 87:

	== References ==		== References ==
	[https://forum.openzeppelin.com/t/list-of-ethereum-smart-contracts-post-mortems/1191 List of Ethereum Smart Contracts Post-Mortems - Security - OpenZeppelin Community] (Jun 22)		<references><ref name="openzeppelinforum-1155">[https://forum.openzeppelin.com/t/list-of-ethereum-smart-contracts-post-mortems/1191 List of Ethereum Smart Contracts Post-Mortems - Security - OpenZeppelin Community] (Jun 22, 2021)</ref>

	[https://medium.com/ddex/fixed-potential-vulnerability-in-contract-used-during-private-beta-217c0ed6f694 Fixed Potential Vulnerability In Contract Used During Private Beta] (Jun 22)		<ref name="ddexmedium-2019">[https://medium.com/ddex/fixed-potential-vulnerability-in-contract-used-during-private-beta-217c0ed6f694 Fixed Potential Vulnerability In Contract Used During Private Beta] (Jun 22, 2021)</ref>

	[https://medium.com/@b0xNet/your-funds-are-safe-d35826fe9a87 Your Funds are Safe.. On Tuesday September 3rd, samczun, the… \| by bZx Team \| Medium] (Jun 22)		<ref name="b0xnetmedium-2023">[https://medium.com/@b0xNet/your-funds-are-safe-d35826fe9a87 Your Funds are Safe.. On Tuesday September 3rd, samczun, the… \| by bZx Team \| Medium] (Jun 22, 2021)</ref>

	[https://samczsun.com/taking-undercollateralized-loans-for-fun-and-for-profit/ Taking undercollateralized loans for fun and for profit] (Jun 22)		<ref name="samczsun-2020">[https://samczsun.com/taking-undercollateralized-loans-for-fun-and-for-profit/ Taking undercollateralized loans for fun and for profit] (Jun 22, 2021)</ref>

	[https://bzx.network/ bZx - A Protocol For Tokenized Margin Trading and Lending] (Jun 23)		<ref name="bzxnetwork-2024">[https://bzx.network/ bZx - A Protocol For Tokenized Margin Trading and Lending] (Jun 23, 2021)</ref>

	[https://developer.kyber.network/docs/Reserves-Intro/ Overview · KyberDeveloper · Powering Liquidity for the Ecosystem] (Jun 23)		<ref name="developer-2025">[https://developer.kyber.network/docs/Reserves-Intro/ Overview · KyberDeveloper · Powering Liquidity for the Ecosystem] (Jun 23, 2021)</ref>

	[https://whitepaper.io/document/43/kyber-network-whitepaper Kyber Network whitepaper - whitepaper.io] (Jun 23)		<ref name="whitepaper-2026">[https://whitepaper.io/document/43/kyber-network-whitepaper Kyber Network whitepaper - whitepaper.io] (Jun 23, 2021)</ref>

	[https://etherscan.io/tx/0xce7df57e6b6d5589f19125b9298bbb36e672d373196d7610073540f59220c318 Ethereum Transaction Hash (Txhash) Details \| Etherscan] (Jun 23)		<ref name="etherscan-2027">[https://etherscan.io/tx/0xce7df57e6b6d5589f19125b9298bbb36e672d373196d7610073540f59220c318 Ethereum Transaction Hash (Txhash) Details \| Etherscan] (Jun 23, 2021)</ref></references>

Azoundria: Created page with "{{Imported Case Study|source=https://www.quadrigainitiative.com/casestudy/bzxexchangepricemanipulation.php}} BZxThe original bZx exchange platform contained a vulnerability which would allow an attacker to manipulate prices, which could have been used to steal platform assets. The vulnerability was fixed before it was able to be exploited. This is a global/international case not involving a specific country. == About BZx == bZx is "[t]he most p..."

2023-01-25T03:17:11Z

Created page with "{{Imported Case Study|source=https://www.quadrigainitiative.com/casestudy/bzxexchangepricemanipulation.php}} thumb|BZxThe original bZx exchange platform contained a vulnerability which would allow an attacker to manipulate prices, which could have been used to steal platform assets. The vulnerability was fixed before it was able to be exploited. This is a global/international case not involving a specific country. == About BZx == bZx is "[t]he most p..."

New page

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

[[File:Bzx.jpg|thumb|BZx]]The original bZx exchange platform contained a vulnerability which would allow an attacker to manipulate prices, which could have been used to steal platform assets.

The vulnerability was fixed before it was able to be exploited.

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

== About BZx ==
bZx is "[t]he most powerful open finance protocol". You can use it to "[b]uild applications that empower lenders, borrowers, and traders with the most flexible decentralized finance protocol on Ethereum." "Fulcrum is a project built by the bZx team on top of bZx itself. One feature of Fulcrum is the ability to take a loan on an iToken (read more about that here) using any* other token as collateral. In order to determine how much collateral is needed, bZx uses the Kyber Network as an on-chain decentralized oracle to check the conversion rate between the collateral token and the loan token."

"KyberNetwork [is] an on-chain protocol which allows instant exchange and conversion of digital assets (e.g. crypto tokens) and cryptocurrencies (e.g. Ether, Bitcoin, ZCash) with high liquidity. KyberNetwork [aimed to] be the first system that implements several ideal operating properties of an exchange including trustless, decentralized execution, instant trade and high liquidity." "KyberNetwork exchange rates are visible to other smart contracts. Hence, it enables the implementation of advanced financial instruments such as swap contracts. The quotes provided by KyberNetwork are secure as they reflect the real rates which are being used to trade between pairs of tokens."

"On Tuesday September 3rd, samczun, [then known as] the security researcher who found the critical bug in 0x, alerted [bZx] to an exploit leveraging [their] implementation of Kyber’s price feeds." "This was an attack vector that both ourselves and our auditors did not detect."

"The premise of the attack involved manipulating the price feed with a sandwich attack at the time of taking out the loan." The attacker can "significantly affect the apparent exchange rate between WAX and ETH simply by listing an order, which means that we can trick any project which relies on Kyber to provide an accurate FMV." We can "turn a profit of approximately 1200ETH by (1) Listing an order buying 1 WAX for 10 ETH, increasing the price from 0.00ETH/WAX to 10ETH/WAX. (2) Borrowing DAI from bZx using WAX as a collateral. (3) Cancelling all orders and converting all assets to ETH."

"[T]he exploit exists and has never been used. The exploit was immediately patched." "The bZx team blocked this attack by whitelisting tokens which can be used as collateral." "We are thankful to members of the community like samczun for strengthening the security of the ecosystem."

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 - bZx Exchange Price Manipulation
!Date
!Event
!Description
|-
|September 3rd, 2019 12:00:00 AM
|First Event
|This is an expanded description of what happened and the impact. If multiple lines are necessary, add them here.
|-
|
|
|
|-
|
|
|
|}

== Total Amount Lost ==
The total amount lost is unknown.

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 ==
It is unknown how much was recovered.

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?

== Prevention Policies ==
There were no user funds lost in this case.

== References ==
[https://forum.openzeppelin.com/t/list-of-ethereum-smart-contracts-post-mortems/1191 List of Ethereum Smart Contracts Post-Mortems - Security - OpenZeppelin Community] (Jun 22)

[https://medium.com/ddex/fixed-potential-vulnerability-in-contract-used-during-private-beta-217c0ed6f694 Fixed Potential Vulnerability In Contract Used During Private Beta] (Jun 22)

[https://medium.com/@b0xNet/your-funds-are-safe-d35826fe9a87 Your Funds are Safe.. On Tuesday September 3rd, samczun, the… | by bZx Team | Medium] (Jun 22)

[https://samczsun.com/taking-undercollateralized-loans-for-fun-and-for-profit/ Taking undercollateralized loans for fun and for profit] (Jun 22)

[https://bzx.network/ bZx - A Protocol For Tokenized Margin Trading and Lending] (Jun 23)

[https://developer.kyber.network/docs/Reserves-Intro/ Overview · KyberDeveloper · Powering Liquidity for the Ecosystem] (Jun 23)

[https://whitepaper.io/document/43/kyber-network-whitepaper Kyber Network whitepaper - whitepaper.io] (Jun 23)

[https://etherscan.io/tx/0xce7df57e6b6d5589f19125b9298bbb36e672d373196d7610073540f59220c318 Ethereum Transaction Hash (Txhash) Details | Etherscan] (Jun 23)