Hedera Token Service Exploited - Revision history

Azoundria: COMPLETE Another 30 minutes. We already had this thread in the wiki with an earlier date, however we added an archived version since the post had been deleted. Filled in a fairly extensive about section introduction and improved the sources there. Removing all placeholder/stub text throughout other sections and filled in with some content. Integrated DefiIgnas technical analysis into the larger post.

2024-02-01T20:27:37Z

COMPLETE Another 30 minutes. We already had this thread in the wiki with an earlier date, however we added an archived version since the post had been deleted. Filled in a fairly extensive about section introduction and improved the sources there. Removing all placeholder/stub text throughout other sections and filled in with some content. Integrated DefiIgnas technical analysis into the larger post.

Show changes

Azoundria: -------2441-------- COMPLETE 30 Minutes. Integrated the HBAR Hedera Reddit post. Added more information surrounding several tweets from Pangolin including about the delays in reimbursement. Cleaning up ongoing developments and about sections.

2024-01-17T20:57:59Z

-------2441-------- COMPLETE 30 Minutes. Integrated the HBAR Hedera Reddit post. Added more information surrounding several tweets from Pangolin including about the delays in reimbursement. Cleaning up ongoing developments and about sections.

Show changes

Azoundria: Another 30 minutes complete.

2023-05-30T22:53:54Z

Another 30 minutes complete.

@@ Line 149: / Line 149: @@
 |Rekt Article Published
 |Blockchain researchers at Rekt publish an article on the situation<ref name="rekthqtwitter-10834" />.
 |}
@@ Line 233: / Line 245: @@
 == 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.
+All Pangolin Hedera funds were restored<ref name=":1" /><ref name=":2" />.
 What funds were recovered? What funds were reimbursed for those affected users?
@@ Line 242: / Line 290: @@
 What parts of this case are still remaining to be concluded?
 == Individual Prevention Policies ==
-{{Prevention:Individuals:Placeholder}}
+{{Prevention:Individual:Avoid Using Smart Contracts}}
 {{Prevention:Individuals:End}}
 == Platform Prevention Policies ==
-No funds were lost in this case, as the vulnerability was never exploited. Further scrutiny by platforms using the EOS blockchain may have helped to uncover the vulnerability before it was exploited. It is also important to place more assets, particularly key treasury assets, within a simpler multi-signature arrangement, which would typically have a lot less risk than more complex smart contracts.
+Further scrutiny by platforms may have helped to uncover the vulnerability before it was exploited. It is also important to place more assets, particularly key treasury assets, within a simpler multi-signature arrangement, which would typically have a lot less risk than more complex smart contracts.
 {{Prevention:Platforms:Regular Audit Procedures}}

Azoundria: Update

2023-05-30T21:28:47Z

Update

← Older revision		Revision as of 15:28, 30 May 2023
Line 247:		Line 247:

	== Platform Prevention Policies ==		== Platform Prevention Policies ==
	{{Prevention:Platforms:~~Placeholder~~}}		No funds were lost in this case, as the vulnerability was never exploited. Further scrutiny by platforms using the EOS blockchain may have helped to uncover the vulnerability before it was exploited. It is also important to place more assets, particularly key treasury assets, within a simpler multi-signature arrangement, which would typically have a lot less risk than more complex smart contracts.

			{{Prevention:Platforms:Regular Audit Procedures}}

			{{Prevention:Platform:Implement Multi-Signature}}

	{{Prevention:Platforms:End}}		{{Prevention:Platforms:End}}

	== Regulatory Prevention Policies ==		== Regulatory Prevention Policies ==
	{{Prevention:Regulators:~~Placeholder~~}}		{{Prevention:Regulators:Blockchain Level Exploit Handling}}

			{{Prevention:Regulators:Establish Industry Insurance Fund}}

	{{Prevention:Regulators:End}}		{{Prevention:Regulators:End}}

Azoundria: Completed 30 minutes. All sources integrated.

2023-05-18T22:15:22Z

Completed 30 minutes. All sources integrated.

Show changes

Azoundria: Initial 30 minutes.

2023-05-04T00:44:11Z

Initial 30 minutes.

← Older revision		Revision as of 18:44, 3 May 2023
Line 4:		Line 4:
	[[File:Hederablockchain.jpg\|thumb\|Hedera Blockchain]]Hedera Hashgraph is a decentralized, open-source, proof-of-stake public ledger that utilizes the leaderless, asynchronous Byzantine Fault Tolerance (aBFT) hashgraph consensus algorithm. It is governed by a decentralized council of leading enterprises, universities, and web3 projects from around the world. Hedera's performance-optimized Ethereum Virtual Machine (EVM) smart contracts, along with its easy-to-use native tokenization and consensus service APIs, enable developers to create real-time web3 applications and ecosystems that will drive the future of the internet. Unfortunately, there was an ongoing exploit that hit the Hedera network, which is targeting the decompiling process in smart contracts. At the time of writing, attackers have hit Pangolin and HeliSwap pools containing wrapped assets. Hedera has turned off network proxies on mainnet, effectively making it inaccessible, but "Hedera core" continues to work through the smart contract irregularity. The lack of certainty caused chaos, and what turned out to be around $515k stolen by the attacker turned into $12M of damage to the ecosystem.		[[File:Hederablockchain.jpg\|thumb\|Hedera Blockchain]]Hedera Hashgraph is a decentralized, open-source, proof-of-stake public ledger that utilizes the leaderless, asynchronous Byzantine Fault Tolerance (aBFT) hashgraph consensus algorithm. It is governed by a decentralized council of leading enterprises, universities, and web3 projects from around the world. Hedera's performance-optimized Ethereum Virtual Machine (EVM) smart contracts, along with its easy-to-use native tokenization and consensus service APIs, enable developers to create real-time web3 applications and ecosystems that will drive the future of the internet. Unfortunately, there was an ongoing exploit that hit the Hedera network, which is targeting the decompiling process in smart contracts. At the time of writing, attackers have hit Pangolin and HeliSwap pools containing wrapped assets. Hedera has turned off network proxies on mainnet, effectively making it inaccessible, but "Hedera core" continues to work through the smart contract irregularity. The lack of certainty caused chaos, and what turned out to be around $515k stolen by the attacker turned into $12M of damage to the ecosystem.

	This is a global/international case not involving a specific country.<ref name="hashscan-10825" /><ref name="defiignastwitter-10826" /><ref name="pangolinhederatwitter-10827" /><ref name="hederatwitter-10828" /><ref name="hederatwitter-10829" /><ref name="hederatwitter-10830~~" /><ref name="hederatwitter-10831~~" /><ref name="defillama-10832" /><ref name="etherscan-10833" /><ref name="rekthqtwitter-10834~~" /><ref name="hedera-10835" /><ref name="prnewswire-10836~~" /><ref name="unnamed-10837" />		This is a global/international case not involving a specific country.<ref name="hashscan-10825" /><ref name="defiignastwitter-10826" /><ref name="pangolinhederatwitter-10827" /><ref name="hederatwitter-10828" /><ref name="hederatwitter-10829" /><ref name="hederatwitter-10830" /><ref name="defillama-10832" /><ref name="etherscan-10833" /><ref name="rekthqtwitter-10834" /><ref name="unnamed-10837" />

	== About Hedera Blockchain ==		== About Hedera Blockchain ==
			<ref name="hedera-10835" /><ref name="prnewswire-10836" />

	"Powering native web3 ecosystems and institutional applications for the next generation of the web"		"Powering native web3 ecosystems and institutional applications for the next generation of the web"

Line 57:		Line 59:
	Attacker targeted liquidity pools on multiple DEXs that forked and ported Uniswap v2 to Hedera Token Service."		Attacker targeted liquidity pools on multiple DEXs that forked and ported Uniswap v2 to Hedera Token Service."

	~~"Today, attackers exploited the Smart Contract Service code of the Hedera mainnet to transfer Hedera Token Service tokens held by victims’ accounts to their own account. (1/6)~~

	The attacker targeted accounts used as liquidity pools on multiple DEXs that use Uniswap v2-derived contract code ported over to use the Hedera Token Service, including @Pangolin_Hedera, @SaucerSwapLabs, and @HeliSwap_DEX. (2/6)

	~~When the attackers moved tokens obtained through these attacks over the @HashportNetwork bridge, the bridge operators detected the activity and took swift action to disable it. (3/6)~~

	~~The Hedera community, including @swirldslabs, @HBAR_foundation, @LimeChainHQ, @Pangolin_Hedera, @SaucerSwapLabs, and @HeliSwap_DEX teams worked together to investigate the attack. (4/6)~~

	To prevent the attacker from being able to steal more tokens, Hedera turned off mainnet proxies, which removed user access to the mainnet. The team has identified the root cause of the issue and are working on a solution. (5/6)

	Once the solution is ready, Hedera Council members will sign transactions to approve the deployment of updated code on mainnet to remove this vulnerability, at which point the mainnet proxies will be turned back on, allowing normal activity to resume. (6/6)"

	"The lack of certainty caused chaos, and what turned out to be around $515k stolen by the attacker, turned into $12M of damage to the ecosystem."		"The lack of certainty caused chaos, and what turned out to be around $515k stolen by the attacker, turned into $12M of damage to the ecosystem."
Line 119:		Line 110:
	\|Funds Bridged To Ethereum		\|Funds Bridged To Ethereum
	\|The first batch of funds are bridged to Ethereum by the attacker.		\|The first batch of funds are bridged to Ethereum by the attacker.
			\|-
			\|March 9th, 2023 9:55:00 PM MST
			\|Hedera Announces Explanation
			\|Hedera posts an announcement about the exploit<ref name="hederatwitter-10831" />.
	\|}		\|}

Line 131:		Line 126:
	== Immediate Reactions ==		== 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?		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?

			=== Hedera Twitter PostMortem ===
			<ref name="hederatwitter-10831" /><blockquote>"Today, attackers exploited the Smart Contract Service code of the Hedera mainnet to transfer Hedera Token Service tokens held by victims’ accounts to their own account. (1/6)

			The attacker targeted accounts used as liquidity pools on multiple DEXs that use Uniswap v2-derived contract code ported over to use the Hedera Token Service, including @Pangolin_Hedera, @SaucerSwapLabs, and @HeliSwap_DEX. (2/6)

			When the attackers moved tokens obtained through these attacks over the @HashportNetwork bridge, the bridge operators detected the activity and took swift action to disable it. (3/6)

			The Hedera community, including @swirldslabs, @HBAR_foundation, @LimeChainHQ, @Pangolin_Hedera, @SaucerSwapLabs, and @HeliSwap_DEX teams worked together to investigate the attack. (4/6)

			To prevent the attacker from being able to steal more tokens, Hedera turned off mainnet proxies, which removed user access to the mainnet. The team has identified the root cause of the issue and are working on a solution. (5/6)

			Once the solution is ready, Hedera Council members will sign transactions to approve the deployment of updated code on mainnet to remove this vulnerability, at which point the mainnet proxies will be turned back on, allowing normal activity to resume. (6/6)"</blockquote>

	== Ultimate Outcome ==		== Ultimate Outcome ==
Line 158:		Line 166:

	== References ==		== References ==
	<references><ref name="hashscan-10825">[https://hashscan.io/mainnet/transaction/1678211946.831147990?tid=0.0.1030878-1678211935-103568959 ~~https://hashscan.io/mainnet/transaction/1678211946.831147990?tid=0.0.1030878-1678211935-103568959]~~ (May 3, 2023)</ref>		<references>
			<ref name="hashscan-10825">https://hashscan.io/mainnet/transaction/1678211946.831147990?tid=0.0.1030878-1678211935-103568959 (May 3, 2023)</ref>
	<ref name="defiignastwitter-10826">[https://twitter.com/DefiIgnas/status/1633821155231674375 @DefiIgnas Twitter] (May 3, 2023)</ref>		<ref name="defiignastwitter-10826">[https://twitter.com/DefiIgnas/status/1633821155231674375 @DefiIgnas Twitter] (May 3, 2023)</ref>

	<ref name="pangolinhederatwitter-10827">[https://twitter.com/Pangolin_Hedera/status/1633771791415132162 @Pangolin_Hedera Twitter] (May 3, 2023)</ref>		<ref name="pangolinhederatwitter-10827">[https://twitter.com/Pangolin_Hedera/status/1633771791415132162 @Pangolin_Hedera Twitter] (May 3, 2023)</ref>

	<ref name="hederatwitter-10828">[https://twitter.com/hedera/status/1633925272830623746 @hedera Twitter] (May 3, 2023)</ref>		<ref name="hederatwitter-10828">[https://twitter.com/hedera/status/1633925272830623746 @hedera Twitter] (May 3, 2023)</ref>

	<ref name="hederatwitter-10829">[https://twitter.com/hedera/status/1633928291555119104 @hedera Twitter] (May 3, 2023)</ref>		<ref name="hederatwitter-10829">[https://twitter.com/hedera/status/1633928291555119104 @hedera Twitter] (May 3, 2023)</ref>

	<ref name="hederatwitter-10830">[https://twitter.com/hedera/status/1633928878698930177 @hedera Twitter] (May 3, 2023)</ref>		<ref name="hederatwitter-10830">[https://twitter.com/hedera/status/1633928878698930177 @hedera Twitter] (May 3, 2023)</ref>
			<ref name="hederatwitter-10831">[https://twitter.com/hedera/status/1634055353435561986 hedera - "Today, attackers exploited the Smart Contract Service code of the Hedera mainnet to transfer Hedera Token Service tokens held by victims’ accounts to their own account." - Twitter] (May 3, 2023)</ref>
	<ref name="hederatwitter-10831">[https://twitter.com/hedera/status/1634055353435561986 @hedera Twitter] (May 3, 2023)</ref>

	<ref name="defillama-10832">[https://defillama.com/chain/Hedera Hedera TVL - DefiLlama] (May 3, 2023)</ref>		<ref name="defillama-10832">[https://defillama.com/chain/Hedera Hedera TVL - DefiLlama] (May 3, 2023)</ref>

	<ref name="etherscan-10833">[https://etherscan.io/address/0x2fd2a8d39fd7c4751fea109a86fa4cdd989e6ad3 Address 0x2fd2a8d39fd7c4751fea109a86fa4cdd989e6ad3 \| Etherscan] (May 3, 2023)</ref>		<ref name="etherscan-10833">[https://etherscan.io/address/0x2fd2a8d39fd7c4751fea109a86fa4cdd989e6ad3 Address 0x2fd2a8d39fd7c4751fea109a86fa4cdd989e6ad3 \| Etherscan] (May 3, 2023)</ref>

	<ref name="rekthqtwitter-10834">[https://twitter.com/RektHQ/status/1634260194648530953 @RektHQ Twitter] (May 3, 2023)</ref>		<ref name="rekthqtwitter-10834">[https://twitter.com/RektHQ/status/1634260194648530953 @RektHQ Twitter] (May 3, 2023)</ref>

	<ref name="hedera-10835">[https://hedera.com/ Hello future \| Hedera] (May 3, 2023)</ref>		<ref name="hedera-10835">[https://hedera.com/ Hello future \| Hedera] (May 3, 2023)</ref>

	<ref name="prnewswire-10836">[https://www.prnewswire.com/news-releases/swiss-hashgraph-association-launches-the-hashgraph-innovation-program-to-accelerate-adoption-of-the-hedera-network-worldwide-301529011.html "Swiss Hashgraph Association" Launches the "Hashgraph Innovation Program" to Accelerate Adoption of the Hedera Network Worldwide] (May 3, 2023)</ref>		<ref name="prnewswire-10836">[https://www.prnewswire.com/news-releases/swiss-hashgraph-association-launches-the-hashgraph-innovation-program-to-accelerate-adoption-of-the-hedera-network-worldwide-301529011.html "Swiss Hashgraph Association" Launches the "Hashgraph Innovation Program" to Accelerate Adoption of the Hedera Network Worldwide] (May 3, 2023)</ref>
			<ref name="unnamed-10837">https://hashscan.io/mainnet/account/0.0.2015717 (May 3, 2023)</ref>
	<ref name="unnamed-10837">[https://hashscan.io/mainnet/account/0.0.2015717 ~~https://hashscan.io/mainnet/account/0.0.2015717]~~ (May 3, 2023)</ref></references>		</references>

Azoundria: Created page with "{{Imported Case Study|source=https://www.quadrigainitiative.com/casestudy/hederatokenserviceexploited.php}} {{Unattributed Sources}} Hedera BlockchainHedera Hashgraph is a decentralized, open-source, proof-of-stake public ledger that utilizes the leaderless, asynchronous Byzantine Fault Tolerance (aBFT) hashgraph consensus algorithm. It is governed by a decentralized council of leading enterprises, universities, and web3 projects from..."

2023-05-04T00:39:02Z

Created page with "{{Imported Case Study|source=https://www.quadrigainitiative.com/casestudy/hederatokenserviceexploited.php}} {{Unattributed Sources}} thumb|Hedera BlockchainHedera Hashgraph is a decentralized, open-source, proof-of-stake public ledger that utilizes the leaderless, asynchronous Byzantine Fault Tolerance (aBFT) hashgraph consensus algorithm. It is governed by a decentralized council of leading enterprises, universities, and web3 projects from..."

New page

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

[[File:Hederablockchain.jpg|thumb|Hedera Blockchain]]Hedera Hashgraph is a decentralized, open-source, proof-of-stake public ledger that utilizes the leaderless, asynchronous Byzantine Fault Tolerance (aBFT) hashgraph consensus algorithm. It is governed by a decentralized council of leading enterprises, universities, and web3 projects from around the world. Hedera's performance-optimized Ethereum Virtual Machine (EVM) smart contracts, along with its easy-to-use native tokenization and consensus service APIs, enable developers to create real-time web3 applications and ecosystems that will drive the future of the internet. Unfortunately, there was an ongoing exploit that hit the Hedera network, which is targeting the decompiling process in smart contracts. At the time of writing, attackers have hit Pangolin and HeliSwap pools containing wrapped assets. Hedera has turned off network proxies on mainnet, effectively making it inaccessible, but "Hedera core" continues to work through the smart contract irregularity. The lack of certainty caused chaos, and what turned out to be around $515k stolen by the attacker turned into $12M of damage to the ecosystem.

This is a global/international case not involving a specific country.<ref name="hashscan-10825" /><ref name="defiignastwitter-10826" /><ref name="pangolinhederatwitter-10827" /><ref name="hederatwitter-10828" /><ref name="hederatwitter-10829" /><ref name="hederatwitter-10830" /><ref name="hederatwitter-10831" /><ref name="defillama-10832" /><ref name="etherscan-10833" /><ref name="rekthqtwitter-10834" /><ref name="hedera-10835" /><ref name="prnewswire-10836" /><ref name="unnamed-10837" />

== About Hedera Blockchain ==
"Powering native web3 ecosystems and institutional applications for the next generation of the web"

"An open source, public network governed by leading organizations around the world The Hedera Governing Council is a decentralized and transparent governing body of independent, global organizations consisting of enterprises, web3 projects, and prestigious universities."

"The Hedera codebase and ecosystem standards are open source and contributed by the community through Hedera Improvement Proposals (HIPs). The community consists of Hedera application and ecosystem developers, node operators, and peripheral organizations."

"Hedera is a decentralized, open-source, proof-of-stake public ledger that utilizes the leaderless, asynchronous Byzantine Fault Tolerance (aBFT) hashgraph consensus algorithm. It is governed by a collusion-resistant, decentralized council of leading enterprises, universities, and web3 projects from around the world.

Hedera’s performance-optimized Ethereum Virtual Machine (EVM) smart contracts, along with its easy-to-use native tokenization and consensus service APIs, enable developers to create real-time web3 applications and ecosystems that will drive the future of the internet.

Hedera is built differently from other blockchains. It has high throughput with fast finality; low, predictable fees; fair transaction ordering with consensus timestamps; and a robust codebase that ensures scalability and reliability at every layer of its network infrastructure. Hedera is governed responsibly by the world’s leading organizations to ensure that the network is collusion-resistant."

"HTS was audited by FP Complete in 2021."

"An ongoing exploit have hit the Hedera network this morning.

The exploit is targeting the decompiling process in smart contracts.

At time of writing attackers have hit Pangolin and HeliSwap pools containing wrapped assets."

"we'd encourage anyone with HTS tokens in Pangolin Pools and Farms to withdraw immediately."

"We’ve noticed network irregularities that are impacting various Hedera dApps and their users.

The Foundation is in communication with impacted partners. We’re monitoring and working to help resolve the issue.

Please standby for more information."

"Due to some Hedera network irregularities, Hashport has paused their bridge, and we'd encourage anyone with HTS tokens in Pangolin Pools and Farms to withdraw immediately."

"Hedera turned off network proxies on mainnet, effectively making it inaccessible.

But 'Hedera core' continues to work through the smart contract irregularity."

"In an abundance of caution & safety for users, @Hedera is turning off network proxies on mainnet, making it inaccessible. @Hedera core is working through the smart contract irregularities & will re-enable proxies once resolved."

"In an abundance of caution for users, @hedera network services will not be accessible during this period of time. This includes wallets, decentralized & centralized exchanges, decentralized applications, etc."

"Staking rewards will continue to accrue during this time — however, you'll only be able to receive those accrued rewards once the network becomes accessible again."

"Fear, rumour and suspicion took hold as both users and devs attempted to make sense of the chaos.

The “proof-of-stake public ledger”, built on blockchain-alternative Hashgraph, saw its TVL plunge by a third since the attack, from $36.8M to $24.6M.

The HBAR Foundation announced “network irregularities” and, given the widespread nature of the attack, users frantically sought a safe haven for their funds."

"The team has identified the root cause of the issue and is working on a solution.

Attacker targeted liquidity pools on multiple DEXs that forked and ported Uniswap v2 to Hedera Token Service."

"Today, attackers exploited the Smart Contract Service code of the Hedera mainnet to transfer Hedera Token Service tokens held by victims’ accounts to their own account. (1/6)

The attacker targeted accounts used as liquidity pools on multiple DEXs that use Uniswap v2-derived contract code ported over to use the Hedera Token Service, including @Pangolin_Hedera, @SaucerSwapLabs, and @HeliSwap_DEX. (2/6)

When the attackers moved tokens obtained through these attacks over the @HashportNetwork bridge, the bridge operators detected the activity and took swift action to disable it. (3/6)

The Hedera community, including @swirldslabs, @HBAR_foundation, @LimeChainHQ, @Pangolin_Hedera, @SaucerSwapLabs, and @HeliSwap_DEX teams worked together to investigate the attack. (4/6)

To prevent the attacker from being able to steal more tokens, Hedera turned off mainnet proxies, which removed user access to the mainnet. The team has identified the root cause of the issue and are working on a solution. (5/6)

Once the solution is ready, Hedera Council members will sign transactions to approve the deployment of updated code on mainnet to remove this vulnerability, at which point the mainnet proxies will be turned back on, allowing normal activity to resume. (6/6)"

"The lack of certainty caused chaos, and what turned out to be around $515k stolen by the attacker, turned into $12M of damage to the ecosystem."

"In a Twitter thread, Hedera explained that “The attacker targeted accounts used as liquidity pools on multiple DEXs that use Uniswap v2-derived contract code ported over to use the Hedera Token Service”."

"The head of Pangolin published a preliminary writeup which states the teams believed that the exploit was “only affecting Hashport tokens. This proved to be false. Further investigation revealed all hts [Hedera Token Service] tokens were at risk”.

This allowed the attacker to burn bridged/wrapped tokens, as well as remove LP positions from the affected DEXs. According to the report, some funds were bridged back to ETH, after the Hashport team deactivated the bridge, the attacker turned to CEXs."

"The report puts losses from Pangolin at $120k. HeliSwap lost just $2K, according to their rundown of events.

The attacker’s alleged addresses contain a total of around $515k; ~$60k of HBAR and $280k of HTS stablecoins on Hedera, and $175k of ETH on Ethereum."

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 - Hedera Token Service Exploited
!Date
!Event
!Description
|-
|March 9th, 2023 3:02:11 AM MST
|Funds Bridged To Ethereum
|The first batch of funds are bridged to Ethereum by the attacker.
|}

== 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 $515,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="hashscan-10825">[https://hashscan.io/mainnet/transaction/1678211946.831147990?tid=0.0.1030878-1678211935-103568959 https://hashscan.io/mainnet/transaction/1678211946.831147990?tid=0.0.1030878-1678211935-103568959] (May 3, 2023)</ref>

<ref name="defiignastwitter-10826">[https://twitter.com/DefiIgnas/status/1633821155231674375 @DefiIgnas Twitter] (May 3, 2023)</ref>

<ref name="pangolinhederatwitter-10827">[https://twitter.com/Pangolin_Hedera/status/1633771791415132162 @Pangolin_Hedera Twitter] (May 3, 2023)</ref>

<ref name="hederatwitter-10828">[https://twitter.com/hedera/status/1633925272830623746 @hedera Twitter] (May 3, 2023)</ref>

<ref name="hederatwitter-10829">[https://twitter.com/hedera/status/1633928291555119104 @hedera Twitter] (May 3, 2023)</ref>

<ref name="hederatwitter-10830">[https://twitter.com/hedera/status/1633928878698930177 @hedera Twitter] (May 3, 2023)</ref>

<ref name="hederatwitter-10831">[https://twitter.com/hedera/status/1634055353435561986 @hedera Twitter] (May 3, 2023)</ref>

<ref name="defillama-10832">[https://defillama.com/chain/Hedera Hedera TVL - DefiLlama] (May 3, 2023)</ref>

<ref name="etherscan-10833">[https://etherscan.io/address/0x2fd2a8d39fd7c4751fea109a86fa4cdd989e6ad3 Address 0x2fd2a8d39fd7c4751fea109a86fa4cdd989e6ad3 | Etherscan] (May 3, 2023)</ref>

<ref name="rekthqtwitter-10834">[https://twitter.com/RektHQ/status/1634260194648530953 @RektHQ Twitter] (May 3, 2023)</ref>

<ref name="hedera-10835">[https://hedera.com/ Hello future | Hedera] (May 3, 2023)</ref>

<ref name="prnewswire-10836">[https://www.prnewswire.com/news-releases/swiss-hashgraph-association-launches-the-hashgraph-innovation-program-to-accelerate-adoption-of-the-hedera-network-worldwide-301529011.html "Swiss Hashgraph Association" Launches the "Hashgraph Innovation Program" to Accelerate Adoption of the Hedera Network Worldwide] (May 3, 2023)</ref>

<ref name="unnamed-10837">[https://hashscan.io/mainnet/account/0.0.2015717 https://hashscan.io/mainnet/account/0.0.2015717] (May 3, 2023)</ref></references>