Azoundria: Created page with "{{Imported Case Study With About|source=https://www.quadrigainitiative.com/casestudy/cryptobottlewithdrawuserliquiditymissingaccesscontrol.php}} {{Unattributed Sources}} Cryptobottle Logo/HomepageCryptoBottle is a unique concept where an NFT representation of virtual vine is minted, which contains a diverse mix of cryptocurrency assets. The NFT can be "opened" in the future to unlock the underlying assets, and this is permanent and irreve..."

2024-11-15T21:42:13Z

Created page with "{{Imported Case Study With About|source=https://www.quadrigainitiative.com/casestudy/cryptobottlewithdrawuserliquiditymissingaccesscontrol.php}} {{Unattributed Sources}} thumb|Cryptobottle Logo/HomepageCryptoBottle is a unique concept where an NFT representation of virtual vine is minted, which contains a diverse mix of cryptocurrency assets. The NFT can be "opened" in the future to unlock the underlying assets, and this is permanent and irreve..."

New page

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

[[File:Cryptobottle.jpg|thumb|Cryptobottle Logo/Homepage]]CryptoBottle is a unique concept where an NFT representation of virtual vine is minted, which contains a diverse mix of cryptocurrency assets. The NFT can be "opened" in the future to unlock the underlying assets, and this is permanent and irreversible, decreasing the remaining bottles in the collection. On October 1st, the project experienced thait first exploit for $6k, which happened due to a missing access control on the smart contract's withdrawUseRLiquidity function. This vulnerability or event doesn't appear to be publicly acknowledged by the team and is not widely known. It would be featured in an analysis by CertiK a month later, only after more vulnerabilities had been exploited for much larger losses.<ref name="certik-16825" /><ref name="nftcryptobottletwitter-16826" /><ref name="cryptobottle-16827" /><ref name="polygonscan-16828" /><ref name="polygonscan-16829" />

== About Cryptobottle ==
"Create, buy or sell first bottles virtual wine. Collect, invest or become an artist by creating your own NFT cryptobottle. Anyone can launch their own vintages (collections) with the possibility of adding benefits that will be used in real life!"

"Cryptobottle is an innovative project designed to empower various entities—such as businesses, associations, event companies, and retailers—to create unique NFT collections. These NFTs, known as "cryptobottles," combine art, utilities, and cryptocurrencies, encapsulating significant financial value. Cryptobottles serve as a versatile tool for promotion, customer loyalty, and sales enhancement."

"Our platform offers an incredibly simple solution for acquiring cryptocurrencies and unique artworks without needing any specialized knowledge. Users can configure these super NFTs according to their specific needs, highlighting their products or services in the most effective way possible."

"These vintages of bottles are actually collections of digital objects which do not contain wine, but cryptocurrencies."

"Each bottle owned gives you access to customer benefits.

The estates offer you these advantages to enhance their wines.

They can take the form of promotional codes, vouchers, loyalty programs, etc
cultural advantages.. and are proposed by the domain that creates the vintage.

Other "affiliation" partnerships can also be offered by any company.

The possibilities are endless. Choose your Cryptobottles well!"

== 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 ==
"On 1 October approximately $6,000 was taken from contract 0x34EFEbC3fdfC4503547116234E4efb203C90ca72 (NA) due to missing access control on the contract’s withdrawUserLIquidity() function."
{| class="wikitable"
|+Key Event Timeline - Cryptobottle WithdrawUserLiquidity Missing Access Control
!Date
!Event
!Description
|-
|October, 2024
|Smart Contract Exploited
|The Cryptobottle smart contract is exploited.
|-
|October 1st, 2024 7:38:54 PM MDT
|Emergency Withdraw Invoked
|The emergency withdraw function is invoked on the smart contract.
|-
|November 11th, 2024 6:06:00 AM MST
|CertiK Analysis Prepared More
|CertiK prepares an analysis of all exploits, mainly focusing on the largest $490k hack which happened near the end of October.
|}

== 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 $6,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="certik-16825">[https://www.certik.com/resources/blog/5sFtciEJ5fBV56zSeXWcW-cryptobottle-incident-analysis https://www.certik.com/resources/blog/5sFtciEJ5fBV56zSeXWcW-cryptobottle-incident-analysis] (Accessed Nov 15, 2024)</ref>

<ref name="nftcryptobottletwitter-16826">[https://twitter.com/NFTCryptoBottle/status/1850221029777354925 @NFTCryptoBottle Twitter] (Accessed Nov 15, 2024)</ref>

<ref name="cryptobottle-16827">[https://www.cryptobottle.fr/ Cryptobottle] (Accessed Nov 15, 2024)</ref>

<ref name="polygonscan-16828">[https://polygonscan.com/tx/0xc1b28b0a34b005c079c399ef706e7f32c5141adb7676f4ed4f163bb7812f4657 Polygon PoS Chain Transaction Hash (Txhash) Details | PolygonScan] (Accessed Nov 15, 2024)</ref>

<ref name="polygonscan-16829">[https://polygonscan.com/txs?a=0x34EFEbC3fdfC4503547116234E4efb203C90ca72 Polygon PoS Chain Transactions Information | PolygonScan] (Accessed Nov 15, 2024)</ref></references>

Cryptobottle WithdrawUserLiquidity Missing Access Control - Revision history