Welcome to the Yuga Labs bug bounty program! We care deeply about the security of our community and we look forward to working with bug bounty hunters to find and remediate vulnerabilities.

Shaping web3 through storytelling, experiences, and community. We believe that the potential of web3 can be realized when we start with imagination, not limitations. No borders, no rulers, just people making cool shit, together. In the Yugaverse, fans and players are owners and creators, and in the game of web3, everyone can create and play together on one team.

Response Targets

Yuga Labs will make a best effort to meet the following SLAs for hackers participating in our program:

We’ll try to keep you informed about our progress throughout the process.

Discord Policy

For the Discord program, we're looking for any issues where an attacker may be able to:

• Access NFT-gated channels without owning the appropriate NFT (e.g. #members-only)
• Post to restricted channels (see Announcement Flag below)
• Perform any unauthorized action against the Discord server

When testing, avoid testing in public channels like #general and take all steps to avoid disrupting the Discord server. You are expected to follow all rules listed in the #rules channel. Social engineering is explicitly out of scope and will result in a permanent ban from both the Discord server and the HackerOne program.

If you find you're able to perform unauthorized actions, do not perform any unnecessary test actions. For example, if you identify a vulnerability allowing you to post to any channel, send one test message to the #announcements-canary channel, stop testing, and report the issue.

Announcement Flag

For the purposes of the bug bounty program, we've created a hidden #announcements-canary channel on the Bored Ape Yacht Club, Otherside, Meebits, and Cryptopunks Discord servers which has the same permissions as the #announcements channel. If you identify a way in which you can post a custom message to the #announcements-canary channel, we will award (at minimum) a critical payout.

Disclosure Policy

• Please do not discuss any vulnerabilities (even resolved ones) outside of the program without express consent from the organization.
• Follow HackerOne's disclosure guidelines.

Program Rules

• Please provide detailed reports with reproducible steps. If the report is not detailed enough to reproduce the issue, the issue will not be eligible for a reward.
• Submit one vulnerability per report, unless you need to chain vulnerabilities to provide impact.
• When duplicates occur, we only award the first report that was received (provided that it can be fully reproduced).
• Multiple vulnerabilities caused by one underlying issue will be awarded one bounty.
• Social engineering (e.g. phishing, vishing, smishing) is prohibited.
• Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our service. Only interact with accounts you own or with explicit permission of the account holder.

Out of scope vulnerabilities

When reporting vulnerabilities, please consider (1) attack scenario / exploitability, and (2) security impact of the bug. The following issues are considered out of scope:

• HTTP request smuggling without clear a reproducible demonstration of harm to another user (e.g. poisoned link, collected HTTP requests from another user, etc)
• Clickjacking on pages with no sensitive actions
• Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions
• Attacks requiring MITM or physical access to a user's device.
• Previously known vulnerable libraries without a working Proof of Concept.
• Comma Separated Values (CSV) injection without demonstrating a vulnerability.
• Missing best practices in SSL/TLS configuration.
• Any activity that could lead to the disruption of our service, including NextJS/CloudFlare header DoS
• Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS
• Rate limiting or bruteforce issues on non-authentication endpoints
• Missing best practices in Content Security Policy.
• Missing HttpOnly or Secure flags on cookies
• Missing email best practices (Invalid, incomplete or missing SPF/DKIM/DMARC records, etc.)
• Vulnerabilities only affecting users of outdated or unpatched browsers [Less than 2 stable versions behind the latest released stable version]
• Software version disclosure / Banner identification issues / Descriptive error messages or headers (e.g. stack traces, application or server errors).
• Public Zero-day vulnerabilities that have had an official patch for less than 1 month will be awarded on a case by case basis.
• Tabnabbing
• Open redirect - unless an additional security impact can be demonstrated
• Issues that require unlikely user interaction will be awarded on a case by case basis
• Granting temporary access to token-gated functionalities across multiple wallets via transferring an NFT between addresses
• Issues related to authentication on the Meebits and Cryptopunks websites

Safe Harbor

Any activities conducted in a manner consistent with this policy will be considered authorized conduct and we will not initiate legal action against you. If legal action is initiated by a third party against you in connection with activities conducted under this policy, we will take steps to make it known that your actions were conducted in compliance with this policy.

Thank you for helping keep Yuga Labs and our users safe! For any questions regarding the Yuga Labs HackerOne program, please contact [email protected]