Doodles NFT Discord Hacked

Notice: This page is a freshly imported case study from the original repository. The original content was in a different format, and may not have relevant information for all sections. Please help restructure the content by moving information from the 'About' and 'General Prevention' sections to other sections, and add any missing information or sources you can find. If you are new here, please read General Tutorial on Wikis or Anatomy of a Case Study for help getting started.

Notice: This page contains sources which are not attributed to any text. The unattributed sources follow the initial description. Please assist by visiting each source, reviewing the content, and placing that reference next to any text it can be used to support. Feel free to add any information that you come across which isn't present already. Sources which don't contain any relevant information can be removed. Broken links can be replaced with versions from the Internet Archive. See General Tutorial on Wikis, Anatomy of a Case Study, and/or Citing Your Sources Guide for additional information. Thanks for your help!

Doodles NFT

The Doodles NFT are a collection of 10,000 hand-drawn NFT images made by a Canadian artist with the handle "Burnt Toast". The Discord server of the project was hacked on February 26th by an unknown exploit. It is unknown how much was taken, and doesn't appear any was recovered. Similar exploits have commonly abused webhooks being given too high of a permission level.

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

About Doodles NFT

"Doodles are a collection of 10,000 NFTs (non-fungible tokens) that are made up of hundreds of exciting visual traits designed by Burnt Toast." "Doodles are a colorful NFT collection of cartoonish figures with unique features and colorful backgrounds. Doodles NFTs were created by Scott Martin (aka Burnt Toast), an established Canadian artist and illustrator. Doodles are made from random combinations of 256 traits. The collection also features 62 hand-drawn Custom Doodles."

"Hand-drawn Doodles include skellys, cats, aliens, apes and mascots. The Doodles collection also includes dozens of rare heads, costumes, and colorways of the artist's palette." "Doodles NFTs are enjoyed for their droll expressions, colorful palettes and the vibrant online community that shares a passion for this project. Doodles are often used as PFPs (profile pictures) on social media platforms."

"The Doodles universe is ever-expanding and new experiences like Space Doodles are only available to collectors. While the universe expands, our brand grows, and collectors can expect exclusive access to the latest products, merchandise and events through ownership."

"Not too long ago, on February 27, the collection’s Discord server was penetrated by a hacked bot." "The NFT industry’s beloved collection, Doodles is the latest to fall victim to a Discord hack. Apparently, a “hacked bot” penetrated the project’s Discord server, the team said in a tweet late last night."

"Doodles discord was penetrated by a hacked bot. Any message put out in any of our channels, ignore for now. We are on it. Our lawyers, friends at discord, and the community are helping us. We will update you as we diagnose the situation."

"But the team managed to regain control and secure the server pretty quickly." "Hours later, Doodles announced that it has secured the server and it will reimburse all the affected holders."

"The Official Doodles Discord has been successfully secured. It will take us some time to collect all of the data and complete an analysis of the attack. Community members affected by the attack will be compensated."

"At the time of going to press, Doodles had not revealed more details of the hack. It is yet unclear how many members were affected or what the losses are. However, many Twitter users praised the Doodles team for their quick action."

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.

Key Event Timeline - Doodles NFT Discord Hacked

Date	Event	Description
February 26th, 2022 1:27:00 PM MST	Main Event	Expand this into a brief 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

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?

General Prevention Policies

The lesson here is most likely about providing an account/tool with more privileges than necessary. Using a full-permissioned account when not necessary increases the breach window.

Ideally, performing key actions such as banning moderators or posting global announcements would be set up such that multiple people's approval is required. In this way, it would be nearly impossible to breach.

In our framework, we advocate for training platform operators about incidents such as these, and require the approval of two separate security sign-offs for a project to launch, which would likely catch any weak security practices. A discretionary treasury fund is available to cover losses, in addition to whatever treasury is available with projects directly.

Individual Prevention Policies

No specific policies for individual prevention have yet been identified in this case.

For the full list of how to protect your funds as an individual, check our Prevention Policies for Individuals guide.

Platform Prevention Policies

Policies for platforms to take to prevent this situation have not yet been selected in this case.

For the full list of how to protect your funds as a financial service, check our Prevention Policies for Platforms guide.

Regulatory Prevention Policies

No specific regulatory policies have yet been identified in this case.

For the full list of regulatory policies that can prevent loss, check our Prevention Policies for Regulators guide.