For Security Researchers
For Customers: Reporting Suspicious Emails
Customers who think they have received a Phishing email, please learn more about phishing at https://cms.paypal.com/us/cgi-bin/marketingweb?cmd=_render-content&content_ID=security/hot_security_topics, or forward it to: firstname.lastname@example.org
For Customers: Reporting All Other Concerns
Customers who have issues with their PayPal Account, please visit: https://www.paypal.com/cgi-bin/helpscr?cmd=_help&t=escalateTab
For Professional Researchers: Bug Bounty Program
Our team of dedicated security professionals works vigilantly to help keep customer information secure. We recognize the important role that security researchers and our user community play in also helping to keep PayPal and our customers secure. If you discover a site or product vulnerability please notify us using the guidelines below.
Please note that your participation in the Bug Bounty Program is voluntary and subject to the terms and conditions set forth on this page (“Program Terms”). By submitting a site or product vulnerability to PayPal, Inc. (“PayPal”) you acknowledge that you have read and agreed to these Program Terms.
These Program Terms supplement the terms of PayPal User Agreement, the PayPal Acceptable Use Policy, and any other agreement in which you have entered with PayPal (collectively “PayPal Agreements”). The terms of those PayPal Agreements will apply to your use of, and participation in, the Bug Bounty Program as if fully set forth herein. If there is any inconsistency exists between the terms of the PayPal Agreements and these Program Terms, these Program Terms will control, but only with regard to the Bug Bounty Program.
You can jump to particular sections of these Program Terms by using the following links:
Eligible Domains Policy
The following domains are included for the paypal.com family of companies:
The Bug Bounty Program is also valid on certain Partner Sites**, such as:
- www.paypal-__.com domains
- any PayPal-branded sites, including www.thepaypalblog.com and ppmts.custhelp.com
Please note that our partner sites (www.paypal-__.com) are mainly marketing based sites that are not part of the core PayPal customer domains (.paypal.com) and are managed by hosting vendor companies. They have variable timelines and are often decommissioned. A listing of these sites designated for deprecation will not be publically maintained due to frequent changes. When researching bugs on these sites, please keep this in mind as bug Submissions for sites on schedule for deprecation will not be honored.
Certain vulnerabilities are considered out-of-scope for the Bug Bounty Program. Those out-of-scope vulnerabilities include, but are not limited to:
- Vulnerabilities dependent upon social engineering techniques
- Denial of service
- Brute forcing
- Vulnerabilities in non-web applications
- Clickjacking on partner sites (i.e., www.paypal-__.com domains)
- Most vulnerabilities involving active content
- Most vulnerabilities within our sandbox and labs domains.
- Outdated Browsers: vulnerabilities contingent upon outdated or unpatched browsers will not be honored, including Internet Explorer versions prior to version 8.
- Information disclosure of public and information that do not present risk to our PayPal PayPal customers or PayPal, including:
- Web server type disclosure
- Access to web server files or directories that do not contain internal, confidential or restricted data.
- Server error messages that do not contain internal, confidential or restricted data or avenues to obtain it
Bug Bounty Payments Payout Ranges
You may be eligible to receive a monetary reward, or “bounty,” if: (i) you are the first person to submit a site or product vulnerability; (ii) that vulnerability is determined to by a valid security issue by PayPal’s security team; and (iii) you have complied with all Program Terms.
Bounty payments, if any, will be determined by PayPal, in PayPal’s sole discretion. In no event shall PayPal be obligated to pay you a bounty for any Submission. All bounty payments shall be considered gratuitous.
In the event PayPal elects to pay you a bounty, PayPal may make a partial payment when the vulnerability is first verified by PayPal and then an additional payment once the vulnerability has been fixed. The format and timing of all bounty payments shall be determined in PayPal’s sole discretion.
All bounty payments must be made to a verified PayPal Account in good standing. If you do not have a verified PayPal Account in good standing at the time of payment, you will not be eligible to receive a bounty.
All bounty payments will be made in United States dollars (USD). You will be responsible for any tax implications related to bounty payments you receive, as determined by the laws of your jurisdiction of residence or citizenship.
.paypal.com and PayPal subsidiary websites
Partner sites (www.paypal-__.com)
Remote Code Execution
Up to $10,000
Up to $5,000
Up to $3,000
Cross-Site Scripting (XSS)
Information Disclosure of Sensitive Data
Cross-Site Request Forgery (CSRF)#
Payout Ranges for paypal.com domains
Estimated payout ranges+ # (in USD) for in-scope vulnerabilities are as listed below. These payout rates apply to domains included under the paypal.com category of the Eligible Domains Policy.
+Payout ranges are based on the classification and sensitivity of the data impacted, ease of exploit and overall risk to PayPal customers, PayPal brand and determined to be a valid security issue by PayPal’s security engineers. Common sensitive data elements include customer social security number, credit card number, card verification code, bank account number, login credentials and passwords. PayPal may pay beyond the range at times when bugs are found to have significant risk.
#Please note that Clickjacking and CSRF vulnerabilities are only reviewed for sites and pages where the ease of exploit and risk to PayPal is significant. Also, please note that, while "Logout CSRF" is a well-acknowledged issue, there are other techniques (like "cookie forcing" and "cookie bombardment") that can make it futile to defend against this attack. Also, PayPal web sessions are relatively short lived and hence, the PayPal will not consider reports of the ability to log out users from PayPal as qualifying for a bounty.
In the event you breach any of these Program Terms or the terms and conditions of the PayPal Agreements, PayPal may immediately terminate your participation in the Bug Bounty Program and disqualify you from receiving any bounty payments.
Any information you receive or collect about PayPal or any PayPal user through the Bug Bounty Program (“Confidential Information”) must be kept confidential and only used in connection with the Bug Bounty Program. You may not use, disclose or distribute any such Confidential Information, including, but not limited to, any information regarding your Submission and information you obtain when researching the PayPal sites, without PayPal’s prior written consent.
In addition to any indemnification obligations you may have under the PayPal Agreements, you agree to defend, indemnify and hold PayPal, our parent, Affiliates and the officers, directors, agents, joint venturers, employees and suppliers of PayPal, our parent, or our Affiliates, harmless from any claim or demand (including attorneys’ fees) made or incurred by any third party due to or arising out of your Submissions, your breach of these Program Terms and/or your improper use of the Bug Bounty Program.
Relationship of the Parties
Nothing contained in this Agreement shall be construed as creating or implying a joint venture, partnership, agency, or employment relationship between you and PayPal.
Changes to Program Terms
The Bug Bounty Program is subject to change or cancellation by PayPal at any time, without notice. As such, PayPal may amend these Program Terms at any time by posting a revised version on our website. By continuing to participate in the Bug Bounty Program after PayPal posts any such changes, you accept the Program Terms, as modified.
Frequently Asked Questions
- The bug must be in scope of our program sites, within a category of vulnerabilities that are within program scope, and found to be a valid security issue by our security engineers. Your submission must be the first of its kind as duplicate submissions will be invalid.
- Payout ranges are based on the classification of the data impacted, ease of exploit and overall risk to PayPal customers and the PayPal brand. We may pay beyond the range at times when bugs are found to have significant risk. The amount of all bounty payments, if any, will be determined by PayPal, in PayPal’s sole discretion.
- If the bug you have reported was already submitted by another Researcher and found to be valid, we will not be able to honor similar bug submissions following that. We have had great participation from our research community. The growing volume of researchers will many times lead to duplicate bug findings. We must honor the first submission of its type and reject subsequent submissions.
- Besides the category of bug and the risk it presents, the type of information exposed is important when determining the severity. Confidential or restricted customer personal identifiable information (PII) exposed as well as the content sensitivity of the page are factors that can facilitate a higher bounty payout.
- Bugs that present negligible to no impact to our customers or company. Common examples include:
- Error messages void of sensitive data
- Web server type disclosure
- Clickjacking on pages without sensitive content, authentication, or state changing actions
- Most vulnerabilities within our sandbox and labs domains. Domains utilized by customers take precedence.
- Self-XSS scenarios that would require additional user interaction, including the user manually inputting the XSS payload.
- Please be aware of all program criteria and scope, as well as the Program Terms.
- Do not engage in testing that can impact our customers, like denial of service, social engineering or spam.
- When utilizing personal or test accounts, they are subject to our fraud controls and filters and may act upon irregular activity.
- A proof of concept consisting of detailed steps or screen shots is helpful in facilitation of review and eventual fix.