Cryptokek

Submit a Bug
22 January 2021
Live since
No
KYC required
$3,000
Maximum bounty

Program Overview

Cryptokek is a cryptocurrency analytics toolbox that provides unique data insights about cryptocurrencies. The focus of the Cryptokek bug bounty program is the API service at https://api.keks.app/ and the application at https://keks.app/.

Verification

Verification of Cryptokek's bug bounty program on Immunefi is available at

See verification

Rewards by Threat Level

Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System. This is a simplified 5-level scale, with separate scales for websites/apps and smart contracts/blockchains, encompassing everything from consequence of exploitation to privilege required to likelihood of a successful exploit.

Critical: Deletion of site data, XSS/CSRF, ACE

Payouts are handled by Cryptokek directly. Payouts are denominated in USD and are paid in KEK, ETH, or USDT/USDC (payments in currencies other than KEK may result in reduced bounty amounts)

Web and Apps

Critical
Level
up to USD $3,000
Payout

Assets in Scope

Please note that https://cryptokek.com/ and its subdomains are excluded from the Cryptokek bug bounty program.

App
Type
API
Type

Prioritized Vulnerabilities

Cryptokek is especially interested in receiving and rewarding vulnerabilities of the following types:

  • DOS
  • XSS
  • CSRF

Websites and Apps

  • Remote Code Execution
  • Vertical Privilege Escalation
  • XML External Entities Injection
  • Horizontal Privilege Escalation
  • Stored XSS
  • Reflective XSS with impact
  • CSRF
  • CSRF with impact
  • Internal SSRF
  • Session fixation
  • Insecure Deserialization
  • Path Traversal
  • DOM XSS
  • SSL misconfigurations
  • SSL/TLS issues (weak crypto, improper setup)
  • URL redirect

Out of Scope & Rules

The following vulnerabilities are excluded from the rewards for this bug bounty program:

  • Attacks that the reporter has already exploited themselves, leading to damage
  • Attacks that rely on social engineering
  • Attacks requiring access to leaked keys/credentials

Websites and Apps

  • Theoretical vulnerabilities without any proof or demonstration
  • Content spoofing / Text injection issues
  • Self-XSS
  • Captcha bypass using OCR
  • CSRF with no security impact (logout CSRF, change language, etc.)
  • Missing HTTP Security Headers (such as X-FRAME-OPTIONS) or cookie security flags (such as “httponly”)
  • Server-side information disclosure such as IPs, server names, and most stack traces
  • Vulnerabilities used to enumerate or confirm the existence of users or tenants
  • Vulnerabilities requiring unlikely user actions
  • URL Redirects (unless combined with another vulnerability to produce a more severe vulnerability)
  • Lack of SSL/TLS best practices
  • DDoS vulnerabilities
  • Attacks requiring privileged access from within the organization

The following vulnerabilities are not sought after for website bug reports:

  • Theoretical vulnerabilities without any proof or demonstration
  • Content spoofing / Text injection issues
  • Self-XSS
  • Captcha bypass using OCR
  • CSRF with no security impact (logout CSRF, change language, etc.)
  • Missing HTTP Security Headers (such as X-FRAME-OPTIONS) or cookie security flags (such as “httponly”)
  • Server-side information disclosure such as IPs, server names, and most stack traces
  • Vulnerabilities used to enumerate or confirm the existence of users or tenants
  • Vulnerabilities requiring unlikely user actions
  • URL Redirects (unless combined with another vulnerability to produce a more severe vulnerability)
  • Lack of SSL/TLS best practices
  • DDoS vulnerabilities
  • Attacks requiring privileged access from within the organization

The following activities are prohibited by bug bounty program:

  • Any testing with mainnet or public testnet contracts; all testing should be done on private testnets
  • Any testing with pricing oracles or third party smart contracts
  • Attempting phishing or other social engineering attacks against our employees and/or customers
  • Any testing with third party systems and applications (e.g. browser extensions) as well as websites (e.g. SSO providers, advertising networks)
  • Any denial of service attacks
  • Automated testing of services that generates significant amounts of traffic
  • Disassembly or reverse engineering of binaries for which source code is not published, not including smart contract bytecode
  • Public disclosure of an unpatched vulnerability in an embargoed bounty