Bug Bounty Program

If you believe you have found a security vulnerability on Flippa, we encourage you to contact our Bug Bounty email group right away. We will investigate all legitimate reports and do our best to quickly fix the problem. Before reporting though, please review this page including our responsible disclosure policy, reward guidelines, and those things that should not be reported.

If you are looking to report another type of issue, please either Contact Support or please visit our Help Center for more information.

Focus areas

If you're planning to scan for vulnerabilities, there are a few particular areas we give priority to.

  1. Stored XSS or uncontrolled ability to modify site layout
  2. Privilege escalation
  3. SQL injection
  4. Verifying ownership of assets you do not control
  5. Bypassing email / phone verification or buyer certification
  6. Unauthorised access to resources (where such access is sensitive, such as information private to the seller, or a listing under NDA)
  7. Buying listings / upgrades without payment where it would otherwise be required

Ineligible Reports and False Positives

  1. Self-XSS.
  2. SPF configuration problems.
  3. CSRF with limited impact.
  4. Debug information.
  5. Rate limiting.
  6. SSL Pinning not applied.
  7. Any vulnerabilities for the Flippa blog that don't result in privilege escalation or post mutation.
  8. Security header misconfiguration.
  9. Mixed HTTP/HTTPs content.
  10. Session fixation.
  11. Spam or social engineering techniques.
  12. Denial-of-service attacks.
  13. Accessing content via raw image URLs from our CDN (Content Delivery Network).
  14. Password reset link practices

Responsible Disclosure Policy

If you comply with the policies below when reporting a security issue to Flippa, we will not initiate a lawsuit or law enforcement investigation against you in response to your report. We ask that:

  1. You give us reasonable time to investigate and mitigate an issue you report before making public any information about the report or sharing such information with others.
  2. You do not interact with an individual account (which includes modifying or accessing data from the account) if the account owner has not consented to such actions.
  3. You make a good faith effort to avoid privacy violations and disruptions to others, including (but not limited to) destruction of data and interruption or degradation of our services.
  4. You do not exploit a security issue you discover for any reason. (This includes demonstrating additional risk, such as attempted compromise of sensitive company data or probing for additional issues.)
  5. You do not violate any other applicable laws or regulations.

Bug Bounty Program Terms

We recognize and reward security researchers who help us keep people safe by reporting vulnerabilities in our services. Monetary bounties for such reports are entirely at Flippa’s discretion, based on risk, impact, and other factors. To potentially qualify for a bounty, you first need to meet the following requirements:

  1. Adhere to our Responsible Disclosure Policy (see above).
  2. Report a security bug: that is, identify a vulnerability in our services or infrastructure which creates a security or privacy risk. (Note that Flippa ultimately determines the risk of an issue, and that many software bugs are not security issues.)
  3. Your report must describe a problem involving our product or service.
  4. We specifically exclude certain types of potential security issues; these are listed under “Ineligible Reports and False Positives” (see below).
  5. Submit your report to our Bug Bounty email group with the subject of Bug Report (one issue per report) and respond to the report with any updates. Please do not contact employees directly or through other channels about a report.
  6. If you inadvertently cause a privacy violation or disruption (such as accessing account data, service configurations, or other confidential information) while investigating an issue, be sure to disclose this in your report.
  7. Use test accounts when investigating issues. If you cannot reproduce an issue with a test account, you can use a real account (except for automated testing). Minimize the amount of test accounts created if possible. Contact Support if you are having trouble with accessing your test accounts
  8. Do not buy or sell on the marketplace or interact with other accounts without consent.

In turn, we will follow these guidelines when evaluating reports under our bug bounty program:

  1. We investigate and respond to all valid reports. We do however prioritize evaluations based on risk and other factors, and it may take some time before you receive a reply.
  2. We determine bounty amounts based on a variety of factors, including (but not limited to) impact, ease of exploitation, and quality of the report. If we pay a bounty, the minimum reward is $100 USD. Note that extremely low-risk issues may not qualify for a bounty at all.
  3. We seek to pay similar amounts for similar issues, but bounty amounts and qualifying issues may change with time. Past rewards do not necessarily guarantee similar results in the future.
  4. In the event of duplicate reports, we award a bounty to the first person to submit an issue. (Flippa determines duplicates and may not share details on the other reports.) A given bounty is only paid to one individual.
  5. We reserve the right to publish reports (and accompanying updates).
  6. We verify that all bounty awards are permitted by applicable laws, including (but not limited to) US trade sanctions and economic restrictions.

Note that your use of the Flippa platform and services including for purposes of this program, is subject to Flippa’s Terms and Policies. We may retain any communications about security issues you report for as long as we deem necessary for program purposes, and we may cancel or modify this program at any time.

Attributes of a Good Report

Detailed steps in your message explaining how to reproduce the bug. This should include any links you clicked on, pages you visited, URLs, user IDs, etc. Images and video can be helpful if you also include written explanations.

  1. Clear descriptions of any accounts used in your report and the relationships between them. Please do not use the same name on multiple accounts to avoid confusion.
  2. Quality before quantity. Many of our highest-paid reports had just a few lines of precise, clear explanations.

If you send a video, consider these tips:

  1. Keep it short by showing only the parts necessary to demonstrate the bug once. (Remove or redo mistakes that might happen while recording.)
  2. Record at a resolution where text or URLs are readable (at least 480p; 1080p is usually not necessary).
  3. Provide commentary or instructions in your messages or video description instead of typing on-screen during the video.
  4. If a large amount of text appears in your video, please include a copy in your messages as well.
  5. Keep the video private either by uploading it as an attachment or posting it privately online (such as with a hidden link or password that you send to us).