Identify vulnerabilities and be Rewarded!

ZETRIX is committed to protecting our
users data by safeguarding their
information from unwarranted disclosure.

Identify vulnerabilities and be Rewarded!

ZETRIX is committed to protecting our users data by safeguarding their information from unwarranted disclosure.

Quick View

Scope of Policy

This policy applies to the following systems and services that handles sensitive user data. This includes:


  • ZETRIX-owned production web domains, such as: *.zetrix.com


Any service which is not listed here are considered out-of-scope and are not authorized for testing. The scope of the ZETRIX system and services covered by this policy will be periodically updated. If vulnerability discovered in third-party asset, the security researcher should report directly to the vendor in accordance with vendor disclosure policy (if any). If a security researcher aren’t sure whether a system is in scope or not, please contact us at [email protected]

Quick View

Scope of Policy

This policy applies to the following systems and services that handles sensitive user data. This includes:


  • ZETRIX-owned web domains, such as: *.zetrix.com


Any service which is not listed here are considered out-of-scope and are not authorized for testing. The scope of the ZETRIX system and services covered by this policy will be periodically updated. If vulnerability discovered in third-party asset, the security researcher should report directly to the vendor in accordance with vendor disclosure policy (if any). If a security researcher aren’t sure whether a system is in scope or not, please contact us at [email protected]

Quick View

Code of Conduct


By participating in ZETRIX VDP programme, security researchers agree to adhere with ZETRIX Code of Conduct (CoC), listed as below:

  1. Report vulnerabilities immediately after discovery.
  2. Only contact ZETRIX security team through approved channels and respect the request of ZETRIX security team.
  3. Do not perform unsafe testing without prior authorization
  4. Do not disclose report information, confidential information or personal data of our users without our consent. Respect our privacy.
  5. Do not violate any laws or regulations to conduct vulnerability research
  6. Do not store, save, or generally abuse any sensitive data exposed by your research
  7. Avoid disrupting our services in the course of your investigation
  8. Extortion and blackmail is prohibited. Any attempt to obtain bounties, money or services by coercion may amount to a criminal offense.

General Guidelines


  • Report any suspected or confirmed vulnerability you discovered immediately via [email protected]
  • Please provide detailed reports with steps that can be replicated. The issue may be closed as Information or N/A if the report isn't thorough enough to duplicate the problem.
  • Multiple vulnerabilities caused by the same underlying issue will be regarded as one; the initial report will be triaged as the original, and all subsequent reports will be closed as duplicates.
  • Social engineering (e.g. phishing, vishing, smishing) is prohibited.
  • Do not intentionally view, store, modify, or destroy data that does not belong to you.
  • Avoid perform denial of service attacks, or any attacks that have a reasonable chance of degrading ZETRIX’s service or user experience.
  • Make a good faith attempt to avoid data loss, privacy violations, and service interruptions or degradation. Only engage with accounts that you own or have specific authorization to interact with.
  • Provide us with a reasonable amount of time to remediate vulnerabilities.

Non-Qualifying Vulnerabilities


To report vulnerability, security researcher are required to consider (1) attack scenario/exploitability and the (2) security impact of the bug. Any of the following actions could result in permanent exclusion from the disclosure programme, as well as a criminal and/or legal investigation.

We do not tolerate any behaviors that may negatively damage other ZETRIX users' experiences on our system and services. We accept only manual or semi-manual tests. All findings coming from automated tools or scripts will be considered out of scope.

  • Attacks designed or likely to degrade, deny, or adversely impact services or user experience (e.g., Denial of Service, Distributed Denial of Service, Brute Force, Password Spraying, Spam…).
  • Attacks designed or likely to destroy, corrupt, make unreadable (or attempts therein) data or information that does not belong to you.
  • Intentionally accessing data or information that does not belong to you beyond the minimum viable access necessary to demonstrate the vulnerability.
  • Performing physical, social engineering, or electronic attacks against our personnel, offices, wireless networks, or property.
  • Security issues in third-party applications, services, or dependencies that integrate within the products or infrastructure that do not have demonstrable proof of concept for the vulnerability (e.g., libraries, SAAS services).
  • Security issues or vulnerabilities created or introduced by the reporter (e.g., modifying a library we rely on to include a vulnerability for the sole purpose of receiving a recognition).
  • Attacks performed on any systems not explicitly mentioned as authorized and in-scope.
  • Reports of missing “best practices” or other guidelines which do not indicate a security issue.
  • Attacks related to email servers, email protocols, email security (e.g., SPF, DMARC, DKIM), or email spam.
  • Missing cookie flags on non-sensitive cookies.
  • Reports of insecure SSL/TLS ciphers (unless accompanied by working proof of concept).
  • Reports of how you can learn whether a given client can authenticate to a product or service.
  • Reports of mappings between code names and client names.
  • Reports of simple IP or port scanning.
  • Missing HTTP headers (e.g. lack of HSTS).
  • Email security best practices or controls (e.g. SPF, DKIM, DMARC).
  • Software or infrastructure bannering, fingerprinting, or reconnaissance with no proven vulnerability.
  • Clickjacking or self-XSS reports.
  • Reports of publicly resolvable or accessible DNS records for internal hosts or infrastructure.
  • Domain-based phishing, typosquatting, punycodes, bitflips, or other techniques.
  • Violating any laws or breaching any agreements (or any reports of the same).


Eligible Findings


The following classes of vulnerabilities are of particular interest to us, and are eligible for attribution upon review:

  • Remote Code Execution (RCE)
  • SQL injection
  • XML External Entity Injection (XXE)
  • Authorization bypass/escalation
  • Sensitive information leaks
  • Cross-site scripting (XSS)
  • Cross-site request forgery (CSRF)
  • Business logic Vulnerabilities (with Impact)

Reward Conditions and Tiers


ZETRIX may offer monetary recognition for vulnerability reports that have a significant business impact on our users, products, or services. Rewards for qualifying findings will range from ZTX 100 to ZTX 10,000 in appreciation for your help.

Note. ZTX is a ZETRIX issued native currency

Eligibility for monetary recognition is determined by calculating the internal severity of a finding against the potential impact to ZETRIX and its userbase. We reserve the right, in our sole discretion, to determine vulnerability qualification for a monetary reward.

The following rules apply if the issue is deemed to be valid and significant:

  1. You must agree and adhere to the Programme Rules as stated previously.
  2. You must be the first person to report the issue to us and provide a comprehensive report. We will review duplicate issues based on completeness of information provided, but priority lays with first reporter.
  3. You must be available to supply additional information as needed by our team to reproduce and triage the issue.
  4. The existence of a vulnerability in multiple applications will be factored into a recognition decision; duplicate reports will be closed without recognition.
  5. We provide a reward at the time of fix based on ZTX, Zetrix's native currency.

MEDIOCRE BUG

Earn 100 - 500 ZTX coins

SEVERITY OF VULNERABILITY

  • Low impact, medium likelihood
  • Medium impact, low likelihood

SUBSTANTIAL BUG

Earn 500 - 1,000 ZTX coins

SEVERITY OF VULNERABILITY

  • High impact, low likelihood
  • Medium impact, medium likelihood
  • Low impact, high likelihood

CRITICAL BUG

Earn 1,000 - 2,000 ZTX coins

SEVERITY OF VULNERABILITY

  • High impact, high likelihood

Reporting Requirements


Security researchers are recommended to share details of any suspected vulnerabilities across any asset owned, controlled, or operated by ZETRIX (or identified as giving a security impact to the ZETRIX and our user) via electronic mail [email protected] and include the following information in your report:

  1. A brief description of the issue and all instances or endpoints at which it is located.
  2. Attack scenario/exploitability, and the security impact of the bug.
  3. Screenshots and/or videos demonstrating the issue.
  4. Step-by-step instructions on how to reproduce the issue, including any exploit code.
  5. Operating system and/or version information, if relevant.
  6. If applicable, a log of all activity related to your discovery, including your IP address(es) and timestamped requests to aid us in validation and investigation.

Disclaimer: In regards to the above, please note the following:

  • Do not upload screenshots, videos, or exploit code to a publicly accessible server/repository in preparation of your email.
  • Do not zip or archive your files (just attach them directly to the email).
  • Very low-quality reports such as those which only contain automated output will be rejected.

If necessary, you may use our PGP public key to encrypt your communication with us.

Reports may be submitted anonymously. Alternatively, a security researcher may provide contact information as well as any preferred communication methods or times of day to communicate, as they see fit.

Response Target


ZETRIX will make a best effort to meet the following response targets for security researcher participating in our programme:

  • Time to first response - 3 business days
  • To the best of our ability, we will confirm the existence of the vulnerability to you and be as transparent as possible about what steps we are taking during the remediation process, including on issues or challenges that may delay resolution.

* ZETRIX calculates severity based on CVSS 3.0, business impact and environment

Safe Harbor


Testing activities conducted in accordance with the ZETRIX VDP programme regulation are protected by Safe Harbor, meaning we will not initiate legal action against you. However, if you violate the rules, ZETRIX retains all other rights and remedies available to it at law, including the rights to seek legal action or law enforcement notice. Security researcher are expected, to comply with all laws applicable to you, and not to disrupt or compromise any data beyond what our VDP programs permit.

Thank you for helping us keep Zetrix's user and data safe.

Copyright (C) 2023 Zetrix. All Rights Reserved.