BZx Fulcrum White Hack - Revision history

Azoundria at 19:29, 1 May 2023

2023-05-01T19:29:08Z

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

	[[File:Bzxfulcrum.jpg\|thumb\|bZx]]The bZx Fulcrum smart contract hot wallet had a $2.5m vulnerability which was not exploited. After refusing to pay out a requested bounty, the team aimed to cover up the exploit. No funds were lost in this case.		[[File:Bzxfulcrum.jpg\|thumb\|bZx]]The bZx Fulcrum smart contract hot wallet had a $2.5m vulnerability which was not exploited. After refusing to pay out a requested bounty, the team aimed to cover up the exploit. No funds were lost in this case.

	This is a global/international case not involving a specific country.		This is a global/international case not involving a specific country.<ref name="cryptosec-5385" /><ref name="1inchblog-5438" /><ref name="bzxnetworkmedium-2016" /><ref name="defirate-2017" /><ref name="decrypt-2018" /><ref name="bzxnetwork-2024" /><ref name="fulcrum-2014" /><ref name="etherscan-5439" /><ref name="etherscan-5440" />
	<ref name="cryptosec-5385" /><ref name="1inchblog-5438" /><ref name="bzxnetworkmedium-2016" /><ref name="defirate-2017" /><ref name="decrypt-2018" /><ref name="bzxnetwork-2024" /><ref name="fulcrum-2014" /><ref name="etherscan-5439" /><ref name="etherscan-5440" />

	== About BZx ==		== About BZx ==
Line 67:		Line 66:
	!Description		!Description
	\|-		\|-
	\|January 11th, 2020 ~~12:00:00 AM~~		\|January 11th, 2020
	\|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 75:		Line 74:
	\|		\|
	\|}		\|}

			== 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 94:		Line 96:
	== 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 ==
			No funds were lost in this case. An independent industry insurance fund would be able to publish reports, cover losses, and/or pay bounties in the best interests of the industry as a whole.
			== 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}}
	~~No funds were lost in this case. An independent industry insurance fund would be able to publish reports, cover losses, and/or pay bounties in the best interests of the industry as a whole.~~

	== References ==		== References ==
Line 103:		Line 118:
	<ref name="1inchblog-5438">[https://blog.1inch.io/yes-we-hacked-bzx-fulcrum-but-one-month-ago-3f7e5c437ee3 https://blog.1inch.io/yes-we-hacked-bzx-fulcrum-but-one-month-ago-3f7e5c437ee3] (Jan 9, 2022)</ref>		<ref name="1inchblog-5438">[https://blog.1inch.io/yes-we-hacked-bzx-fulcrum-but-one-month-ago-3f7e5c437ee3 https://blog.1inch.io/yes-we-hacked-bzx-fulcrum-but-one-month-ago-3f7e5c437ee3] (Jan 9, 2022)</ref>

	<ref name="bzxnetworkmedium-2016">[https://medium.com/bzxnetwork/introducing-fulcrum-tokenized-margin-made-dead-simple-e65ccc82393f Introducing Fulcrum Tokenized Margin Made Dead Simple] (Jun 25, 2021)</ref>		<ref name="bzxnetworkmedium-2016">[https://medium.com/bzxnetwork/introducing-fulcrum-tokenized-margin-made-dead-simple-e65ccc82393f Introducing Fulcrum Tokenized Margin Made Dead Simple] (Jun 26, 2021)</ref>

	<ref name="defirate-2017">[https://defirate.com/bzx/ Fulcrum Trade - bZx Decentralized Lending & Margin Trading] (Jun 25, 2021)</ref>		<ref name="defirate-2017">[https://defirate.com/bzx/ Fulcrum Trade - bZx Decentralized Lending & Margin Trading] (Jun 26, 2021)</ref>

	<ref name="decrypt-2018">[https://decrypt.co/resources/bzx-ethereum-defi-decentralized-finance-explained-guide What is bZx? A 3-minute guide to the defi trading platform - Decrypt] (Jun 25, 2021)</ref>		<ref name="decrypt-2018">[https://decrypt.co/resources/bzx-ethereum-defi-decentralized-finance-explained-guide What is bZx? A 3-minute guide to the defi trading platform - Decrypt] (Jun 26, 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="fulcrum-2014">[https://fulcrum.trade/ Crypto Margin Trading with Fulcrum \| bZx] (Jun 25, 2021)</ref>		<ref name="fulcrum-2014">[https://fulcrum.trade/ Crypto Margin Trading with Fulcrum \| bZx] (Jun 26, 2021)</ref>

	<ref name="etherscan-5439">[https://etherscan.io/tx/0xa5611cdc8f0c9e90b89399eb81016cd6346206155d751ea318c6bb4ab129cdc3 Ethereum Transaction Hash (Txhash) Details \| Etherscan] (Jan 9, 2022)</ref>		<ref name="etherscan-5439">[https://etherscan.io/tx/0xa5611cdc8f0c9e90b89399eb81016cd6346206155d751ea318c6bb4ab129cdc3 Ethereum Transaction Hash (Txhash) Details \| Etherscan] (Jan 9, 2022)</ref>

	<ref name="etherscan-5440">[https://etherscan.io/tx/0xc2e02ef9d45bd5ca645ad0c7a85425d1f75418de23cea1f996bd65c249194c3e Ethereum Transaction Hash (Txhash) Details \| Etherscan] (Jan 9, 2022)</ref></references>		<ref name="etherscan-5440">[https://etherscan.io/tx/0xc2e02ef9d45bd5ca645ad0c7a85425d1f75418de23cea1f996bd65c249194c3e Ethereum Transaction Hash (Txhash) Details \| Etherscan] (Jan 9, 2022)</ref></references>

Azoundria at 17:13, 17 February 2023

2023-02-17T17:13:26Z

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

	[[File:Bzxfulcrum.jpg\|thumb\|~~BZx~~]]The bZx Fulcrum smart contract hot wallet had a $2.5m vulnerability which was not exploited. After refusing to pay out a requested bounty, the team aimed to cover up the exploit. No funds were lost in this case.		[[File:Bzxfulcrum.jpg\|thumb\|bZx]]The bZx Fulcrum smart contract hot wallet had a $2.5m vulnerability which was not exploited. After refusing to pay out a requested bounty, the team aimed to cover up the exploit. No funds were lost in this case.

	This is a global/international case not involving a specific country.		This is a global/international case not involving a specific country.
			<ref name="cryptosec-5385" /><ref name="1inchblog-5438" /><ref name="bzxnetworkmedium-2016" /><ref name="defirate-2017" /><ref name="decrypt-2018" /><ref name="bzxnetwork-2024" /><ref name="fulcrum-2014" /><ref name="etherscan-5439" /><ref name="etherscan-5440" />

	== About BZx ==		== About BZx ==
Line 45:		Line 47:

	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 67:		Line 68:
	\|-		\|-
	\|January 11th, 2020 12:00:00 AM		\|January 11th, 2020 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 80:		Line 77:

	== Total Amount Lost ==		== Total Amount Lost ==
	The total amount lost ~~is unknown~~.		The total amount at risk has been estimated at $2,500,000 USD. 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 91:		Line 88:

	== 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 102:		Line 99:

	== References ==		== References ==
	[https://cryptosec.info/defi-hacks/ Comprehensive List of DeFi Hacks & Exploits - CryptoSec] (Jan 8)		<references><ref name="cryptosec-5385">[https://cryptosec.info/defi-hacks/ Comprehensive List of DeFi Hacks & Exploits - CryptoSec] (Jan 8, 2022)</ref>

	[https://blog.1inch.io/yes-we-hacked-bzx-fulcrum-but-one-month-ago-3f7e5c437ee3 https://blog.1inch.io/yes-we-hacked-bzx-fulcrum-but-one-month-ago-3f7e5c437ee3] (Jan 9)		<ref name="1inchblog-5438">[https://blog.1inch.io/yes-we-hacked-bzx-fulcrum-but-one-month-ago-3f7e5c437ee3 https://blog.1inch.io/yes-we-hacked-bzx-fulcrum-but-one-month-ago-3f7e5c437ee3] (Jan 9, 2022)</ref>

	[https://medium.com/bzxnetwork/introducing-fulcrum-tokenized-margin-made-dead-simple-e65ccc82393f Introducing Fulcrum Tokenized Margin Made Dead Simple] (Jun 25)		<ref name="bzxnetworkmedium-2016">[https://medium.com/bzxnetwork/introducing-fulcrum-tokenized-margin-made-dead-simple-e65ccc82393f Introducing Fulcrum Tokenized Margin Made Dead Simple] (Jun 25, 2021)</ref>

	[https://defirate.com/bzx/ Fulcrum Trade - bZx Decentralized Lending & Margin Trading] (Jun 25)		<ref name="defirate-2017">[https://defirate.com/bzx/ Fulcrum Trade - bZx Decentralized Lending & Margin Trading] (Jun 25, 2021)</ref>

	[https://decrypt.co/resources/bzx-ethereum-defi-decentralized-finance-explained-guide What is bZx? A 3-minute guide to the defi trading platform - Decrypt] (Jun 25)		<ref name="decrypt-2018">[https://decrypt.co/resources/bzx-ethereum-defi-decentralized-finance-explained-guide What is bZx? A 3-minute guide to the defi trading platform - Decrypt] (Jun 25, 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://fulcrum.trade/ Crypto Margin Trading with Fulcrum \| bZx] (Jun 25)		<ref name="fulcrum-2014">[https://fulcrum.trade/ Crypto Margin Trading with Fulcrum \| bZx] (Jun 25, 2021)</ref>

	[https://etherscan.io/tx/0xa5611cdc8f0c9e90b89399eb81016cd6346206155d751ea318c6bb4ab129cdc3 Ethereum Transaction Hash (Txhash) Details \| Etherscan] (Jan 9)		<ref name="etherscan-5439">[https://etherscan.io/tx/0xa5611cdc8f0c9e90b89399eb81016cd6346206155d751ea318c6bb4ab129cdc3 Ethereum Transaction Hash (Txhash) Details \| Etherscan] (Jan 9, 2022)</ref>

	[https://etherscan.io/tx/0xc2e02ef9d45bd5ca645ad0c7a85425d1f75418de23cea1f996bd65c249194c3e Ethereum Transaction Hash (Txhash) Details \| Etherscan] (Jan 9)		<ref name="etherscan-5440">[https://etherscan.io/tx/0xc2e02ef9d45bd5ca645ad0c7a85425d1f75418de23cea1f996bd65c249194c3e Ethereum Transaction Hash (Txhash) Details \| Etherscan] (Jan 9, 2022)</ref></references>

Azoundria: Created page with "{{Imported Case Study|source=https://www.quadrigainitiative.com/casestudy/bzxfulcrumwhitehacked.php}} BZxThe bZx Fulcrum smart contract hot wallet had a $2.5m vulnerability which was not exploited. After refusing to pay out a requested bounty, the team aimed to cover up the exploit. No funds were lost in this case. This is a global/international case not involving a specific country. == About BZx == "bZx (formerly known at b0x) was concei..."

2023-01-25T17:10:39Z

Created page with "{{Imported Case Study|source=https://www.quadrigainitiative.com/casestudy/bzxfulcrumwhitehacked.php}} thumb|BZxThe bZx Fulcrum smart contract hot wallet had a $2.5m vulnerability which was not exploited. After refusing to pay out a requested bounty, the team aimed to cover up the exploit. No funds were lost in this case. This is a global/international case not involving a specific country. == About BZx == "bZx (formerly known at b0x) was concei..."

New page

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

[[File:Bzxfulcrum.jpg|thumb|BZx]]The bZx Fulcrum smart contract hot wallet had a $2.5m vulnerability which was not exploited. After refusing to pay out a requested bounty, the team aimed to cover up the exploit. No funds were lost in this case.

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

== About BZx ==
"bZx (formerly known at b0x) was conceived in August 2017." "bZx was founded by Tom Bean, a self-starter with years of experience working with top-profile car companies using GPS technology." "The project first started publicly marketing themselves during ETHDenver in 2018. Since then, the protocol published their formal whitepaper in February of 2018, followed by a testnet release in April and a full mainnet launch in August of the same year." "The bZx team currently lists 8 team members and 3 advisors on their official website."

"bZx is a set of smart contracts built on top of Ethereum that allows people to lend and margin trade without having to rely on third parties." "Fulcrum is a powerful DeFi platform for tokenized lending and margin trading." "Fulcrum is a decentralized margin trading platform. There is no need for any verification, KYC or AML." "It is the first and only completely trustless platform for margin; it does not use centralized price feeds or centrally administered margin calls. It is permissionless and rent free; there are no fees and no accounts. Fulcrum is built on the bZx base protocol and extends the protocol by allowing both loans and margin positions to be tokenized." "Enjoy a frictionless trading experience with positions that automatically renew and zero rollover fees."

"bZx has been heavily focused on solidifying strong industry partnerships with key players including but not limited to MakerDAO, Kyber, ChainLink, Augur and Set Protocol." "The bZx base protocol [was] audited by leading blockchain security auditor ZK Labs."

"when Fulcrum team released their own Flash Loans feature on the Ethereum Mainnet, and we happened to find a very critical vulnerability in it. We discovered that $2.5M of user funds from 3 pools could be stolen within a single transaction."

"All started on January 11, 2020, when Fulcrum team released their own Flash Loans feature on the Ethereum Mainnet, and we happened to find a very critical vulnerability in it. We discovered that $2.5M of user funds from 3 pools could be stolen within a single transaction. We prepared our own smart contract to perform a white-hat hack to protect user funds. Since the vulnerable smart contract was published less than 48h before we discovered the issue, there was a very high chance malicious attackers could exploit it, and we wanted to assure that this wouldn’t happen."

"At the very last moment, we decided to make proof of concept and transferred only 1 weiDAI (0.000000000000000001 DAI) in two separate transactions to make sure it’s true and give a chance to the Fulcrum team to shut-down their system (we had no idea if they have such functionality and had not enough time to check). This potentially would allow their system to avoid inconsistent state and recover without significant damage. We decided to spend up to half of an hour trying to reach the team by every accessible communication channel, and if we failed to reach them we were standing by to white-hack the funds and immediately disclose it to the DeFi community."

"We provided a link to the proof-of-hack transactions (first and second) in the hope that they would immediately stop their smart contract. We offered to the Fulcrum team to white-hack their pools at any moment to protect user funds if they had no kill-switch, but they declined. Apparently they thought it it was worth risking user funds during the period of building and queueing a patch in order to avoid integration issues and negative attention."

"It took nearly 4 hours for the Fulcrum team to manage the issue, and we got no details from the team about the progress. Additionally, the deployment of the fix took another 12 HOURS, because of special system upgrade timelock in the smart contract."

"Since we contacted the Fulcrum team and they denied us to white-hack, we were legally unable to help their users and were forced to wait and monitor their contracts for suspicious transactions and Approval events for 16 hours."

"Finally, the fix was deployed on mainnet. But this story wasn’t over yet. We genuinely feel ashamed that after working through an anxiety-filled night with them, they basically tried to deny us any bounty reward. Please note that it’s usually industry practice to share a percentage of funds saved, while here they are trying to deny us anything based on a technicality."

"After all this, it still got worse. Instead of disclosing the incident to the community as promised, the strategy was now to cover-up. They tried to use the $3.5k to silence us and hide the whole thing. The right thing would have been to share it with their users and community so they can decide whether they want to continue entrusting their money to code that the Fulcrum team released."

"We strongly feel that we need to come forward with this information, and honestly wish we had done so earlier. Making mistakes is ok, but denying the truth to users and the commnunity and therefore depriving them of their ability to make infomed decisions, especially when it comes to money, is unacceptable."

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 Fulcrum White Hack
!Date
!Event
!Description
|-
|January 11th, 2020 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 ==
No funds were lost in this case. An independent industry insurance fund would be able to publish reports, cover losses, and/or pay bounties in the best interests of the industry as a whole.

== References ==
[https://cryptosec.info/defi-hacks/ Comprehensive List of DeFi Hacks & Exploits - CryptoSec] (Jan 8)

[https://blog.1inch.io/yes-we-hacked-bzx-fulcrum-but-one-month-ago-3f7e5c437ee3 https://blog.1inch.io/yes-we-hacked-bzx-fulcrum-but-one-month-ago-3f7e5c437ee3] (Jan 9)

[https://medium.com/bzxnetwork/introducing-fulcrum-tokenized-margin-made-dead-simple-e65ccc82393f Introducing Fulcrum Tokenized Margin Made Dead Simple] (Jun 25)

[https://defirate.com/bzx/ Fulcrum Trade - bZx Decentralized Lending & Margin Trading] (Jun 25)

[https://decrypt.co/resources/bzx-ethereum-defi-decentralized-finance-explained-guide What is bZx? A 3-minute guide to the defi trading platform - Decrypt] (Jun 25)

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

[https://fulcrum.trade/ Crypto Margin Trading with Fulcrum | bZx] (Jun 25)

[https://etherscan.io/tx/0xa5611cdc8f0c9e90b89399eb81016cd6346206155d751ea318c6bb4ab129cdc3 Ethereum Transaction Hash (Txhash) Details | Etherscan] (Jan 9)

[https://etherscan.io/tx/0xc2e02ef9d45bd5ca645ad0c7a85425d1f75418de23cea1f996bd65c249194c3e Ethereum Transaction Hash (Txhash) Details | Etherscan] (Jan 9)