Uranium Finance Hack - Revision history

Azoundria at 23:48, 2 May 2023

2023-05-02T23:48:36Z

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

	[[File:Uraniumfinance.jpg\|thumb\|Uranium Finance]]The Uranium Finance smart contract upgraded their code base, modified in a way which added an exploit. Either this happened on purpose by one member of their team and wasn't noticed, or it happened by accident.		[[File:Uraniumfinance.jpg\|thumb\|Uranium Finance]]The Uranium Finance smart contract upgraded their code base, modified in a way which added an exploit. Either this happened on purpose by one member of their team and wasn't noticed, or it happened by accident.
Line 6:		Line 6:
	Given the history of having two hacks in the same month, and the nature of the code being modified to specifically add an exploit, it does seem more likely that one member of their team is involved. However, it is impossible to know for sure, and this is entirely speculation.		Given the history of having two hacks in the same month, and the nature of the code being modified to specifically add an exploit, it does seem more likely that one member of their team is involved. However, it is impossible to know for sure, and this is entirely speculation.

	This is a global/international case not involving a specific country.		This is a global/international case not involving a specific country.<ref name="halborn-522" /><ref name="cryptopotato-523" /><ref name="rekt-513" /><ref name="rekt-524" /><ref name="cryptobriefing-525" /><ref name="cryptonews-526" /><ref name="mycryptotwitter-527" /><ref name="uraniumfinancetwitter-528" /><ref name="bscdotnews-529" /><ref name="frankresearchertwitter-530" /><ref name="mickyaustralia-531" /><ref name="uraniumfinancemedium-532" /><ref name="slowmistmedium-533" /><ref name="cryptoslate-534" /><ref name="slowmisthacked-678" /><ref name="openblocksecgithub-2342" /><ref name="uraniumfinancemedium-2364" /><ref name="certik-1251" />
	<ref name="halborn-522" /><ref name="cryptopotato-523" /><ref name="rekt-513" /><ref name="rekt-524" /><ref name="cryptobriefing-525" /><ref name="cryptonews-526" /><ref name="mycryptotwitter-527" /><ref name="uraniumfinancetwitter-528" /><ref name="bscdotnews-529" /><ref name="frankresearchertwitter-530" /><ref name="mickyaustralia-531" /><ref name="uraniumfinancemedium-532" /><ref name="slowmistmedium-533" /><ref name="cryptoslate-534" /><ref name="slowmisthacked-678" /><ref name="openblocksecgithub-2342" /><ref name="uraniumfinancemedium-2364" /><ref name="certik-1251" />

	== About Uranium Finance ==		== About Uranium Finance ==
Line 61:		Line 60:
	!Description		!Description
	\|-		\|-
	\|April 24th, 2021 ~~12:00:00 AM~~		\|April 24th, 2021
	\|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 69:		Line 68:
	\|		\|
	\|}		\|}

			== 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 88:		Line 90:
	== 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 ==
	== Prevention Policies ==
	Decentralized smart contracts are essentially hot wallets. They have no ability to think critically like a human being would. If you asked a human being to perform the same transaction as had happened in this exploit, your probability of success would be almost none. If you had to ask a few people and get approval from all of them, the probability would be effectively zero.		Decentralized smart contracts are essentially hot wallets. They have no ability to think critically like a human being would. If you asked a human being to perform the same transaction as had happened in this exploit, your probability of success would be almost none. If you had to ask a few people and get approval from all of them, the probability would be effectively zero.

	For this reason, having fund withdrawals controlled by a multi-signature wallet, with funds stored properly offline, is more secure than a smart contract. In addition, if smart contract are used, it's best to have only the necessary funds accessible at once, have some additional checks in place on larger withdrawals, and potentially set up a fund which can be used to cover any issues.		For this reason, having fund withdrawals controlled by a multi-signature wallet, with funds stored properly offline, is more secure than a smart contract. In addition, if smart contract are used, it's best to have only the necessary funds accessible at once, have some additional checks in place on larger withdrawals, and potentially set up a fund which can be used to cover any issues.
			== 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 ==
	<references><ref name="halborn-522">[https://halborn.com/explained-the-uranium-finance-hack-april-2021/ Explained: The Uranium Finance Hack (April 2021) - Halborn] (May 10, 2021)</ref>		<references><ref name="halborn-522">[https://halborn.com/explained-the-uranium-finance-hack-april-2021/ Explained: The Uranium Finance Hack (April 2021) - Halborn] (May 11, 2021)</ref>

	<ref name="cryptopotato-523">[https://cryptopotato.com/50m-drained-from-uranium-finance-hack-or-rug-pull/ $50M Drained From Uranium Finance: Hack or Rug Pull?] (May 12, 2021)</ref>		<ref name="cryptopotato-523">[https://cryptopotato.com/50m-drained-from-uranium-finance-hack-or-rug-pull/ $50M Drained From Uranium Finance: Hack or Rug Pull?] (May 13, 2021)</ref>

	<ref name="rekt-513">[https://rekt.news/leaderboard/ Rekt - Leaderboard] (May 12, 2021)</ref>		<ref name="rekt-513">[https://rekt.news/leaderboard/ Rekt - Leaderboard] (May 13, 2021)</ref>

	<ref name="rekt-524">[https://rekt.news/uranium-rekt/ Rekt - Uranium Finance - REKT] (May 13, 2021)</ref>		<ref name="rekt-524">[https://rekt.news/uranium-rekt/ Rekt - Uranium Finance - REKT] (May 14, 2021)</ref>

	<ref name="cryptobriefing-525">[https://cryptobriefing.com/bsc-protocol-uranium-finance-hacked-50-million/ BSC Protocol Uranium Finance Hacked for $50 Million \| Crypto Briefing] (May 13, 2021)</ref>		<ref name="cryptobriefing-525">[https://cryptobriefing.com/bsc-protocol-uranium-finance-hacked-50-million/ BSC Protocol Uranium Finance Hacked for $50 Million \| Crypto Briefing] (May 14, 2021)</ref>

	<ref name="cryptonews-526">[https://cryptonews.com/news/uranium-finance-suffers-a-security-breach-millions-of-usd-on-10083.htm BSC-Based Uranium Finance Attacked, Millions on the Move] (May 14, 2021)</ref>		<ref name="cryptonews-526">[https://cryptonews.com/news/uranium-finance-suffers-a-security-breach-millions-of-usd-on-10083.htm BSC-Based Uranium Finance Attacked, Millions on the Move] (May 15, 2021)</ref>

	<ref name="mycryptotwitter-527">[https://twitter.com/MyCrypto/status/1387268992910323713 @MyCrypto Twitter] (May 14, 2021)</ref>		<ref name="mycryptotwitter-527">[https://twitter.com/MyCrypto/status/1387268992910323713 @MyCrypto Twitter] (May 15, 2021)</ref>

	<ref name="uraniumfinancetwitter-528">[https://twitter.com/UraniumFinance/status/1387245696454041600 @UraniumFinance Twitter] (May 14, 2021)</ref>		<ref name="uraniumfinancetwitter-528">[https://twitter.com/UraniumFinance/status/1387245696454041600 @UraniumFinance Twitter] (May 15, 2021)</ref>

	<ref name="bscdotnews-529">[https://www.bsc.news/post/uranium-finance-50m-hacked-or-stolen URANIUM FINANCE $50m HACKED or STOLEN?] (May 14, 2021)</ref>		<ref name="bscdotnews-529">[https://www.bsc.news/post/uranium-finance-50m-hacked-or-stolen URANIUM FINANCE $50m HACKED or STOLEN?] (May 15, 2021)</ref>

	<ref name="frankresearchertwitter-530">[https://twitter.com/FrankResearcher/status/1387347001172398086 @FrankResearcher Twitter] (May 14, 2021)</ref>		<ref name="frankresearchertwitter-530">[https://twitter.com/FrankResearcher/status/1387347001172398086 @FrankResearcher Twitter] (May 15, 2021)</ref>

	<ref name="mickyaustralia-531">[https://micky.com.au/hackers-steal-50-million-from-uranium-finance-during-token-migration/ Hackers steal $50 million from Uranium Finance during token migration - Micky News] (May 14, 2021)</ref>		<ref name="mickyaustralia-531">[https://micky.com.au/hackers-steal-50-million-from-uranium-finance-during-token-migration/ Hackers steal $50 million from Uranium Finance during token migration - Micky News] (May 15, 2021)</ref>

	<ref name="uraniumfinancemedium-532">[https://uraniumfinance.medium.com/uranium-post-mortem-v2-compensations-aac4b0706d7d Uranium Post Mortem V2 Compensations] (May 14, 2021)</ref>		<ref name="uraniumfinancemedium-532">[https://uraniumfinance.medium.com/uranium-post-mortem-v2-compensations-aac4b0706d7d Uranium Post Mortem V2 Compensations] (May 15, 2021)</ref>

	<ref name="slowmistmedium-533">[https://slowmist.medium.com/slowmist-analysis-of-uranium-finances-hacked-event-9c9d11af7b2b SlowMist Analysis of Uranium Finances Hacked Event] (May 14, 2021)</ref>		<ref name="slowmistmedium-533">[https://slowmist.medium.com/slowmist-analysis-of-uranium-finances-hacked-event-9c9d11af7b2b SlowMist Analysis of Uranium Finances Hacked Event] (May 15, 2021)</ref>

	<ref name="cryptoslate-534">[https://cryptoslate.com/the-most-recently-hacked-defi-project-couldnt-even-copy-and-paste-uniswap-and-sushiswaps-code/ The most recently hacked DeFi project couldn't even copy and paste Uniswap and Sushiswap's code \| CryptoSlate] (May 14, 2021)</ref>		<ref name="cryptoslate-534">[https://cryptoslate.com/the-most-recently-hacked-defi-project-couldnt-even-copy-and-paste-uniswap-and-sushiswaps-code/ The most recently hacked DeFi project couldn't even copy and paste Uniswap and Sushiswap's code \| CryptoSlate] (May 15, 2021)</ref>

	<ref name="slowmisthacked-678">[https://hacked.slowmist.io/en/?c=ETH%20DApp SlowMist Hacked - SlowMist Zone] (May 17, 2021)</ref>		<ref name="slowmisthacked-678">[https://hacked.slowmist.io/en/?c=ETH%20DApp SlowMist Hacked - SlowMist Zone] (May 18, 2021)</ref>

	<ref name="openblocksecgithub-2342">[https://github.com/openblocksec/blocksec-incidents/blob/main/defi/2021.md blocksec-incidents/2021.md at main · openblocksec/blocksec-incidents · GitHub] (Aug 10, 2021)</ref>		<ref name="openblocksecgithub-2342">[https://github.com/openblocksec/blocksec-incidents/blob/main/defi/2021.md blocksec-incidents/2021.md at main · openblocksec/blocksec-incidents · GitHub] (Aug 11, 2021)</ref>

	<ref name="uraniumfinancemedium-2364">[https://uraniumfinance.medium.com/exploit-d3a88921531c Exploit] (Aug 10, 2021)</ref>		<ref name="uraniumfinancemedium-2364">[https://uraniumfinance.medium.com/exploit-d3a88921531c Exploit] (Aug 11, 2021)</ref>

	<ref name="certik-1251">[https://www.certik.org/ CertiK Blockchain Security Leaderboard] (~~May 31~~, 2021)</ref></references>		<ref name="certik-1251">[https://www.certik.org/ CertiK Blockchain Security Leaderboard] (Jun 1, 2021)</ref></references>

Azoundria at 23:50, 18 February 2023

2023-02-18T23:50:49Z

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

	[[File:Uraniumfinance.jpg\|thumb\|Uranium Finance]]The Uranium Finance smart contract upgraded their code base, modified in a way which added an exploit. Either this happened on purpose by one member of their team and wasn't noticed, or it happened by accident.		[[File:Uraniumfinance.jpg\|thumb\|Uranium Finance]]The Uranium Finance smart contract upgraded their code base, modified in a way which added an exploit. Either this happened on purpose by one member of their team and wasn't noticed, or it happened by accident.
Line 6:		Line 7:

	This is a global/international case not involving a specific country.		This is a global/international case not involving a specific country.
			<ref name="halborn-522" /><ref name="cryptopotato-523" /><ref name="rekt-513" /><ref name="rekt-524" /><ref name="cryptobriefing-525" /><ref name="cryptonews-526" /><ref name="mycryptotwitter-527" /><ref name="uraniumfinancetwitter-528" /><ref name="bscdotnews-529" /><ref name="frankresearchertwitter-530" /><ref name="mickyaustralia-531" /><ref name="uraniumfinancemedium-532" /><ref name="slowmistmedium-533" /><ref name="cryptoslate-534" /><ref name="slowmisthacked-678" /><ref name="openblocksecgithub-2342" /><ref name="uraniumfinancemedium-2364" /><ref name="certik-1251" />

	== About Uranium Finance ==		== About Uranium Finance ==
Line 39:		Line 41:

	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 61:		Line 62:
	\|-		\|-
	\|April 24th, 2021 12:00:00 AM		\|April 24th, 2021 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 74:		Line 71:

	== Total Amount Lost ==		== Total Amount Lost ==
	The total amount lost ~~is unknown~~.		The total amount lost has been estimated at $57,200,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?		How much was lost and how was it calculated? If there are conflicting reports, which are accurate and where does the discrepancy lie?
Line 85:		Line 82:

	== 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 98:		Line 95:

	== References ==		== References ==
	[https://halborn.com/explained-the-uranium-finance-hack-april-2021/ Explained: The Uranium Finance Hack (April 2021) - Halborn] (May 10)		<references><ref name="halborn-522">[https://halborn.com/explained-the-uranium-finance-hack-april-2021/ Explained: The Uranium Finance Hack (April 2021) - Halborn] (May 10, 2021)</ref>

	[https://cryptopotato.com/50m-drained-from-uranium-finance-hack-or-rug-pull/ $50M Drained From Uranium Finance: Hack or Rug Pull?] (May 12)		<ref name="cryptopotato-523">[https://cryptopotato.com/50m-drained-from-uranium-finance-hack-or-rug-pull/ $50M Drained From Uranium Finance: Hack or Rug Pull?] (May 12, 2021)</ref>

	[https://rekt.news/leaderboard/ Rekt - Leaderboard] (May 12)		<ref name="rekt-513">[https://rekt.news/leaderboard/ Rekt - Leaderboard] (May 12, 2021)</ref>

	[https://rekt.news/uranium-rekt/ Rekt - Uranium Finance - REKT] (May 13)		<ref name="rekt-524">[https://rekt.news/uranium-rekt/ Rekt - Uranium Finance - REKT] (May 13, 2021)</ref>

	[https://cryptobriefing.com/bsc-protocol-uranium-finance-hacked-50-million/ BSC Protocol Uranium Finance Hacked for $50 Million \| Crypto Briefing] (May 13)		<ref name="cryptobriefing-525">[https://cryptobriefing.com/bsc-protocol-uranium-finance-hacked-50-million/ BSC Protocol Uranium Finance Hacked for $50 Million \| Crypto Briefing] (May 13, 2021)</ref>

	[https://cryptonews.com/news/uranium-finance-suffers-a-security-breach-millions-of-usd-on-10083.htm BSC-Based Uranium Finance Attacked, Millions on the Move] (May 14)		<ref name="cryptonews-526">[https://cryptonews.com/news/uranium-finance-suffers-a-security-breach-millions-of-usd-on-10083.htm BSC-Based Uranium Finance Attacked, Millions on the Move] (May 14, 2021)</ref>

	[https://twitter.com/MyCrypto/status/1387268992910323713 @MyCrypto Twitter] (May 14)		<ref name="mycryptotwitter-527">[https://twitter.com/MyCrypto/status/1387268992910323713 @MyCrypto Twitter] (May 14, 2021)</ref>

	[https://twitter.com/UraniumFinance/status/1387245696454041600 @UraniumFinance Twitter] (May 14)		<ref name="uraniumfinancetwitter-528">[https://twitter.com/UraniumFinance/status/1387245696454041600 @UraniumFinance Twitter] (May 14, 2021)</ref>

	[https://www.bsc.news/post/uranium-finance-50m-hacked-or-stolen URANIUM FINANCE $50m HACKED or STOLEN?] (May 14)		<ref name="bscdotnews-529">[https://www.bsc.news/post/uranium-finance-50m-hacked-or-stolen URANIUM FINANCE $50m HACKED or STOLEN?] (May 14, 2021)</ref>

	[https://twitter.com/FrankResearcher/status/1387347001172398086 @FrankResearcher Twitter] (May 14)		<ref name="frankresearchertwitter-530">[https://twitter.com/FrankResearcher/status/1387347001172398086 @FrankResearcher Twitter] (May 14, 2021)</ref>

	[https://micky.com.au/hackers-steal-50-million-from-uranium-finance-during-token-migration/ Hackers steal $50 million from Uranium Finance during token migration - Micky News] (May 14)		<ref name="mickyaustralia-531">[https://micky.com.au/hackers-steal-50-million-from-uranium-finance-during-token-migration/ Hackers steal $50 million from Uranium Finance during token migration - Micky News] (May 14, 2021)</ref>

	[https://uraniumfinance.medium.com/uranium-post-mortem-v2-compensations-aac4b0706d7d Uranium Post Mortem V2 Compensations] (May 14)		<ref name="uraniumfinancemedium-532">[https://uraniumfinance.medium.com/uranium-post-mortem-v2-compensations-aac4b0706d7d Uranium Post Mortem V2 Compensations] (May 14, 2021)</ref>

	[https://slowmist.medium.com/slowmist-analysis-of-uranium-finances-hacked-event-9c9d11af7b2b SlowMist Analysis of Uranium Finances Hacked Event] (May 14)		<ref name="slowmistmedium-533">[https://slowmist.medium.com/slowmist-analysis-of-uranium-finances-hacked-event-9c9d11af7b2b SlowMist Analysis of Uranium Finances Hacked Event] (May 14, 2021)</ref>

	[https://cryptoslate.com/the-most-recently-hacked-defi-project-couldnt-even-copy-and-paste-uniswap-and-sushiswaps-code/ The most recently hacked DeFi project couldn't even copy and paste Uniswap and Sushiswap's code \| CryptoSlate] (May 14)		<ref name="cryptoslate-534">[https://cryptoslate.com/the-most-recently-hacked-defi-project-couldnt-even-copy-and-paste-uniswap-and-sushiswaps-code/ The most recently hacked DeFi project couldn't even copy and paste Uniswap and Sushiswap's code \| CryptoSlate] (May 14, 2021)</ref>

	[https://hacked.slowmist.io/en/?c=ETH%20DApp SlowMist Hacked - SlowMist Zone] (May 17)		<ref name="slowmisthacked-678">[https://hacked.slowmist.io/en/?c=ETH%20DApp SlowMist Hacked - SlowMist Zone] (May 17, 2021)</ref>

	[https://github.com/openblocksec/blocksec-incidents/blob/main/defi/2021.md blocksec-incidents/2021.md at main · openblocksec/blocksec-incidents · GitHub] (Aug 10)		<ref name="openblocksecgithub-2342">[https://github.com/openblocksec/blocksec-incidents/blob/main/defi/2021.md blocksec-incidents/2021.md at main · openblocksec/blocksec-incidents · GitHub] (Aug 10, 2021)</ref>

	[https://uraniumfinance.medium.com/exploit-d3a88921531c Exploit] (Aug 10)		<ref name="uraniumfinancemedium-2364">[https://uraniumfinance.medium.com/exploit-d3a88921531c Exploit] (Aug 10, 2021)</ref>

	[https://www.certik.org/ CertiK Blockchain Security Leaderboard] (May 31)		<ref name="certik-1251">[https://www.certik.org/ CertiK Blockchain Security Leaderboard] (May 31, 2021)</ref></references>

Azoundria: Created page with "{{Imported Case Study|source=https://www.quadrigainitiative.com/casestudy/uraniumfinancehack.php}} Uranium FinanceThe Uranium Finance smart contract upgraded their code base, modified in a way which added an exploit. Either this happened on purpose by one member of their team and wasn't noticed, or it happened by accident. Given the history of having two hacks in the same month, and the nature of the code being modified to specifically..."

2023-01-26T05:42:18Z

Created page with "{{Imported Case Study|source=https://www.quadrigainitiative.com/casestudy/uraniumfinancehack.php}} thumb|Uranium FinanceThe Uranium Finance smart contract upgraded their code base, modified in a way which added an exploit. Either this happened on purpose by one member of their team and wasn't noticed, or it happened by accident. Given the history of having two hacks in the same month, and the nature of the code being modified to specifically..."

New page

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

[[File:Uraniumfinance.jpg|thumb|Uranium Finance]]The Uranium Finance smart contract upgraded their code base, modified in a way which added an exploit. Either this happened on purpose by one member of their team and wasn't noticed, or it happened by accident.

Given the history of having two hacks in the same month, and the nature of the code being modified to specifically add an exploit, it does seem more likely that one member of their team is involved. However, it is impossible to know for sure, and this is entirely speculation.

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

== About Uranium Finance ==
Uranium Finance is "The daily dividends AMM". They "believe the answer is to simply return the majority of the profits to [their] users : make them shareholders instead of only liquidity providers."

"According to The Block’s research analyst Igor Igamberdiev, pair contracts in Uranium’s V2 version had contained the bug which enabled the exploit. They did this by allowing anyone to interact with the pair contracts, which are smart contracts for trading pairs in an AMM and withdraw all of the tokens." "The BSC Uniswap clone played around too much with their copied code and left a loophole open for someone to take the funds." "[T]he V 2.0 code was exploited by an attacker who transferred $50 million away from the LP funds into a swapping platform and specific wallets. The exploiter swapped for BTC, ETH, and DOT coin." "What allegedly happened is hackers taking over the migration of Uranium’s liquidity provider (LP) tokens." "The attackers exploited a bug in Uranium Finance’s smart contract to swap a single token for almost all other tokens in the protocol’s liquidity pool."

"This problem occurred on the pair contract of the Uranium project. The swap function part of the contract logic refers to the logic of PancakeSwap, allowing users to lend out funds through flash loans. However, when this function checks the contract balance according to the constant product formula, there is a problem of accuracy processing errors, resulting in the balance calculated in the final contract being 100 times larger than the actual balance of the contract. In this case, if the attacker uses a flash loan to borrow , Only need to return 1% of the loan amount to pass the inspection and steal the remaining 99% of the balance, resulting in project losses."

"The perpetrators have reportedly employed the services of Tornado Cash – an Ethereum privacy instrument – to move 2,400 ETH (worth nearly $6 million). Etherscan shows that all transactions were made in batches of 100 ETH." "The beneficiary of this incident is now sat on $57.2 million of liquid assets." "The hacker used PancakeSwap service to swap DOT and ADA to ETH. The attacker withdrew 2,438 ETH via Anyswap to Ethereum and 80 BTC after that. After, $1 Million USDT and $99k DAI (bought with USDT) then went to xDAI." "The funds stolen include 80 Bitcoin (BTC), 1,800 Ethereum (ETH), 26,500 Polkadot (DOT), 5.7 million Tether (USDT), 638,000 Cardano (ADA) and 112,000 U92, the native coin of Uranium Finance."

"This attack is the second for the Uranium project this April, the first being the exploit of hackers in the platform’s pools to steal around $1.3 million worth of BUSD and BNB." "On the 8th April around 00:30 UTC, an exploiter was able to constantly grab the contents of the RADS pool and all of the RADS/sRADS rewards and sell them for $1.3Mil worth of BUSD and BNB. This drastically dumped the price of RADS and the exploiter then transferred the BUSD and BNB to his wallet."

"The team additionally said that they are in contact with Binance Security Team and "in the process of escalating this," adding to those in possession of the funds or those who know someone who is, to contact them "to arrange a deal before this goes higher.""

"Uranium migration has been exploited, the following address has 50m in it The only thing that matters is keeping the funds on BSC, everyone please start tweeting this address to Binance immediately asking them to stop transfers."

"The general feeling is that this may not be the case of a hack; rather, this may be a soft rugpull event done by the team to jeopardize users’ funds. While the community carries this sentiment it is impossible to know who the malicious user was." "And of course, these millions of dollars were peoples' hard earned money. There are real consequences to this game if you're not careful."

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 - Uranium Finance Hack
!Date
!Event
!Description
|-
|April 24th, 2021 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 ==
Decentralized smart contracts are essentially hot wallets. They have no ability to think critically like a human being would. If you asked a human being to perform the same transaction as had happened in this exploit, your probability of success would be almost none. If you had to ask a few people and get approval from all of them, the probability would be effectively zero.

For this reason, having fund withdrawals controlled by a multi-signature wallet, with funds stored properly offline, is more secure than a smart contract. In addition, if smart contract are used, it's best to have only the necessary funds accessible at once, have some additional checks in place on larger withdrawals, and potentially set up a fund which can be used to cover any issues.

== References ==
[https://halborn.com/explained-the-uranium-finance-hack-april-2021/ Explained: The Uranium Finance Hack (April 2021) - Halborn] (May 10)

[https://cryptopotato.com/50m-drained-from-uranium-finance-hack-or-rug-pull/ $50M Drained From Uranium Finance: Hack or Rug Pull?] (May 12)

[https://rekt.news/leaderboard/ Rekt - Leaderboard] (May 12)

[https://rekt.news/uranium-rekt/ Rekt - Uranium Finance - REKT] (May 13)

[https://cryptobriefing.com/bsc-protocol-uranium-finance-hacked-50-million/ BSC Protocol Uranium Finance Hacked for $50 Million | Crypto Briefing] (May 13)

[https://cryptonews.com/news/uranium-finance-suffers-a-security-breach-millions-of-usd-on-10083.htm BSC-Based Uranium Finance Attacked, Millions on the Move] (May 14)

[https://twitter.com/MyCrypto/status/1387268992910323713 @MyCrypto Twitter] (May 14)

[https://twitter.com/UraniumFinance/status/1387245696454041600 @UraniumFinance Twitter] (May 14)

[https://www.bsc.news/post/uranium-finance-50m-hacked-or-stolen URANIUM FINANCE $50m HACKED or STOLEN?] (May 14)

[https://twitter.com/FrankResearcher/status/1387347001172398086 @FrankResearcher Twitter] (May 14)

[https://micky.com.au/hackers-steal-50-million-from-uranium-finance-during-token-migration/ Hackers steal $50 million from Uranium Finance during token migration - Micky News] (May 14)

[https://uraniumfinance.medium.com/uranium-post-mortem-v2-compensations-aac4b0706d7d Uranium Post Mortem V2 Compensations] (May 14)

[https://slowmist.medium.com/slowmist-analysis-of-uranium-finances-hacked-event-9c9d11af7b2b SlowMist Analysis of Uranium Finances Hacked Event] (May 14)

[https://cryptoslate.com/the-most-recently-hacked-defi-project-couldnt-even-copy-and-paste-uniswap-and-sushiswaps-code/ The most recently hacked DeFi project couldn't even copy and paste Uniswap and Sushiswap's code | CryptoSlate] (May 14)

[https://hacked.slowmist.io/en/?c=ETH%20DApp SlowMist Hacked - SlowMist Zone] (May 17)

[https://github.com/openblocksec/blocksec-incidents/blob/main/defi/2021.md blocksec-incidents/2021.md at main · openblocksec/blocksec-incidents · GitHub] (Aug 10)

[https://uraniumfinance.medium.com/exploit-d3a88921531c Exploit] (Aug 10)

[https://www.certik.org/ CertiK Blockchain Security Leaderboard] (May 31)