Details

Magic Eden looks forward to working with the security community to find vulnerabilities in order to keep our businesses and customers safe.

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

Disclosure Policy

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

Program Rules

Reporting your vulnerability

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.
When reporting vulnerabilities, please consider (1) attack scenario / exploitability, and (2) security impact of the bug.
For vulnerabilities involving personally identifiable information, please explain the kind of PII you believe is exposed and limit the amount of PII data included in your submissions.
Reference HackerOne’s guidance on writing quality reports

Performing your research

Do not impact production systems in a negative way for any testing
All smart contract testing should be done with a forked local copy of mainnet
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.
We recommend adding your HackerOne @wearehackerone.com email address to any Magic Eden account that you use to perform security research and testing. Clearly identifying accounts that are associated with bug bounty research helps our team to differentiate between possibly malicious activity and that of researchers involved in our bug bounty program

dicey.com Program Scope

Original games
Bonus points
High-severity technical vulnerabilities
RNG vulnerabilities
Payout vulnerabilities

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:

Any activity that could lead to the disruption of our service (DoS, DDoS)
Any attack that requires a user to interact with contract from an attacker controlled website
Attacks requiring MITM or physical access to a user's device.
Broken external links
Chain specific vulnerabilities are excluded, (e.g. EVM or Solana runtime issues)
Clickjacking on pages with no sensitive actions
Clickjacking within a NFT displayed on Magic Eden
Comma Separated Values (CSV) injection without demonstrating a vulnerability.
Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS
Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions
Duplicate reported vulnerabilities from other reports or submissions that have yet to be resolved
Issues that depend on third-party services or out of scope assets
Issues that require unlikely user interaction
Missing best practices in Content Security Policy
Missing best practices in SSL/TLS configuration
Missing email best practices (Invalid, incomplete or missing SPF/DKIM/DMARC records, etc.)
Missing HttpOnly or Secure flags on cookies
Open redirect - unless an additional security impact can be demonstrated
Previously known vulnerable libraries without a working Proof of Concept
Public Zero-day vulnerabilities that have had an official patch for less than 1 month will be awarded on a case by case basis
Rate limiting or bruteforce issues on non-authentication endpoints
Software version disclosure / Banner identification issues / Descriptive error messages or headers (e.g. stack traces, application or server errors)
Tabnabbing
Vulnerabilities only affecting users of outdated or unpatched browsers [Less than 2 stable versions behind the latest released stable version]

dicey.com | Out of Scope

Third-party games: Any vulnerabilities residing within games provided by external vendors.
Third-party wallets: Issues related to external wallet providers that do not directly impact user balances or transaction integrity on our platform.
General exclusions: All vulnerabilities listed in our [General Out-of-Scope Policy].

magiceden.io/us | Out of Scope

Non-Solana networks: Any issues specifically related to blockchains other than Solana (e.g., Ethereum, Polygon, Bitcoin).
General exclusions: All vulnerabilities listed in our [General Out-of-Scope Policy].

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 Magic Eden and our users safe!

Reporting your vulnerability

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.

When reporting vulnerabilities, please consider (1) attack scenario / exploitability, and (2) security impact of the bug.

For vulnerabilities involving personally identifiable information, please explain the kind of PII you believe is exposed and limit the amount of PII data included in your submissions.

Reference HackerOne’s guidance on writing quality reports

Performing your research

Do not impact production systems in a negative way for any testing

All smart contract testing should be done with a forked local copy of mainnet

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.

We recommend adding your HackerOne @wearehackerone.com email address to any Magic Eden account that you use to perform security research and testing. Clearly identifying accounts that are associated with bug bounty research helps our team to differentiate between possibly malicious activity and that of researchers involved in our bug bounty program

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:

Any activity that could lead to the disruption of our service (DoS, DDoS)

Any attack that requires a user to interact with contract from an attacker controlled website

Attacks requiring MITM or physical access to a user's device.

Broken external links

Chain specific vulnerabilities are excluded, (e.g. EVM or Solana runtime issues)

Clickjacking on pages with no sensitive actions

Clickjacking within a NFT displayed on Magic Eden

Comma Separated Values (CSV) injection without demonstrating a vulnerability.

Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS

Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions

Duplicate reported vulnerabilities from other reports or submissions that have yet to be resolved

Issues that depend on third-party services or out of scope assets

Issues that require unlikely user interaction

Missing best practices in Content Security Policy

Missing best practices in SSL/TLS configuration

Missing email best practices (Invalid, incomplete or missing SPF/DKIM/DMARC records, etc.)

Missing HttpOnly or Secure flags on cookies

Open redirect - unless an additional security impact can be demonstrated

Previously known vulnerable libraries without a working Proof of Concept

Public Zero-day vulnerabilities that have had an official patch for less than 1 month will be awarded on a case by case basis

Rate limiting or bruteforce issues on non-authentication endpoints

Software version disclosure / Banner identification issues / Descriptive error messages or headers (e.g. stack traces, application or server errors)

Tabnabbing

Vulnerabilities only affecting users of outdated or unpatched browsers [Less than 2 stable versions behind the latest released stable version]

dicey.com | Out of Scope

Third-party games: Any vulnerabilities residing within games provided by external vendors.

Third-party wallets: Issues related to external wallet providers that do not directly impact user balances or transaction integrity on our platform.

General exclusions: All vulnerabilities listed in our [General Out-of-Scope Policy].

Safe Harbor

Thank you for helping keep Magic Eden and our users safe!