How to make money on facebook by reporting bugs in 2023

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

• You give us reasonable time to investigate and mitigate an issue that you report before making any information about the report public or sharing such information with others.
• 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.
• You make a good faith effort to avoid privacy violations and disruptions to others, including (but not limited to) unauthorised access to or destruction of data, and interruption or degradation of our services.
• You do not exploit a security issue that you discover for any reason. (This includes demonstrating additional risk, such as attempted compromise of sensitive company data or probing for additional issues.)
• You do not intentionally violate any other applicable laws or regulations, including (but not limited to) laws and regulations prohibiting the unauthorised access to data.
• For the purposes of this policy, you are not authorised to access user data or company data, including (but not limited to) personally identifiable information and data relating to an identified or identifiable natural person.

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

• Adhere to our responsible disclosure policy (see above).
• Report a security bug: identify a vulnerability in our services or infrastructure which creates a security or privacy risk. (Note that Facebook ultimately determines the risk of an issue, and that many software bugs are not security issues.)
• Your report must describe a problem involving one of the products or services listed under “Bug bounty programme scope” (see below).
• We specifically exclude certain types of potential security issues; these are listed under “Out of scope and false positives” (see below).
• Submit your report via our “Report a security vulnerability” form (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.
• If you inadvertently cause a privacy violation or disruption (such as accessing account data, service configurations or other confidential information) while investigating an issue, you must disclose this in your report.
• 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). Do not interact with other accounts without consent (e.g. do not test against Mark Zuckerberg’s account).

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

• We investigate and respond to all valid reports. Due to the volume of reports that we receive, however, we prioritise evaluations based on risk and other factors, and it may take some time before you receive a reply.
• 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 USD 500. Note that extremely low-risk issues may not qualify for a bounty at all.
• We aim to pay similar amounts for similar issues, but bounty amounts and qualifying issues may change over time. Past rewards do not necessarily guarantee similar results in the future.
• In the event of duplicate reports, we award a bounty to the first person to submit an issue. (Facebook determines duplicates and may not share details on the other reports.) A given bounty is only paid to one individual.
• You may donate a bounty to a recognised charity (subject to approval by Facebook) and we double bounty amounts that are donated in this way.
• We reserve the right to publish reports (and accompanying updates).
• We publish a list of researchers who have submitted valid security reports. You must receive a bounty to be eligible to be included in this list, but your participation is then optional. We reserve the right to limit or modify the information accompanying your name in the list.
• We verify that all bounty awards are permitted by applicable laws, including (but not limited to) US trade sanctions and economic restrictions.

From time to time, Facebook may offer promotions in connection with the Bug bounty programme. Reports submitted according to these terms may be subject to additional governing rules for that promotion as described in those rules, which are or will be made available here and are incorporated into these terms through this reference: https://www.facebook.com/whitehat/promotion/.

Note that your use of Facebook services and the services of any member of the Facebook family of companies, including for the purposes of this programme, is subject to Facebook’s Terms and Policies and the terms and policies of any member of the Facebook family of companies whose services you use. We (and any member of the Facebook family of companies that is the subject of your report) may retain any communications about security issues that you report for as long as we deem necessary for programme purposes, and we may cancel or modify this programme at any time.

To qualify for a bounty, report a security bug in Facebook or one of the following qualifying products or acquisitions:

• Instagram
• Internet.org/Free Basics
• Oculus
• Onavo
• Open source projects by Facebook (e.g. osquery)
• WhatsApp

also read 6 ways to promote your small business on Facebook

Note that services not owned by Facebook (e.g. WordPress VIP and Page.ly) are not eligible under our bug bounty programme. While we often care about vulnerabilities affecting services that we use, we cannot guarantee that our disclosure policies apply to services from other companies.

Please also note that vulnerabilities in third-party apps or websites that integrate with Facebook (including most pages on apps.facebook.com) are generally not within the scope of our bug bounty programme. Currently, the only exception is for security bugs resulting in the exposure of Facebook user access tokens to unauthorised entities. We will accept reports of such vulnerabilities, but only if the bug is discovered by passively viewing the data sent to or from your device while using the app or website. You are not permitted to manipulate any request sent to the app or website from your device or otherwise interfere with the ordinary functioning of the app or website in connection with submitting your report. (For example, SQLi, XSS, open redirect or permission-bypass vulnerabilities (such as IDOR) are strictly out of scope.) Furthermore, you may not access data or use any access token from any Facebook account other than your own. Finally, only third-party apps with at least 50,000 active users are within scope.

Out of scope

False positives