CertiK LogoCertiK Logo
MyTonWallet logo
MyTonWallet
Wallet
Max Payout
$5,000
Project Overview

MyTonWallet is a self-custodial Web3 wallet giving users complete control over their assets. With no intermediaries and no recovery possible without the secret phrase, users bear full responsibility for their funds. Built for security and sovereignty, MyTonWallet ensures that only you hold the keys to your digital wealth.

Rewards by Severity

Program Overview MyTonWallet operates a security-focused bug bounty program to uphold the reliability and safety of its wallet infrastructure. The program invites ethical hackers to identify vulnerabilities that may impact user assets or system integrity.

Reward Structure A 4-tier severity model is used to assess all valid submissions, with reward amounts based on both the criticality of the vulnerability and the type of component affected, such as smart contracts or frontend interfaces. Higher-severity issues that pose substantial risk to platform users are eligible for more significant rewards.

Submission Requirements Researchers must submit a complete proof of concept (PoC) that clearly demonstrates the vulnerability and its impact on an in-scope asset. Submissions without actionable code or measurable consequences will not qualify.

Payouts All bounties are denominated in USD and distributed in USDT. Payouts are processed directly by the MyTonWallet team after validation and completion of KYC.

Application/Web
The bounty will be paid out in USDT
Assets In-Scope
Target
Severity
Name
Web Application
MyTonWallet App
In-Scope Vulnerabilities
Only the following impacts are accepted within this bug bounty program. All other impacts are not considered in-scope, even if they affect something in the assets in scope table.
Application/Web
Critical
A possibility for mass private keys or secret phrases leakage from users' devices without direct physical access
Major
A possibility of funds being stolen from users' wallets due to security issue in some specific scenarios without direct access to the user device
Medium
Possibility of losing funds or leaking secret keys or phrases in some rare scenarios
Low
Inaccuracies in implementing common security patterns
Out-Of-Scope Vulnerabilities
The following vulnerabilities are excluded from the rewards for this bug bounty program:
  • Vulnerabilities that have already been exploited
  • Centralization-related vulnerabilities related to: private keys, privileged addresses, governance, credentials, etc.
Application/Web
Reports exploiting the behavior of - or vulnerabilities in - outdated browsers
Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions - Login/Logout CSRF
Non-Sensitive Data Disclosure - for example server version banners
Self-XSS with no security impact
CORS misconfiguration with no security impact
Presence of autocomplete attribute on web forms
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.
  • 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.
  • 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.
  • Do not attempt to conduct post-exploitation including modification or destruction of data - and interruption or degradation of services.
  • Do not attempt to perform brute-force attacks or denial-of-service attacks.
  • Do not attempt to target employees or customers including social engineering attacks - phishing attacks or physical attacks.
The following activities are prohibited by this bug bounty program:
  • Automated testing of services that generate significant amounts of traffic.
  • Public disclosure of an unpatched vulnerability in an embargoed bounty.
FAQs
How do I search for active bounties?
A: Active bounties can be viewed here [CertiK URL], and by filtering for bounties on the Security Leaderboard. Projects will post bounties along with the assets in the scope of the bounties with a corresponding bounty reward.
How do I submit a bounty?
To submit a bug report, first register an account with us https://www.certik.com/auth/signup. Once your account is created, you can log in and select “Submit Bug” for the specific bounties you're interested in. You will be prompted to fill out a webform; follow the instructions and upon successful submission, you will receive an email confirmation with a reference ID.
Who do I contact if I'm having trouble with my bug report submission?
You can reach out to bugbounty@certik.com for updates and assistance with your bug bounty submission.
I submitted my bug report. What now?
Once your bug report is submitted, CertiK will evaluate the report and contact the respective project. Depending on the criteria stated within a bug bounty, a KYC may be required. With valid bug reports, you will be contacted to begin the process of evaluating the bug with the project.
How is KYC handled?
CertiK has a team of investigative professionals that will handle any needed KYC services for bug bounty submissions requiring KYC.
Why was my bug report submission rejected?
A description of dismissal will be available for any bug bounty that is rejected.
The project is being slow responding to my bug report. What are their required response times / SLAs?
There can be multiple bug bounty submissions therefore there might be some delay in process times.
How do payouts work?
Payments for successful bug bounties will be communicated directly via the project wherein wallet information can be exchanged.
Bounty Highlights
Assets in Scope1
Live SinceMar 27, 2024
Last Updated2mo 22d ago
Funds Reserved$100,000
Max Payout$5,000
Skynet Score
92.33
AA
KYC
Required
PoC
Required