Goldman Sachs

Maintaining the security of our applications and networks is a high priority for Goldman Sachs. If you have information related to security vulnerabilities of GS products and services, please submit a report in accordance with the guidelines below.
The vulnerabilities identified in the HackerOne reports will be classified by the degree of risk as well as the impact they present to the host system, this includes the amount and type of data exposed, privilege level obtained, proportion of systems or users affected.

Do not try to further pivot into the network by using a vulnerability. The rules around Remote Code Execution (RCE), SQL Injection (SQLi), vulnerabilities allowing you to access file/folder structure, defacement and file uploads are listed below.

Do not try to exploit service providers we use (hosting, domain registrar, email, marketing, etc.). The Firm does not authorize you to perform any actions against non-GS owned property/system/service/data. If you are unsure if a system you discovered belongs to Goldman Sachs or not, ask first before testing further.

If you encounter Personally Identifiable Information (PII) contact us at [email protected] immediately. Do not proceed with access and immediately purge any local information, if applicable.

Please limit any automated scanning to 60 requests per second. Aggressive testing that causes service degradation will be grounds for removal from the program.

Thank you for helping keep Goldman Sachs and our users safe!

Program Rules

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. Providing clear and concise steps to reproduce the issue will help to expedite the response. As a bare minimum, please include in your report:

• The URL and any affected parameters
• The browser, OS, and/or app version
• The perceived impact. How could the bug potentially be exploited?
• 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.
• Only interact with accounts you own or with explicit permission of the account holder AND Goldman Sachs. Please reach out to [email protected] with any questions.
• If you inadvertently gain access to an account you do not own, please cease testing immediately and submit a report for Goldman Sachs to validate further. Do not attempt to prove higher impact by downloading data or by modifying any settings
• By default, the report should clearly reference your @wearehackerone.com email alias address where possible.

Register accounts using your @wearehackerone.com addresses. To create additional accounts please use '+N' with your email address: [email protected], [email protected] etc.

• Per our Rewards section below, the addition of the following custom headers along with your public IP is required to qualify you for a bonus on valid triaged reports(Burp and other proxies allow the easy automatic addition of headers to all outbound requests):

• Do not try to further pivot into the network by using a vulnerability. The rules around RCE, SQLi, vulnerabilities allowing you to access file/folder structure, defacement and file-uploads are listed below.
• Do not try to exploit service providers we use (hosting, domain registrar, email, marketing, etc.). The Firm does not authorize you to perform any actions against non-GS owned property/system/service/data. If you are unsure if a system you discovered belongs to Goldman Sachs or not, ask first before testing further.
• Zero-day, recently disclosed vulnerabilities, and vulnerabilities that do not have an official patch may not be eligible for a monetary reward. A vulnerability is considered recently disclosed if it was publicly disclosed, or a vendor patch was released, within the ninety (90) days prior to your submission. Reports of this nature will be evaluated on a case-by-case basis, and a reward may be granted where the report provides meaningful new value to Goldman Sachs' remediation efforts. This position is recorded under HackerOne Platform Standards Deviations.
• If you encounter Personally Identifiable Information (PII) contact us at [email protected] immediately. Do not proceed with access, do not upload PII, and immediately purge any local information, if applicable.
• Please limit any automated scanning to 60 requests per second. Aggressive testing that causes service degradation will be grounds for removal from the program.
• For any vulnerability (including RCE, XXE, LFI, Path Traversal etc.) that might allow you to read underlying file/ folder structure, it is prohibited to read sensitive files (eg /etc/shadow) and/or snooping through the file/folder structure.
• For Subdomain Takeovers (SDTO) you must demonstrate that you have taken over the domain and that it is still in your possession to avoid false positives and claim-jumping. A valid Proof of Concept html file hosted by you on the site with your HackerOne username is required, preferably in a sub-directory. SDTO reports without a working proof of concept confirming you have control over the subdomain in question will be closed as N/A.
• The program does not forbid researchers from using AI/Large-Language-Model (LLM) assisted tooling in their reports. However, researchers should be careful to manually ensure all of their report's content is complete and contains sufficient evidence for our triagers to reproduce and validate. If researchers fail to provide informative content, the program may classify their reports as Spam.

#Eligibility Guidelines To be eligible to participate in the Goldman Sachs Bug Bounty Program, you must:

• Be at least 18 years old.
• Agree and adhere to the Program Rules and Legal terms as stated in this policy.
• Be the first to submit a sufficiently reproducible report for an issue in order to be eligible for a bounty.
• Assist the Goldman Sachs team in reproducing and triaging the issue, and to provide additional information as needed.
• Not be employed by Goldman Sachs or be employed by 3rd parties managing digital assets in use by Goldman Sachs.
• Not be a resident of, or make submissions from, a country against which the United States has issued export sanctions or other trade restrictions.
• Not be in violation of any national, state, or local law or regulation with respect to any activities directly or indirectly related to the Bug Bounty Program.
• Not be using duplicate HackerOne accounts.
• Out-of-scope vulnerability reports that pose a valid security impact may be addressed as a form of vulnerability disclosure but will generally not be considered eligible for a bounty.

Failure to meet the eligibility requirements above, any breach of the Golman Sachs Bug Bounty policy, or actions taken that adversely impact Goldman Sachs, our affiliates, or any of our users, employees, or agents, may lead to Goldman Sachs in our sole discretion, removing you from this program.

#**Rewards **

Goldman Sachs believes in rewarding findings based on their security impact regardless of the vulnerability class. As a general concept the vulnerabilities identified will be classified by the degree of risk as well as the impact they present to the host system, this includes the amount and type of data exposed, privilege level obtained, proportion of systems or users affected. Severity scores and reward amounts are calculated by evaluating two primary factors: Impact to our users and CVSS 3.0 base score. Please note that those two always work in tandem and a higher or lower CVSS score does not always qualify for a higher or lower reward amount. On the table above, you will find listed our reward structure and further below what usually falls under the 4 different impact classes.

Critical Impact

Critical Impact findings present a direct and immediate risk to Goldman Sachs or a majority of our users or customers. They often affect core/ critical components in production application stacks or infrastructure. Examples might include:

• Server Side Injections (RCE, Command Injections)
• SQLi

Note again that a finding falling under these examples doesn't automatically qualify for a critical bounty reward, the final decision is always based on the security impact of the issue.

High Impact

High impact findings usually materially impact several users/ customers or affect the security of the platform itself including the processes it supports. This would usually include the following types of issues:

• SSRF
• LFI
• XXE
• Significant Authentication Bypasses

Note again that a finding falling under these examples doesn't automatically qualify for a high bounty reward, the final decision is always based on the security impact of the issue.

Medium Impact

Medium impact findings typically materially impact a small number of our users/ customers and usually require little to no user interaction to trigger. They often result due to the following types of vulnerabilities:

• RFI
• Memory Leaks
• IDORs
• Stored XSS

Note again that a finding falling under these examples doesn't automatically qualify for a medium bounty reward, the final decision is always based on the security impact of the issue.

Low Impact

Based on how our apps are setup, low impact findings usually only affect a very small number of users or have a fairly limited security impact. These might include issues that require interaction or significant prerequisites to trigger. In our apps this would usually comprise of the below issues:

• Reflected XSS - In our apps, it is usually considered a low impact issue and is usually rewarded a standard $250
• Open Redirects - Similar to reflected XSS, open redirects might have a higher traditional cvss score, but in our apps, it is usually considered a low impact issue and usually rewarded a standard $250
• HTML Injection - In our apps, it is usually considered a low impact issue and are usually rewarded a standard $125

Informational Issues

These are usually best practices, mitigations, issues that are by design or acceptable business risk because of the way our apps are setup.

Notes:

• Some of our public applications share similar code bases and configurations, allowing a vulnerability found on one URL to exist on others. When the same fix addresses the issue in multiple places, only the first report is eligible for reward. However, additional reported instances might affect the severity of the issue and be eligible for discretionary bonuses. So, if you identify numerous instances of the same issue on multiple in-scope domains, we request that you submit a single report that documents the finding. Additional instances that are discovered later should also be added to the original report.

• Subdomain Takeover (SDTO) reports are evaluated based on severity, considering cookie scoping, historical significance, and potential traffic volume. The standard reward for such issues is $750. Valid SDTO reports on *.gs.com, *.marcus.com, *. goldman.com, *.gsam.com might be eligible for a reward up to $1,500 (note again that the actual reward may differ from these standards based on the impact of the finding)

• All submissions will be evaluated on a case-by-case basis by the Firm's BugBounty Rewards Panel. Please remember that as an example, executing RCE (Remote Code Execution/OS Command Injection) does not necessarily mean the impact is Critical. The Bug Bounty Panel will analyze the finding, evaluate the risk, and pay according to the reward schema, while taking the highest foreseen impact scenario into account. Reward amounts may vary depending upon the risk/impact of the vulnerability reported

##Monetary bonus for sharing AI Methodology As AI and Large Language Model (LLM) tooling becomes increasingly integrated into modern security research, Goldman Sachs is committed to understanding how these techniques contribute to the discovery of real-world vulnerabilities. To support this effort, we are introducing a $50 bonus on every valid, non-informational report that is accepted on the program in which the researcher voluntarily documents how they leveraged AI/LLMs during their research, via the dedicated "Researcher AI Methodology " custom field on the HackerOne submission form.

To qualify for the bonus, the disclosure should be specific to the vulnerability being reported and should provide meaningful insight into how AI tooling contributed to that particular finding. We suggest including:

• The AI or LLM tool(s) used (for example, a commercial assistant, an in-house model, or an AI-augmented testing tool).
• The stage(s) of research in which AI provided material assistance (for example, reconnaissance, endpoint or parameter enumeration, source code review, payload generation, or report drafting).
• The general prompting approach or workflow that led to the discovery.
• Any incorrect leads or hallucinated output produced by the AI tooling, and how the researcher recognized and worked past them to confirm the actual vulnerability.

For example, for a reflected XSS finding, a qualifying disclosure might explain that the researcher used a LLM to generate payload options for the reflection context they observed, note that some of the initial suggestions did not work (for example, payloads that assumed a filter which was not actually in place), and describe how the researcher/LLM spotted these false leads, adjusted their prompts, and confirmed a working payload against the target.

The bonus is awarded per report and rewards the specific insight the disclosure provides for that finding. Reusing the same methodology disclosure across multiple reports, or making only minor changes to it, will not qualify each additional report for the bonus.

Monetary bonus for IP Address and/or header identification:

There is a possibility that traffic generated by researchers can be categorized as malicious. Providing additional information allows us to identify your traffic. Researchers who are willing to put this information and provide it in a report will be eligible for a $50 bonus for every valid, accepted, non informational report when it is used during testing and it is mentioned in the report. This can be done by adding the following header to your request:

Mobile apps guidance

• Only use the latest official releases in the Play Store and App Store for testing.
• Only test backend domains listed as in-scope for the program.
• Applications developed and signed by Goldman Sachs must be up-to-date with the latest update.

Focus Areas:

• Unauthorized access to GS customer/user account
• Application compromise via physical access
• GS app attack via user installed legitimate/malicious application
• Application Login/Authentication Bypass
• Application Logic Bypass
• Authorization Bypass
• Insecure Access Controls
• Application Requests permissions that are overly privileged causing both privacy & security issues
• Sensitive user data / GS data extraction
• Exposed credentials/secret/hard-coded secrets on mobile apps which lead to leakage of sensitive user/GS data
• XSS, CSRF, directory traversal, Injection vulnerabilities that pose a valid risk
• Security issues that arise from misconfiguration or improper implementation of third-party SDK/framework/libraries/plugins may be considered as in scope under this program. Goldman Sachs is extremely interested in customer-controlled configuration and implementation choices we made that expose a vulnerability while vulnerabilities in the third-party components' source code itself or third-party external endpoints are not in scope.

Examples: IN SCOPE: Misconfigured security settings in a third-party authentication plugin OUT OF SCOPE: A vulnerability in the third-party plugin's core code OUT OF SCOPE: Vulnerabilities in external API endpoints operated by the third-party vendor

Safe Testing Guidance

###Safe AI usage policy

Use of AI and Large Language Model (LLM) assisted tooling is permitted within this program. Goldman Sachs recognizes that AI-assisted tools can support researchers throughout the discovery, analysis, and reporting process. Researchers electing to use such tooling are expected to observe the following standards:

• Researchers are fully responsible for the accuracy and integrity of all testing or content submitted, regardless of whether it was drafted or assisted by an AI tool. Every finding, reproduction step, payload, and impact assessment must be independently validated against the target prior to submission.
• Reports containing fabricated endpoints, non-existent parameters, invented CVEs, or otherwise unverified content generated by AI tooling will be closed as Not Applicable or Spam and may adversely affect the researcher's standing in the program.
• Submitting AI-assisted reports that do not show real security impact, are not properly verified, or otherwise do not add value to the program may lead to restrictions on future submissions, or removal from the program. When using third-party AI or LLM services, do not share with the model, information that identifies a Goldman Sachs asset or share specific details about a vulnerability finding on a Goldman Sachs asset. This includes in-scope domains, hostnames, IP addresses, URLs, request or response contents (including any source code, stack traces, or internal path information revealed in error messages), application source code, and screenshots. For example, if you are exploring a suspected XSS in an in-scope application, you may ask the AI to review or refine a payload in the abstract, but the target URL, parameters, and any response data captured from the Goldman Sachs application should be redacted or replaced with generic placeholders (for example, https://example.com/search?q=) before it is submitted to the tool.Credentials, session tokens, authentication material, personally identifiable information, customer data, and any other non-public information encountered during testing must not be submitted to third-party AI or LLM services in any form, whether directly, obfuscated, or as part of a larger prompt or attachment.
• AI-assisted reconnaissance and testing remain subject to all Program Rules, scope definitions, rate limits, and prohibited actions set out in this policy.

Remote Code Execution (RCE) Policy

Vulnerabilities which allow execution of code on the application server or shell command on the server itself should be run in accordance to this policy.

Prohibited actions when conducting RCE attempts:

• Altering or uploading files on the web server. (In case of file-upload functionality upload of webshells is prohibited, try uploading echo, info or any variable/info-based invocation code)
• Altering file permissions
• Reading sensitive files on the system (e.g /etc/shadow) and/or snooping through the file/folder structure (Same applies to XXE, LFI and Path Traversal, or any other vulnerability which allows you to read underlying file/folder structure)
• Altering/Modifying/Deleting any files on the system.
• Copying any files from the system and disclosing them to a non-GS site or entity
• Interacting with underlying OS-level data and/or databases.
• Interacting with other services running on the OS-level and/or any remote hosts residing on the network.
• Interrupting the normal operation of the server.
• Any type of establishment for persistent connection mechanisms (netcat, ssh reverse tunnel, etc) are prohibited.

Allowed actions when conducting RCE attempts - Unix:

• Executing 'ifconfig', 'hostname', 'whoami', 'uptime', 'top' or any metrics commands
• Reading content of the '/etc/passwd' file
• Using 'echo' to pipe characters into a file located in the "/tmp/", reading the file and then removing it right after confirmation.

Allowed actions when conducting RCE attempts - Windows:

• Executing ipconfig, hostname, whoami or any metrics commands
• Reading content of the drive:/boot.ini, drive:/install.ini or drive:/Windows/System32/drivers/etc/networks
• Using echo to pipe characters into a file located in the drive:/temp, reading the file (type) and then removing it right after confirmation.

SQL Injection (SQLi) Policy**

Vulnerabilities which allow injection of attacker controlled parts of the SQL query should be run in accordance to this policy. Prohibited actions when conducting SQLi attempts:

• Reading sensitive files on the system (e.g /etc/shadow) and/or snooping through the file/folder structure (SELECT LOAD_FILE)
• Reading specific sensitive database records
• Creating/Altering/Modifying/Deleting any files/records on the system/database. This includes use of INTO OUTFILE
• Command Execution (xp_cmdshell, uploading .so or any action that leads to command execution)
• Creating/Deleting Users
• Reading/Altering Username and Password information (includes password hashes)
• Interrupting the normal operation of the server and the database.

Allowed actions when conducting SQLi attempts:

• Executing SELECT queries such as: @@version; @@SERVERNAME; user(); system_user(); or database();
• Listing Databases names from schema, listing Columns, Table names
• Using Logic and time in Server Responses
• Using output responses
• Executing Mathematical, conversion or logical queries, such as:

1. ASCII Value -> Char SELECT char(65); # returns A
2. Char -> ASCII Value SELECT ascii('A'); # returns 65
3. String Concatenation SELECT CONCAT('A','B','C'); # returns ABC
4. Case Statement SELECT CASE WHEN (1=1) THEN 'A' ELSE 'B' END; # returns A)
5. Character Decoding SELECT 0x414243; # returns ABC)
6. Time Delay SELECT BENCHMARK(1000000,MD5('A')); SELECT SLEEP(5); )

File-Upload Policy

Vulnerabilities which allow upload of files through any means (e.g. PUT HTTP Method, File-upload functionality/module., etc.) are subjected to these rules

Prohibited actions when conducting File-upload attempts:

• Altering/Modifying/Deleting/Replacing any files on the system. (e.g. defacement)
• Uploading files to the account of a user which is not owned by you and you are not authorized by (does not apply to system users or web users like www-data e.g.)
• Uploading files which deliberately introduce additional exploitation vectors (e.g. html code with cross-site scripting code on it etc.)
• Uploading files which can cause Denial of Service (e.g. over-sized files or unlimited number of files resulting in running out of Disk Quota)

Allowed actions when conducting File-upload attempts:

• Chained exploitation vectors allowing you to jump out from the upload folder using e.g. path traversal or path manipulation that do not violate prohibited actions mentioned in File-Upload Policy.
• Upload of a file (any extension) with no content, simple string, integer or a special character.

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:

• Archived documents and files accessible via services like web.archive.org are temporarily out of scope for the program
• All Github/Gitlab/darkweb based credential leakage/information disclosure issues are temporarily out of scope. We monitor a lot of different sources like intelx.io, phonebook.cz etc. for leaked credentials, PII, financial information etc. As such, reports sharing a dump of leaked information from darkweb data aggregators like these do not provide value.

If you would still like to responsibly disclose any leaked passwords or sensitive information, please make sure to provide sufficient identifying information, but obfuscate all other sensitive information. eg: For leaked credentials, please share the username ([email protected]) but obfuscate the password (abc****)

• Any vulnerabilities for assets not owned, hosted or managed by Goldman Sachs are out of scope. Goldman Sachs does not authorize testing on any applications that are hosted by 3rd parties. Please reach out to the Goldman Sachs Bug Bounty team at [email protected] when in doubt about whether an asset is in scope.
• All Flash based vulnerabilities out of scope
• Reports from automated tools or scans
• Reports affecting outdated browsers
• Denial of Service Attacks
• Issues without clearly identified security impact (such as clickjacking on a static website) or speculative theoretical exploitability - for example using UXSS to steal the auth cookies, identifying Apache Tomcat 8.0.43 but not being able to perform any attack.
• Missing security best practices and controls (rate-limiting/throttling, lack of CSRF protection, lack of security headers, missing flags on cookies, descriptive errors, server/technology disclosure - without clear and working exploit)
• Lack of crossdomain.xml, p3p.xml, robots.txt or any other policy files and/or wildcard presence/misconfigurations in these.
• Use of a known-vulnerable libraries or frameworks - for example an outdated JQuery or AngularJS (without clear and working exploit)
• Self-exploitation (cookie reuse, self cookie-bomb, self denial-of-service etc.)
• Self Cross-site Scripting vulnerabilities without evidence on how the vulnerability can be used to attack another user
• Lack of HTTPS
• Reports about insecure SSL / TLS configuration
• Password complexity requirements, account/email enumeration, or any report that discusses how you can learn whether a given username or email address has a GS-related account
• Brute Forcing Login and/or Registration
• Presence/Lack of autocomplete attribute on web forms/password managers.
• Server Banner Disclosure/Technology used Disclosure
• Full Path Disclosure
• IP Address Disclosure
• CSRF on logout or insignificant functionalities
• Publicly accessible login panels
• Clickjacking
• CSS Injection attacks. (Unless it gives you ability to read anti-CSRF tokens or other sensitive information)
• Tabnabbing
• Host Header Injection (Unless it gives you access to interim proxies)
• Cache Poisoning
• Reflective File Download
• Cross-Origin Resource Sharing (CORS) Access-Control-Allow-Origin: * or accepting of custom Origin header that do not specifically show a valid attack scenario
• PRSSI - Path-relative stylesheet import vulnerabilities (without a impactful exploitation scenario - for example stealing CSRF-tokens)
• OPTIONS/TRACE/DELETE/PUT/WEBDAV or any other HTTP Methods accepted by the server which do not specifically show a valid attack scenario
• Cookie scoped to parent domain or anything related to the path misconfiguration and improperly scoped
• Private IP/Hostname disclosures or real IP disclosures for services using CDN
• Open ports which do not lead directly to a vulnerability
• Our policies on presence/absence of SPF / DKIM / DMARC records
• Lack of DNS CAA and DNS-related configurations
• Weak Certificate Hash Algorithm
• Vulnerabilities that require extensive user interaction or social engineering
• Social engineering of GS employees or contractors
• Any physical/wireless attempt against GS property or data centers
• Avoid all active testing on contact and registration forms, such as "Contact us", "Register for a Demo". These forms may generate emails that will affect the business.
• Do not try sending your commando-trained pigeons equipped with knowledge of RFC-2549 to sniff the traffic from our access points

On top of the above, the following items also are out-of-scope for mobile applications:

• Vulnerabilities that can only be exploited on a rooted, jailbroken, or device with intentionally reduced security controls are considered out of scope. Submissions will be rewarded only if the vulnerability exists and can be exploited on a non-jailbroken, non- rooted or non-modified device.
• Lack of / Incomplete certificate pinning
• Bugs that simply cause an app to crash without any security impact
• Exposure of non-sensitive data on the device
• Exposure of data via usage of overlays or accessibility services.

Public Disclosure Policy

• Goldman Sachs will not be publicly disclosing reports at this time. If and when Goldman Sachs does disclose a report, it will be mutually agreed upon with the hacker.
• Goldman Sachs reserves the right to deny any request for public disclosure. If a hacker publicly discloses without consent, they run the risk of a program ban.
• Follow HackerOne's disclosure guidelines.

Legal

• You must comply with all applicable Federal, State, and local laws in connection with your security research activities or other participation in this vulnerability disclosure program.
• You agree that You shall not, without the prior written consent of GS in each instance (i) use in advertising, publicity or otherwise the name of GS or its Affiliates or any trade name, trademark, trade device, service mark, symbol or any abbreviation, contraction or simulation thereof owned by GS or its Affiliates, or (ii) represent, directly or indirectly, any service or work provided by You as approved or endorsed by GS or its Affiliates.
• You agree that any and all information acquired or accessed by You as part of this exercise is confidential to GS and You shall hold the Confidential Information in strict confidence and shall not copy, reproduce, sell, assign, license, market, transfer or otherwise dispose of, give or disclose such information to third parties or use such information for any purposes other than for the performance of your work.
• You acknowledge and agree that any and all information you encounter is owned by GS or its third party providers, clients or customers. You have no rights, title or ownership to any information that you may encounter.
• GS may modify the terms of this policy or terminate the policy at any time.
• By clicking Submit Report, you consent to Your Information being transferred to and stored in the United States and acknowledge that you have read and accepted the Terms, Privacy Policy and Disclosure Guidelines presented to you when you created your account.
• Please use your own account for testing or research purposes. Do not attempt to gain access to another users account or confidential information.
• Please do not test for spam, social engineering or denial of service issues. Your testing must not violate any law, or disrupt or compromise any data that is not your own.

==Most Valuable Hacker (MVH) Recognition Program==

The Most Valuable Hacker (MVH) program recognizes security researchers who consistently demonstrate exceptional contributions to our security posture through high-impact, high-quality vulnerability reports and collaborative engagement throughout the remediation process.

Annual Recognition: Three researchers are honored annually for sustained excellence throughout the year. The top-ranked researcher is awarded a $2000 monetary bonus, the second-ranked researcher receives $1000, and the third-ranked researcher receives $500.

Quarterly Recognition: Three researchers are honored each quarter. The top-ranked researcher receives a $500 monetary bonus. The second and third-ranked researchers receive public recognition.

##Recognition Criteria: Researchers are evaluated based on: Impact: Severity and business criticality of identified vulnerabilities Quality: Thoroughness of reports, including detailed reproduction steps and remediation guidance Consistency: Regular submission of valid, actionable findings Collaboration: Professional communication and support during the vulnerability triage/Resolution process Volume: Number of valid and actionable security reports submitted through HackerOne

2026 Q2 Recognition:

1. @jamieparfet
2. @mut3d
3. @areebtanzeem

2026 Q1 Recognition:

1. @erickfernandox
2. @thaivu
3. @shabomala

2025 Annual Recognition:

1. @m0chan
2. @godiego
3. @medusa_, @sw33tlie, @bsysop