[{"id":3770596,"new_policy":"Magic Eden looks forward to working with the security community to find vulnerabilities in order to keep our businesses and customers safe.\n\nWe’ll try to keep you informed about our progress throughout the process.\n\n# Disclosure Policy\n* Please do not discuss this program or any vulnerabilities (even resolved ones) outside of the program without express consent from the organization.\n* Follow HackerOne's [disclosure guidelines](https://www.hackerone.com/disclosure-guidelines).\n\n\n# Program Rules\n## Reporting your vulnerability\n* 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.\n* When reporting vulnerabilities, please consider (1) attack scenario / exploitability, and (2) security impact of the bug. \n* 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.\n* Reference [HackerOne’s guidance on writing quality reports](https://docs.hackerone.com/hackers/quality-reports.html)\n\n## Performing your research\n* Do not impact production systems in a negative way for any testing\n* All smart contract testing should be done with a forked local copy of mainnet\n* Submit one vulnerability per report, unless you need to chain vulnerabilities to provide impact.\n* When duplicates occur, we only award the first report that was received (provided that it can be fully reproduced).\n* Multiple vulnerabilities caused by one underlying issue will be awarded one bounty.\n* Social engineering (e.g. phishing, vishing, smishing) is prohibited.\n* 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.\n* 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\n\n## dicey.com Program Scope\n* Original games\n* Bonus points\n* High-severity technical vulnerabilities\n* RNG vulnerabilities\n* Payout vulnerabilities\n \n\n# Out of scope vulnerabilities\n\n### When reporting vulnerabilities, please consider (1) attack scenario / exploitability, and (2) security impact of the bug. The following issues are considered out of scope:\n\n* Any activity that could lead to the disruption of our service (DoS, DDoS)\n* Any attack that requires a user to interact with contract from an attacker controlled website\n* Attacks requiring MITM or physical access to a user's device.\n* Broken external links\n* Chain specific vulnerabilities are excluded, (e.g. EVM or Solana runtime issues)\n* Clickjacking on pages with no sensitive actions\n* Clickjacking within a NFT displayed on Magic Eden\n* Comma Separated Values (CSV) injection without demonstrating a vulnerability.\n* Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS\n* Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions\n* Duplicate reported vulnerabilities from other reports or submissions that have yet to be resolved\n* Issues that depend on third-party services or out of scope assets\n* Issues that require unlikely user interaction\n* Missing best practices in Content Security Policy\n* Missing best practices in SSL/TLS configuration\n* Missing email best practices (Invalid, incomplete or missing SPF/DKIM/DMARC records, etc.)\n* Missing HttpOnly or Secure flags on cookies\n* Open redirect - unless an additional security impact can be demonstrated\n* Previously known vulnerable libraries without a working Proof of Concept\n* Public Zero-day vulnerabilities that have had an official patch for less than 1 month will be awarded on a case by case basis\n* Rate limiting or bruteforce issues on non-authentication endpoints\n* Software version disclosure / Banner identification issues / Descriptive error messages or headers (e.g. stack traces, application or server errors)\n* Tabnabbing\n* Vulnerabilities only affecting users of outdated or unpatched browsers [Less than 2 stable versions behind the latest released stable version]\n\n## dicey.com | Out of Scope\n* Third-party games: Any vulnerabilities residing within games provided by external vendors.\n* Third-party wallets: Issues related to external wallet providers that do not directly impact user balances or transaction integrity on our platform.\n* General exclusions: All vulnerabilities listed in our [General Out-of-Scope Policy].\n\n## magiceden.io/us | Out of Scope\n* Non-Solana networks: Any issues specifically related to blockchains other than Solana (e.g., Ethereum, Polygon, Bitcoin).\n* General exclusions: All vulnerabilities listed in our [General Out-of-Scope Policy].\n\n\n# Safe Harbor\nAny 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.\n\nThank you for helping keep Magic Eden and our users safe!\n","has_open_scope":null,"pays_within_one_month":null,"protected_by_gold_standard_safe_harbor":true,"protected_by_ai_safe_harbor":null,"disclosure_declaration":null,"introduction":null,"platform_standards_exclusions":[],"exemplary_standards_exclusions":[],"scope_exclusions":[],"timestamp":"2026-03-04T22:07:14.803Z"},{"id":3770595,"new_policy":"Magic Eden looks forward to working with the security community to find vulnerabilities in order to keep our businesses and customers safe.\n\nWe’ll try to keep you informed about our progress throughout the process.\n\n# Disclosure Policy\n* Please do not discuss this program or any vulnerabilities (even resolved ones) outside of the program without express consent from the organization.\n* Follow HackerOne's [disclosure guidelines](https://www.hackerone.com/disclosure-guidelines).\n\n\n# Program Rules\n## Reporting your vulnerability\n* 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.\n* When reporting vulnerabilities, please consider (1) attack scenario / exploitability, and (2) security impact of the bug. \n* 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.\n* Reference [HackerOne’s guidance on writing quality reports](https://docs.hackerone.com/hackers/quality-reports.html)\n\n## Performing your research\n* Do not impact production systems in a negative way for any testing\n* All smart contract testing should be done with a forked local copy of mainnet\n* Submit one vulnerability per report, unless you need to chain vulnerabilities to provide impact.\n* When duplicates occur, we only award the first report that was received (provided that it can be fully reproduced).\n* Multiple vulnerabilities caused by one underlying issue will be awarded one bounty.\n* Social engineering (e.g. phishing, vishing, smishing) is prohibited.\n* 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.\n* 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\n\n## General dicey.com scope\n* Original games\n* Bonus points\n* High-severity technical vulnerabilities\n* RNG vulnerabilities\n* Payout vulnerabilities\n \n\n# Out of scope vulnerabilities\n\n### When reporting vulnerabilities, please consider (1) attack scenario / exploitability, and (2) security impact of the bug. The following issues are considered out of scope:\n\n* Any activity that could lead to the disruption of our service (DoS, DDoS)\n* Any attack that requires a user to interact with contract from an attacker controlled website\n* Attacks requiring MITM or physical access to a user's device.\n* Broken external links\n* Chain specific vulnerabilities are excluded, (e.g. EVM or Solana runtime issues)\n* Clickjacking on pages with no sensitive actions\n* Clickjacking within a NFT displayed on Magic Eden\n* Comma Separated Values (CSV) injection without demonstrating a vulnerability.\n* Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS\n* Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions\n* Duplicate reported vulnerabilities from other reports or submissions that have yet to be resolved\n* Issues that depend on third-party services or out of scope assets\n* Issues that require unlikely user interaction\n* Missing best practices in Content Security Policy\n* Missing best practices in SSL/TLS configuration\n* Missing email best practices (Invalid, incomplete or missing SPF/DKIM/DMARC records, etc.)\n* Missing HttpOnly or Secure flags on cookies\n* Open redirect - unless an additional security impact can be demonstrated\n* Previously known vulnerable libraries without a working Proof of Concept\n* Public Zero-day vulnerabilities that have had an official patch for less than 1 month will be awarded on a case by case basis\n* Rate limiting or bruteforce issues on non-authentication endpoints\n* Software version disclosure / Banner identification issues / Descriptive error messages or headers (e.g. stack traces, application or server errors)\n* Tabnabbing\n* Vulnerabilities only affecting users of outdated or unpatched browsers [Less than 2 stable versions behind the latest released stable version]\n\n## dicey.com | Out of Scope\n* Third-party games: Any vulnerabilities residing within games provided by external vendors.\n* Third-party wallets: Issues related to external wallet providers that do not directly impact user balances or transaction integrity on our platform.\n* General exclusions: All vulnerabilities listed in our [General Out-of-Scope Policy].\n\n## magiceden.io/us | Out of Scope\n* Non-Solana networks: Any issues specifically related to blockchains other than Solana (e.g., Ethereum, Polygon, Bitcoin).\n* General exclusions: All vulnerabilities listed in our [General Out-of-Scope Policy].\n\n\n# Safe Harbor\nAny 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.\n\nThank you for helping keep Magic Eden and our users safe!\n","has_open_scope":null,"pays_within_one_month":null,"protected_by_gold_standard_safe_harbor":true,"protected_by_ai_safe_harbor":null,"disclosure_declaration":null,"introduction":null,"platform_standards_exclusions":[],"exemplary_standards_exclusions":[],"scope_exclusions":[],"timestamp":"2026-03-04T22:06:01.332Z"},{"id":3755745,"new_policy":"Magic Eden looks forward to working with the security community to find vulnerabilities in order to keep our businesses and customers safe.\n\nWe’ll try to keep you informed about our progress throughout the process.\n\n# Disclosure Policy\n* Please do not discuss this program or any vulnerabilities (even resolved ones) outside of the program without express consent from the organization.\n* Follow HackerOne's [disclosure guidelines](https://www.hackerone.com/disclosure-guidelines).\n\n\n# Program Rules\n## Reporting your vulnerability\n* 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.\n* When reporting vulnerabilities, please consider (1) attack scenario / exploitability, and (2) security impact of the bug. \n* 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.\n* Reference [HackerOne’s guidance on writing quality reports](https://docs.hackerone.com/hackers/quality-reports.html)\n\n## Performing your research\n* Do not impact production systems in a negative way for any testing\n* All smart contract testing should be done with a forked local copy of mainnet\n* Submit one vulnerability per report, unless you need to chain vulnerabilities to provide impact.\n* When duplicates occur, we only award the first report that was received (provided that it can be fully reproduced).\n* Multiple vulnerabilities caused by one underlying issue will be awarded one bounty.\n* Social engineering (e.g. phishing, vishing, smishing) is prohibited.\n* 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.\n* 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\n \n\n# Out of scope vulnerabilities\n\n### When reporting vulnerabilities, please consider (1) attack scenario / exploitability, and (2) security impact of the bug. The following issues are considered out of scope:\n\n* Any activity that could lead to the disruption of our service (DoS, DDoS)\n* Any attack that requires a user to interact with contract from an attacker controlled website\n* Attacks requiring MITM or physical access to a user's device.\n* Broken external links\n* Chain specific vulnerabilities are excluded, (e.g. EVM or Solana runtime issues)\n* Clickjacking on pages with no sensitive actions\n* Clickjacking within a NFT displayed on Magic Eden\n* Comma Separated Values (CSV) injection without demonstrating a vulnerability.\n* Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS\n* Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions\n* Duplicate reported vulnerabilities from other reports or submissions that have yet to be resolved\n* Issues that depend on third-party services or out of scope assets\n* Issues that require unlikely user interaction\n* Missing best practices in Content Security Policy\n* Missing best practices in SSL/TLS configuration\n* Missing email best practices (Invalid, incomplete or missing SPF/DKIM/DMARC records, etc.)\n* Missing HttpOnly or Secure flags on cookies\n* Open redirect - unless an additional security impact can be demonstrated\n* Previously known vulnerable libraries without a working Proof of Concept\n* Public Zero-day vulnerabilities that have had an official patch for less than 1 month will be awarded on a case by case basis\n* Rate limiting or bruteforce issues on non-authentication endpoints\n* Software version disclosure / Banner identification issues / Descriptive error messages or headers (e.g. stack traces, application or server errors)\n* Tabnabbing\n* Vulnerabilities only affecting users of outdated or unpatched browsers [Less than 2 stable versions behind the latest released stable version]\n\n\n# Safe Harbor\nAny 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.\n\nThank you for helping keep Magic Eden and our users safe!\n","has_open_scope":null,"pays_within_one_month":null,"protected_by_gold_standard_safe_harbor":true,"protected_by_ai_safe_harbor":null,"disclosure_declaration":null,"introduction":null,"platform_standards_exclusions":[],"exemplary_standards_exclusions":[],"scope_exclusions":[],"timestamp":"2025-05-15T23:03:37.318Z"},{"id":3711572,"new_policy":"Magic Eden looks forward to working with the security community to find vulnerabilities in order to keep our businesses and customers safe.\n\n# Response Targets\nMagic Eden will make a best effort to meet the following SLAs for hackers participating in our program:\n\n| Type of Response | SLA in business days |\n| ------------- | ------------- |\n| First Response | 2 days |\n| Time to Triage | 7 days |\n| Time to Bounty | 14 days |\n| Time to Resolution | depends on severity and complexity |\n\nWe’ll try to keep you informed about our progress throughout the process.\n\n# Disclosure Policy\n* Please do not discuss this program or any vulnerabilities (even resolved ones) outside of the program without express consent from the organization.\n* Follow HackerOne's [disclosure guidelines](https://www.hackerone.com/disclosure-guidelines).\n\n\n# Program Rules\n## Reporting your vulnerability\n* 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.\n* When reporting vulnerabilities, please consider (1) attack scenario / exploitability, and (2) security impact of the bug. \n* 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.\n* Reference [HackerOne’s guidance on writing quality reports](https://docs.hackerone.com/hackers/quality-reports.html)\n\n## Performing your research\n* Do not impact production systems in a negative way for any testing\n* All smart contract testing should be done with a forked local copy of mainnet\n* Submit one vulnerability per report, unless you need to chain vulnerabilities to provide impact.\n* When duplicates occur, we only award the first report that was received (provided that it can be fully reproduced).\n* Multiple vulnerabilities caused by one underlying issue will be awarded one bounty.\n* Social engineering (e.g. phishing, vishing, smishing) is prohibited.\n* 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.\n* 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\n \n\n# Out of scope vulnerabilities\n\n### When reporting vulnerabilities, please consider (1) attack scenario / exploitability, and (2) security impact of the bug. The following issues are considered out of scope:\n\n* Any activity that could lead to the disruption of our service (DoS, DDoS)\n* Any attack that requires a user to interact with contract from an attacker controlled website\n* Attacks requiring MITM or physical access to a user's device.\n* Broken external links\n* Chain specific vulnerabilities are excluded, (e.g. EVM or Solana runtime issues)\n* Clickjacking on pages with no sensitive actions\n* Clickjacking within a NFT displayed on Magic Eden\n* Comma Separated Values (CSV) injection without demonstrating a vulnerability.\n* Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS\n* Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions\n* Duplicate reported vulnerabilities from other reports or submissions that have yet to be resolved\n* Issues that depend on third-party services or out of scope assets\n* Issues that require unlikely user interaction\n* Missing best practices in Content Security Policy\n* Missing best practices in SSL/TLS configuration\n* Missing email best practices (Invalid, incomplete or missing SPF/DKIM/DMARC records, etc.)\n* Missing HttpOnly or Secure flags on cookies\n* Open redirect - unless an additional security impact can be demonstrated\n* Previously known vulnerable libraries without a working Proof of Concept\n* Public Zero-day vulnerabilities that have had an official patch for less than 1 month will be awarded on a case by case basis\n* Rate limiting or bruteforce issues on non-authentication endpoints\n* Software version disclosure / Banner identification issues / Descriptive error messages or headers (e.g. stack traces, application or server errors)\n* Tabnabbing\n* Vulnerabilities only affecting users of outdated or unpatched browsers [Less than 2 stable versions behind the latest released stable version]\n\n\n# Safe Harbor\nAny 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.\n\nThank you for helping keep Magic Eden and our users safe!\n","has_open_scope":null,"pays_within_one_month":null,"protected_by_gold_standard_safe_harbor":null,"protected_by_ai_safe_harbor":null,"disclosure_declaration":null,"introduction":null,"platform_standards_exclusions":[],"exemplary_standards_exclusions":[],"scope_exclusions":[],"timestamp":"2024-01-26T05:12:20.712Z"},{"id":3683280,"new_policy":"Magic Eden looks forward to working with the security community to find vulnerabilities in order to keep our businesses and customers safe.\n\n# Response Targets\nMagic Eden will make a best effort to meet the following SLAs for hackers participating in our program:\n\n| Type of Response | SLA in business days |\n| ------------- | ------------- |\n| First Response | 2 days |\n| Time to Triage | 4 days |\n| Time to Bounty | 14 days |\n| Time to Resolution | depends on severity and complexity |\n\nWe’ll try to keep you informed about our progress throughout the process.\n\n# Disclosure Policy\n* Please do not discuss this program or any vulnerabilities (even resolved ones) outside of the program without express consent from the organization.\n* Follow HackerOne's [disclosure guidelines](https://www.hackerone.com/disclosure-guidelines).\n\n\n# Program Rules\n## Reporting your vulnerability\n* 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.\n* When reporting vulnerabilities, please consider (1) attack scenario / exploitability, and (2) security impact of the bug. \n* 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.\n* Reference [HackerOne’s guidance on writing quality reports](https://docs.hackerone.com/hackers/quality-reports.html)\n\n## Performing your research\n* Do not impact production systems in a negative way for any testing\n* All smart contract testing should be done with a forked local copy of mainnet\n* Submit one vulnerability per report, unless you need to chain vulnerabilities to provide impact.\n* When duplicates occur, we only award the first report that was received (provided that it can be fully reproduced).\n* Multiple vulnerabilities caused by one underlying issue will be awarded one bounty.\n* Social engineering (e.g. phishing, vishing, smishing) is prohibited.\n* 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.\n* 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\n \n\n# Out of scope vulnerabilities\n\n### When reporting vulnerabilities, please consider (1) attack scenario / exploitability, and (2) security impact of the bug. The following issues are considered out of scope:\n\n* Any activity that could lead to the disruption of our service (DoS, DDoS)\n* Any attack that requires a user to interact with contract from an attacker controlled website\n* Attacks requiring MITM or physical access to a user's device.\n* Broken external links\n* Chain specific vulnerabilities are excluded, (e.g. EVM or Solana runtime issues)\n* Clickjacking on pages with no sensitive actions\n* Clickjacking within a NFT displayed on Magic Eden\n* Comma Separated Values (CSV) injection without demonstrating a vulnerability.\n* Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS\n* Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions\n* Duplicate reported vulnerabilities from other reports or submissions that have yet to be resolved\n* Issues that depend on third-party services or out of scope assets\n* Issues that require unlikely user interaction\n* Missing best practices in Content Security Policy\n* Missing best practices in SSL/TLS configuration\n* Missing email best practices (Invalid, incomplete or missing SPF/DKIM/DMARC records, etc.)\n* Missing HttpOnly or Secure flags on cookies\n* Open redirect - unless an additional security impact can be demonstrated\n* Previously known vulnerable libraries without a working Proof of Concept\n* Public Zero-day vulnerabilities that have had an official patch for less than 1 month will be awarded on a case by case basis\n* Rate limiting or bruteforce issues on non-authentication endpoints\n* Software version disclosure / Banner identification issues / Descriptive error messages or headers (e.g. stack traces, application or server errors)\n* Tabnabbing\n* Vulnerabilities only affecting users of outdated or unpatched browsers [Less than 2 stable versions behind the latest released stable version]\n\n\n# Safe Harbor\nAny 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.\n\nThank you for helping keep Magic Eden and our users safe!\n","has_open_scope":null,"pays_within_one_month":null,"protected_by_gold_standard_safe_harbor":null,"protected_by_ai_safe_harbor":null,"disclosure_declaration":null,"introduction":null,"platform_standards_exclusions":[],"exemplary_standards_exclusions":[],"scope_exclusions":[],"timestamp":"2023-02-10T06:03:37.433Z"},{"id":3683279,"new_policy":"Magic Eden looks forward to working with the security community to find vulnerabilities in order to keep our businesses and customers safe.\n\n# Response Targets\nMagic Eden will make a best effort to meet the following SLAs for hackers participating in our program:\n\n| Type of Response | SLA in business days |\n| ------------- | ------------- |\n| First Response | 2 days |\n| Time to Triage | 4 days |\n| Time to Bounty | 14 days |\n| Time to Resolution | depends on severity and complexity |\n\nWe’ll try to keep you informed about our progress throughout the process.\n\n# Disclosure Policy\n* Please do not discuss this program or any vulnerabilities (even resolved ones) outside of the program without express consent from the organization.\n* Follow HackerOne's [disclosure guidelines](https://www.hackerone.com/disclosure-guidelines).\n\n\n# Program Rules\n## Reporting your vulnerability\n* 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.\n* When reporting vulnerabilities, please consider (1) attack scenario / exploitability, and (2) security impact of the bug. \n* 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.\n* Reference [HackerOne’s guidance on writing quality reports](https://docs.hackerone.com/hackers/quality-reports.html)\n\n## Performing your research\n* Do not impact production systems in a negative way for any testing\n* All smart contract testing should be done with a forked local copy of mainnet\n* Submit one vulnerability per report, unless you need to chain vulnerabilities to provide impact.\n* When duplicates occur, we only award the first report that was received (provided that it can be fully reproduced).\n* Multiple vulnerabilities caused by one underlying issue will be awarded one bounty.\n* Social engineering (e.g. phishing, vishing, smishing) is prohibited.\n* 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.\n* 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\n \n\n# Sample issues by severity\n## Web2 assets\n| Severity | Sample Issue |\n| ------------- | ------------- |\n| Critical | Complete control over the affected asset |\n| | Ability to modify critical information or run arbitrary commands | \n| | Significant impact to the affected system or network operation | \n| High | Disclosure of sensitive information | \n| | Impersonation of other users |\n| | System compromise |\n| | Significant reputation impact |\n| Medium | Disclosure of sensitive but non-critical information | \n| | Denial of service|\n| Low | Non-sensitive information disclosure |\n| | Increased exposure to other weaknesses |\n| Informational | Missing best practices|\n\n\n## Web3 assets\n| Severity | Sample Issue |\n| ------------- | ------------- |\n| Critical | Any governance voting result manipulation |\n| | Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield |\n| | Permanent freezing of funds | \n| | Protocol Insolvency | \n| High | Theft of unclaimed yield | \n| | Permanent freezing of unclaimed yield | \n| Medium | Smart contract unable to operate due to lack of token funds | \n| | Block stuffing for profit | \n| | Grieving (e.g. no profit motive for an attacker, but damage to the users or the protocol) | \n| | Theft of gas | \n| | Unbounded gas consumption |\n| Low | Contract fails to deliver promised returns, but doesn't lose value | \n| Informational | Missing best practices|\n\n\n# Out of scope vulnerabilities\n\n### When reporting vulnerabilities, please consider (1) attack scenario / exploitability, and (2) security impact of the bug. The following issues are considered out of scope:\n\n* Any activity that could lead to the disruption of our service (DoS, DDoS)\n* Any attack that requires a user to interact with contract from an attacker controlled website\n* Attacks requiring MITM or physical access to a user's device.\n* Broken external links\n* Chain specific vulnerabilities are excluded, (e.g. EVM or Solana runtime issues)\n* Clickjacking on pages with no sensitive actions\n* Clickjacking within a NFT displayed on Magic Eden\n* Comma Separated Values (CSV) injection without demonstrating a vulnerability.\n* Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS\n* Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions\n* Duplicate reported vulnerabilities from other reports or submissions that have yet to be resolved\n* Issues that depend on third-party services or out of scope assets\n* Issues that require unlikely user interaction\n* Missing best practices in Content Security Policy\n* Missing best practices in SSL/TLS configuration\n* Missing email best practices (Invalid, incomplete or missing SPF/DKIM/DMARC records, etc.)\n* Missing HttpOnly or Secure flags on cookies\n* Open redirect - unless an additional security impact can be demonstrated\n* Previously known vulnerable libraries without a working Proof of Concept\n* Public Zero-day vulnerabilities that have had an official patch for less than 1 month will be awarded on a case by case basis\n* Rate limiting or bruteforce issues on non-authentication endpoints\n* Software version disclosure / Banner identification issues / Descriptive error messages or headers (e.g. stack traces, application or server errors)\n* Tabnabbing\n* Vulnerabilities only affecting users of outdated or unpatched browsers [Less than 2 stable versions behind the latest released stable version]\n\n\n# Safe Harbor\nAny 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.\n\nThank you for helping keep Magic Eden and our users safe!\n","has_open_scope":null,"pays_within_one_month":null,"protected_by_gold_standard_safe_harbor":null,"protected_by_ai_safe_harbor":null,"disclosure_declaration":null,"introduction":null,"platform_standards_exclusions":[],"exemplary_standards_exclusions":[],"scope_exclusions":[],"timestamp":"2023-02-10T05:59:06.479Z"},{"id":3683278,"new_policy":"Magic Eden looks forward to working with the security community to find vulnerabilities in order to keep our businesses and customers safe.\n\n# Response Targets\nMagic Eden will make a best effort to meet the following SLAs for hackers participating in our program:\n\n| Type of Response | SLA in business days |\n| ------------- | ------------- |\n| First Response | 2 days |\n| Time to Triage | 4 days |\n| Time to Bounty | 14 days |\n| Time to Resolution | depends on severity and complexity |\n\nWe’ll try to keep you informed about our progress throughout the process.\n\n# Disclosure Policy\n* Please do not discuss this program or any vulnerabilities (even resolved ones) outside of the program without express consent from the organization.\n* Follow HackerOne's [disclosure guidelines](https://www.hackerone.com/disclosure-guidelines).\n\n\n# Program Rules\n## Reporting your vulnerability\n* 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.\n* When reporting vulnerabilities, please consider (1) attack scenario / exploitability, and (2) security impact of the bug. \n* 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.\n* Reference [HackerOne’s guidance on writing quality reports](https://docs.hackerone.com/hackers/quality-reports.html)\n\n## Performing your research\n* Do not impact production systems in a negative way for any testing\n* All smart contract testing should be done with a forked local copy of mainnet\n* Submit one vulnerability per report, unless you need to chain vulnerabilities to provide impact.\n* When duplicates occur, we only award the first report that was received (provided that it can be fully reproduced).\n* Multiple vulnerabilities caused by one underlying issue will be awarded one bounty.\n* Social engineering (e.g. phishing, vishing, smishing) is prohibited.\n* 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.\n* 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\n \n# Out of scope vulnerabilities\n\n### When reporting vulnerabilities, please consider (1) attack scenario / exploitability, and (2) security impact of the bug. The following issues are considered out of scope:\n\n* Any activity that could lead to the disruption of our service (DoS, DDoS)\n* Any attack that requires a user to interact with contract from an attacker controlled website\n* Attacks requiring MITM or physical access to a user's device.\n* Broken external links\n* Chain specific vulnerabilities are excluded, (e.g. EVM or Solana runtime issues)\n* Chain specific vulnerabilities are excluded, e.g. EVM or Solana runtime issues.\n* Clickjacking on pages with no sensitive actions\n* Clickjacking within a NFT displayed on Magic Eden\n* Comma Separated Values (CSV) injection without demonstrating a vulnerability.\n* Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS\n* Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions\n* Duplicate reported vulnerabilities from other reports or submissions that have yet to be resolved\n* Issues that depend on third-party services or out of scope assets\n* Issues that require unlikely user interaction\n* Missing best practices in Content Security Policy.\n* Missing best practices in SSL/TLS configuration.\n* Missing email best practices (Invalid, incomplete or missing SPF/DKIM/DMARC records, etc.)\n* Missing HttpOnly or Secure flags on cookies\n* Open redirect - unless an additional security impact can be demonstrated\n* Previously known vulnerable libraries without a working Proof of Concept.\n* Public Zero-day vulnerabilities that have had an official patch for less than 1 month will be awarded on a case by case basis.\n* Rate limiting or bruteforce issues on non-authentication endpoints\n* Software version disclosure / Banner identification issues / Descriptive error messages or headers (e.g. stack traces, application or server errors).\n* Tabnabbing\n* Vulnerabilities only affecting users of outdated or unpatched browsers [Less than 2 stable versions behind the latest released stable version]\n\n\n# Safe Harbor\nAny 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.\n\nThank you for helping keep Magic Eden and our users safe!\n","has_open_scope":null,"pays_within_one_month":null,"protected_by_gold_standard_safe_harbor":null,"protected_by_ai_safe_harbor":null,"disclosure_declaration":null,"introduction":null,"platform_standards_exclusions":[],"exemplary_standards_exclusions":[],"scope_exclusions":[],"timestamp":"2023-02-10T05:27:40.185Z"},{"id":3682040,"new_policy":"Magic Eden looks forward to working with the security community to find vulnerabilities in order to keep our businesses and customers safe.\n\n# Response Targets\nMagic Eden will make a best effort to meet the following SLAs for hackers participating in our program:\n\n| Type of Response | SLA in business days |\n| ------------- | ------------- |\n| First Response | 2 days |\n| Time to Triage | 4 days |\n| Time to Bounty | 14 days |\n| Time to Resolution | depends on severity and complexity |\n\nWe’ll try to keep you informed about our progress throughout the process.\n\n# Disclosure Policy\n* Please do not discuss this program or any vulnerabilities (even resolved ones) outside of the program without express consent from the organization.\n* Follow HackerOne's [disclosure guidelines](https://www.hackerone.com/disclosure-guidelines).\n\n\n# Program Rules\nPlease 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.\n* Do not impact production systems in a negative way for any testing\n* All smart contract testing should be done with a forked local copy of mainnet\n* Submit one vulnerability per report, unless you need to chain vulnerabilities to provide impact.\n* When duplicates occur, we only award the first report that was received (provided that it can be fully reproduced).\n* Multiple vulnerabilities caused by one underlying issue will be awarded one bounty.\n* Social engineering (e.g. phishing, vishing, smishing) is prohibited.\n* 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.\n \n# Out of scope vulnerabilities\n\n### When reporting vulnerabilities, please consider (1) attack scenario / exploitability, and (2) security impact of the bug. The following issues are considered out of scope:\n\n* Clickjacking on pages with no sensitive actions\n* Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions\n* Attacks requiring MITM or physical access to a user's device.\n* Previously known vulnerable libraries without a working Proof of Concept.\n* Comma Separated Values (CSV) injection without demonstrating a vulnerability.\n* Missing best practices in SSL/TLS configuration.\n* Any activity that could lead to the disruption of our service (DoS).\n* Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS\n* Rate limiting or bruteforce issues on non-authentication endpoints\n* Missing best practices in Content Security Policy.\n* Missing HttpOnly or Secure flags on cookies\n* Missing email best practices (Invalid, incomplete or missing SPF/DKIM/DMARC records, etc.)\n* Vulnerabilities only affecting users of outdated or unpatched browsers [Less than 2 stable versions behind the latest released stable version]\n* Duplicate reported vulnerabilities from other reports or submissions that have yet to be resolved\n* Software version disclosure / Banner identification issues / Descriptive error messages or headers (e.g. stack traces, application or server errors).\n* Public Zero-day vulnerabilities that have had an official patch for less than 1 month will be awarded on a case by case basis.\n* Tabnabbing\n* Open redirect - unless an additional security impact can be demonstrated\n* Broken external links\n* Clickjacking within a NFT displayed on Magic Eden\n* Chain specific vulnerabilities are excluded, (e.g. EVM or Solana runtime issues)\n* Issues that require unlikely user interaction\n* Issues that depend on third-party services or out of scope assets\n\n\n# Safe Harbor\nAny 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.\n\nThank you for helping keep Magic Eden and our users safe!\n","has_open_scope":null,"pays_within_one_month":null,"protected_by_gold_standard_safe_harbor":null,"protected_by_ai_safe_harbor":null,"disclosure_declaration":null,"introduction":null,"platform_standards_exclusions":[],"exemplary_standards_exclusions":[],"scope_exclusions":[],"timestamp":"2023-01-13T19:06:59.101Z"},{"id":3680252,"new_policy":"Magic Eden looks forward to working with the security community to find vulnerabilities in order to keep our businesses and customers safe.\n\n# Response Targets\nMagic Eden will make a best effort to meet the following SLAs for hackers participating in our program:\n\n| Type of Response | SLA in business days |\n| ------------- | ------------- |\n| First Response | 2 days |\n| Time to Triage | 4 days |\n| Time to Bounty | 14 days |\n| Time to Resolution | depends on severity and complexity |\n\nWe’ll try to keep you informed about our progress throughout the process.\n\n# Disclosure Policy\n* Please do not discuss this program or any vulnerabilities (even resolved ones) outside of the program without express consent from the organization.\n* Follow HackerOne's [disclosure guidelines](https://www.hackerone.com/disclosure-guidelines).\n\n\n# Program Rules\nPlease 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.\n* Do not impact production systems in a negative way for any testing\n* All smart contract testing should be done with a forked local copy of mainnet\n* Submit one vulnerability per report, unless you need to chain vulnerabilities to provide impact.\n* When duplicates occur, we only award the first report that was received (provided that it can be fully reproduced).\n* Multiple vulnerabilities caused by one underlying issue will be awarded one bounty.\n* Social engineering (e.g. phishing, vishing, smishing) is prohibited.\n* 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.\n \n# Out of scope vulnerabilities\n\n### When reporting vulnerabilities, please consider (1) attack scenario / exploitability, and (2) security impact of the bug. The following issues are considered out of scope:\n\n* Clickjacking on pages with no sensitive actions\n* Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions\n* Attacks requiring MITM or physical access to a user's device.\n* Previously known vulnerable libraries without a working Proof of Concept.\n* Comma Separated Values (CSV) injection without demonstrating a vulnerability.\n* Missing best practices in SSL/TLS configuration.\n* Any activity that could lead to the disruption of our service (DoS).\n* Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS\n* Rate limiting or bruteforce issues on non-authentication endpoints\n* Missing best practices in Content Security Policy.\n* Missing HttpOnly or Secure flags on cookies\n* Missing email best practices (Invalid, incomplete or missing SPF/DKIM/DMARC records, etc.)\n* Vulnerabilities only affecting users of outdated or unpatched browsers [Less than 2 stable versions behind the latest released stable version]\n* Software version disclosure / Banner identification issues / Descriptive error messages or headers (e.g. stack traces, application or server errors).\n* Public Zero-day vulnerabilities that have had an official patch for less than 1 month will be awarded on a case by case basis.\n* Tabnabbing\n* Open redirect - unless an additional security impact can be demonstrated\n* Broken external links\n* Clickjacking within a NFT displayed on Magic Eden\n* Chain specific vulnerabilities are excluded, (e.g. EVM or Solana runtime issues)\n* Issues that require unlikely user interaction\n* Issues that depend on third-party services or out of scope assets\n\n\n# Safe Harbor\nAny 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.\n\nThank you for helping keep Magic Eden and our users safe!\n","has_open_scope":null,"pays_within_one_month":null,"protected_by_gold_standard_safe_harbor":null,"protected_by_ai_safe_harbor":null,"disclosure_declaration":null,"introduction":null,"platform_standards_exclusions":[],"exemplary_standards_exclusions":[],"scope_exclusions":[],"timestamp":"2022-11-23T14:28:47.004Z"},{"id":3680251,"new_policy":"Magic Eden looks forward to working with the security community to find vulnerabilities in order to keep our businesses and customers safe.\n\n# Response Targets\nMagic Eden will make a best effort to meet the following SLAs for hackers participating in our program:\n\n| Type of Response | SLA in business days |\n| ------------- | ------------- |\n| First Response | 2 days |\n| Time to Triage | 4 days |\n| Time to Bounty | 14 days |\n| Time to Resolution | depends on severity and complexity |\n\nWe’ll try to keep you informed about our progress throughout the process.\n\n# Disclosure Policy\n* As this is a private program, please do not discuss this program or any vulnerabilities (even resolved ones) outside of the program without express consent from the organization.\n* Follow HackerOne's [disclosure guidelines](https://www.hackerone.com/disclosure-guidelines).\n\n\n# Program Rules\nPlease 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.\n* Do not impact production systems in a negative way for any testing\n* All smart contract testing should be done with a forked local copy of mainnet\n* Submit one vulnerability per report, unless you need to chain vulnerabilities to provide impact.\n* When duplicates occur, we only award the first report that was received (provided that it can be fully reproduced).\n* Multiple vulnerabilities caused by one underlying issue will be awarded one bounty.\n* Social engineering (e.g. phishing, vishing, smishing) is prohibited.\n* 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.\n \n# Out of scope vulnerabilities\n\n### When reporting vulnerabilities, please consider (1) attack scenario / exploitability, and (2) security impact of the bug. The following issues are considered out of scope:\n\n* Clickjacking on pages with no sensitive actions\n* Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions\n* Attacks requiring MITM or physical access to a user's device.\n* Previously known vulnerable libraries without a working Proof of Concept.\n* Comma Separated Values (CSV) injection without demonstrating a vulnerability.\n* Missing best practices in SSL/TLS configuration.\n* Any activity that could lead to the disruption of our service (DoS).\n* Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS\n* Rate limiting or bruteforce issues on non-authentication endpoints\n* Missing best practices in Content Security Policy.\n* Missing HttpOnly or Secure flags on cookies\n* Missing email best practices (Invalid, incomplete or missing SPF/DKIM/DMARC records, etc.)\n* Vulnerabilities only affecting users of outdated or unpatched browsers [Less than 2 stable versions behind the latest released stable version]\n* Software version disclosure / Banner identification issues / Descriptive error messages or headers (e.g. stack traces, application or server errors).\n* Public Zero-day vulnerabilities that have had an official patch for less than 1 month will be awarded on a case by case basis.\n* Tabnabbing\n* Open redirect - unless an additional security impact can be demonstrated\n* Broken external links\n* Clickjacking within a NFT displayed on Magic Eden\n* Chain specific vulnerabilities are excluded, (e.g. EVM or Solana runtime issues)\n* Issues that require unlikely user interaction\n* Issues that depend on third-party services or out of scope assets\n\n\n# Safe Harbor\nAny 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.\n\nThank you for helping keep Magic Eden and our users safe!\n","has_open_scope":null,"pays_within_one_month":null,"protected_by_gold_standard_safe_harbor":null,"protected_by_ai_safe_harbor":null,"disclosure_declaration":null,"introduction":null,"platform_standards_exclusions":[],"exemplary_standards_exclusions":[],"scope_exclusions":[],"timestamp":"2022-11-23T14:27:09.625Z"}]