Azoundria: Created page with "{{Imported Case Study|source=https://www.quadrigainitiative.com/casestudy/ethereansoswhitehatrugpull.php}} {{Unattributed Sources}} Etherean's OSThe Items v2 protocol discovered a critical bug that could have been exploited by a malicious actor to create an infinite supply of $OS tokens, which could then have been dumped into open OS pools. To prevent this, the protocol team conducted what they called a "White Hat Rug Pull." They used the..."

2023-09-15T19:27:01Z

Created page with "{{Imported Case Study|source=https://www.quadrigainitiative.com/casestudy/ethereansoswhitehatrugpull.php}} {{Unattributed Sources}} thumb|Etherean's OSThe Items v2 protocol discovered a critical bug that could have been exploited by a malicious actor to create an infinite supply of $OS tokens, which could then have been dumped into open OS pools. To prevent this, the protocol team conducted what they called a "White Hat Rug Pull." They used the..."

New page

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

[[File:Ethereansos.jpg|thumb|Etherean's OS]]The Items v2 protocol discovered a critical bug that could have been exploited by a malicious actor to create an infinite supply of $OS tokens, which could then have been dumped into open OS pools. To prevent this, the protocol team conducted what they called a "White Hat Rug Pull." They used the exploit to mint enough $OS tokens and sold them for all the ETH and USDC in the affected pools. They then worked to return these funds to the rightful owners at no loss.

This is a global/international case not involving a specific country.<ref name="ethereansosmedium-11664" /><ref name="ethereansosmedium-11665" /><ref name="ethereansosmedium-11666" /><ref name="ethereansos-11667" /><ref name="ethereansos-11668" /><ref name="facebook-11669" /><ref name="facebook-11670" /><ref name="ethosdocs-11671" />

== About EthereansOS ==
"EthereansOS provides features that allow anyone to easily create DeFi products, sophisticated token standards, and 100% on-chain organizations. While also providing a straightforward way for developers to monetize and token holders to profit."

"Everything is set up to make the accessibility and performance of building in web3 seamless and is dedicated to ensuring the core principles of the blockchain (decentralization, scalability, and security) are kept at the core of every application built within its framework."

The Items v2 protocol discovered a critical bug that could have been exploited by a malicious actor to create an infinite supply of $OS tokens, which could then have been dumped into open OS pools. To prevent this, the protocol team conducted what they called a "White Hat Rug Pull." They used the exploit to mint enough $OS tokens and sold them for all the ETH and USDC in the affected pools. They then worked to return these funds to the rightful owners at no loss.

Users who had assets in these pools at block 13506003 can now claim their ETH and USDC back. Additionally, those with $OS and ETH staked in the Covenants farm will receive a bonus of 0.15 ETH when claiming. A new iteration of the Items v2 protocol was deployed, and users can claim their new $OS tokens based on the amount they held at the time of the snapshot.

This incident allowed the protocol to make some upgrades, including better decimals management and more granular governance of collections by hosts. Despite the hack, the team maintains that their roadmap is on track, and E-Day is not delayed.

The new $OS contract address is 0x6100dd79fCAA88420750DceE3F735d168aBcB771, and its name is "Ethereans (OS)." They are working on updating various platforms and wallets with this information. The compensation for gas fees is sourced from the EthOS public treasury and the NERV treasury.

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 - EthereansOS White Hat Rug Pull
!Date
!Event
!Description
|-
|December 9th, 2021 7:13:38 PM MST
|Medium Post
|The community posts on Medium.
|}

== 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 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 ==
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="ethereansosmedium-11664">[https://medium.com/ethereansos/the-white-hat-rug-pull-your-eth-usdc-and-os-are-safe-all-is-well-3125bd5f3409 The White Hat Rug Pull Your Eth Usdc And Os Are Safe All Is Well] (Nov 4, 2022)</ref>

<ref name="ethereansosmedium-11665">[https://medium.com/ethereansos/an-overview-of-ethereansos-3c761cc5ae8f An Overview of Ethereansos] (Sep 12, 2023)</ref>

<ref name="ethereansosmedium-11666">[https://medium.com/ethereansos https://medium.com/ethereansos] (Sep 12, 2023)</ref>

<ref name="ethereansos-11667">[https://ethereansos.eth.link/ EthereansOS] (Sep 12, 2023)</ref>

<ref name="ethereansos-11668">[https://ethereansos.eth.limo/ EthereansOS] (Sep 12, 2023)</ref>

<ref name="facebook-11669">[https://www.facebook.com/EthereansCommunity/videos/399318758343898/ EthereansCommunity - Facebook] (Sep 12, 2023)</ref>

<ref name="facebook-11670">[https://www.facebook.com/groups/2920359114947846/ Groups - Facebook] (Sep 12, 2023)</ref>

<ref name="ethosdocs-11671">[https://docs.ethos.wiki/ethereansos-docs/ Index - EthereansOS Docs] (Sep 12, 2023)</ref></references>

EthereansOS White Hat Rug Pull - Revision history