← Opportunities

TON Security Bug Bounty

Funder
TON Blockchain ⚪ No history
Type / status
bounty · open
Amount
up to 100,000 USD
Deadline
rolling
Ecosystems
ton
Categories
security
Tech stack
cppfuncfiftsolidity
Apply
https://github.com/ton-blockchain/bug-bounty
Source
https://github.com/ton-blockchain/bug-bounty
Fit
8% · poor fit · The Venture23 Aleo team works exclusively in the Aleo ecosystem with Rust/Leo/ZK tech, which is fundamentally different from TON's C++/FunC stack and ecosystem.
Trust
67% · model self-report 90% · first seen 2026-09-28 · v10
Verified
2026-11-15 · page still up, no closing language

The TON blockchain offers a bug bounty program for critical vulnerabilities in its core C++ blockchain code and standard FunC smart contracts. Security researchers can submit reports via Telegram bot for core issues or HackenProof for frontend issues, with rewards up to $100,000 in Grams or USDt depending on severity. The program explicitly excludes minor bugs, validator-initiated attacks, and issues in deprecated or out-of-scope components.

Eligibility: Open to anyone who discovers a critical bug or vulnerability in the TON Blockchain (C++ code of the main repository) or TON standard smart contracts and can provide a description and exploitation scenario.

Pipeline

Override status:

Funder track record · does TON Blockchain actually pay grants?

⚪ No payout history found · checked 2026-11-02 · 0 forum reports, 3 web pages read, 1 unverifiable claims dropped

Proven payer: at least 3 named grantees and one payout in the last 90 days. Every grantee below is quoted word for word from its source. When a source does not date a grant, the date is when that page or post was published.

Trust breakdown (3/4 checkable facts verified)

SignalWeightResultNote
deadline0.350%rolling claimed but not stated
amount0.25100%figure appears in source
apply link0.075100%link in source
funder0.075100%named in source
source quality0.1550%social or search hit
model confidence0.190%model self-report
corroborationbonus+10%10 sources

Fit breakdown (against the ORG_* profile)

SignalWeightResultNote
model fit0.510%model rated 10%
ecosystem overlap0.250%ton vs aleo
category overlap0.1517%security vs zk, privacy, infra, dev_tooling, security, interoperability
tech overlap0.10%cpp, func, fift, solidity vs rust, leo, zk

Sources (10)

RoleDocumentFromFetched
primaryGitHub - ton-blockchain/bug-bounty: TON security bug bounty description · GitHubWeb discovery: ecosystem sweep2026-09-28
primaryGitHub - ton-blockchain/bug-bounty: TON security bug bounty description · GitHubWeb discovery: ecosystem sweep2026-10-03
mirrorGitHub - ton-blockchain/bug-bounty: TON security bug bounty description · GitHubWeb discovery: ecosystem sweep2026-10-05
primaryGitHub - ton-blockchain/bug-bounty: TON security bug bounty description · GitHubWeb discovery: ecosystem sweep2026-10-05
primaryGitHub - ton-blockchain/bug-bounty: TON security bug bounty description · GitHubWeb discovery: ecosystem sweep2026-10-09
primaryGitHub - ton-blockchain/bug-bounty: TON security bug bounty description · GitHubWeb discovery: ecosystem sweep2026-10-12
primaryGitHub - ton-blockchain/bug-bounty: TON security bug bounty description · GitHubWeb discovery: ecosystem sweep2026-10-17
primaryGitHub - ton-blockchain/bug-bounty: TON security bug bounty description · GitHubWeb discovery: ecosystem sweep2026-10-17
primaryGitHub - ton-blockchain/bug-bounty: TON security bug bounty description · GitHubWeb discovery: ecosystem sweep2026-10-23
primaryGitHub - ton-blockchain/bug-bounty: TON security bug bounty description · GitHubWeb discovery: ecosystem sweep2026-10-24

History (10)

vChangedFields
102026-10-24summary
92026-10-23title, summary, type
82026-10-17summary
72026-10-17summary
62026-10-12summary
52026-10-09summary
42026-10-05summary, type
32026-10-05summary, type
22026-10-03title, summary, type
12026-09-28created

Extracted text

[ton-blockchain](/ton-blockchain) / **[bug-bounty](/ton-blockchain/bug-bounty)** Public

*   [Notifications](/login?return_to=%2Fton-blockchain%2Fbug-bounty) You must be signed in to change notification settings
*   [Fork 68](/login?return_to=%2Fton-blockchain%2Fbug-bounty)
*   [Star 289](/login?return_to=%2Fton-blockchain%2Fbug-bounty)
    

 [](/ton-blockchain/bug-bounty)

main

[Branches](/ton-blockchain/bug-bounty/branches)[Tags](/ton-blockchain/bug-bounty/tags)

[](/ton-blockchain/bug-bounty/branches)[](/ton-blockchain/bug-bounty/tags)

Go to file

Code

Open more actions menu

## Latest commit

## History

[43 Commits](/ton-blockchain/bug-bounty/commits/main/)

[](/ton-blockchain/bug-bounty/commits/main/)43 Commits

## Folders and files

Name

Name

Last commit message

Last commit date

[skills](/ton-blockchain/bug-bounty/tree/main/skills "skills")

[skills](/ton-blockchain/bug-bounty/tree/main/skills "skills")

[README.md](/ton-blockchain/bug-bounty/blob/main/README.md "README.md")

[README.md](/ton-blockchain/bug-bounty/blob/main/README.md "README.md")

View all files

## Repository files navigation

# TON security bug bounty

[](#ton-security-bug-bounty)

If you find a critical bug or vulnerability in the TON Blockchain (in the C++ code of the main repository) or TON standard smart contracts, you can send its description and exploitation scenario and receive a reward.

We are interested in critical vulnerabilities: crash, loss/theft of coins, etc.

You can target a reward of up to $100,000 in Grams or USDt for vulnerability, depending on the severity; large bounties for severe vulnerabilities are given with 1 year lock-up.

Let's perfect the safety and security of TON together!

Send general reports to [@ton\_bugs\_bot](https://t.me/ton_bugs_bot). Reports about frontend should be sent to [hackenproof page](https://hackenproof.com/programs/ton-society) (check Frontend section below).

_We reserve the right not to review some reports._

⚠️ Due to spam in the bug bounty program caused by LLM-generated reports, we are currently experiencing delays in processing your submissions. We are doing everything we can to process your submissions as quickly as possible, and most reports are processed within 90 days.

## Out of scope / not accepted cases

[](#out-of-scope--not-accepted-cases)

The following are generally out of scope or will not be accepted without a clear escalation to a real security impact on normal network/service operation:

*   Any minor attacks or bugs that do not cause a node crash, blockchain stoppage, loss/theft of coins, or an incorrect change to the blockchain state.
    
*   Any attacks initiated by a validator.
    
*   Issues that require the attacker to already control the local host, local files/libraries, runtime parameters, environment variables, startup flags, or other trusted operator inputs.
    
*   Issues that require the attacker to already control majority of honest validators, including issues related to malformed blocks signed by the quorum, incorrect network config parameters (require validators voting for them to be accepted). Often under such conditions errors cause CHECK() and node crash: this is intended behavior, where under malfunctioning quorum it is better to halt rather then continue operation.
    
*   Issues that require the attacker to know leaked private information: private key for different public keys (like ADNL, wallets, block signing keys), keys for control-interface, FullNodeMaster, etc
    
*   General advices on how to write blockchains, smartcontracts, or complaints that TON has it's own peculiarities that require different approach then bitcoin, ethereum, etc
    
*   Client-side SDK misuse by the integrating application, including loading attacker-controlled local code/data, when no privilege boundary is crossed.
    
*   Reports against components not listed below, or against stubs / preliminary-testing implementations / deprecated components not intended for production use.
    
*   Input-validation, error-message, or status-code hygiene issues (for example 5xx vs 4xx/405) when the service remains healthy.
    
*   Crashes or odd behavior in local tools, debug-only paths, or other user-side workflows that do not affect normal node/service/blockchain operation.
    
*   Behavior with no realistic manifestation or exploitation path in normal network operation.
    
*   Long-known implementation or design peculiarities, unless you demonstrate a new security impact.
    
*   Issues related to misbehaving validator ability to force other validators to do useless work: validate and/or re-broadcast incorrect candidates.
    
*   Issues related to future timestamps not fitting corresponding uints, including 2038/2106 years problems
    
*   Sybil attack for public overlay
    
*   TON-ETH, TON-BSC, and TON-Eth-token bridges are [deprecated](https://t.me/tonstatus/215) and are out of the scope now.
    

# Priority list:

[](#priority-list)

## TON Blockchain Core (C++)

[](#ton-blockchain-core-c)

[https://github.com/ton-blockchain/ton](https://github.com/ton-blockchain/ton).

Simplex, Validator Node, Full Node, DHT Node.

The testnet branch is considered experimental and often undergoes tests and audits. We are interested in identifying problems at this stage, thus bugs in the testnet branch are accepted, in some cases report review maybe postponed till the end of audit/tests (you will be immediately notified upon report submission).

_Extracurrency_ related bugs are considered but has low priority in terms of processing speed and bounty rewards, due to not being practically deployed on mainnet (with not firm plans about them).

_MisbehaviorProof_ absence in Simplex is known and is a low-priority work-in-progress. It is not critical part for current Simplex operation and expected to be implemented as defence-in-depth. Reports about MisbehaviorProof are not accepted.

Reports about TVM issues, in particular "crash due to some OPCODE usage", "exponential CPU/Mem load over linear gas usage", "gas undercharging" and everything else related to Computation Phase execution strictly requires PoC in Fift, reports without such PoC will be instantaneously rejected. Use [TVM Fift Hypothesis Proover](https://github.com/ton-blockchain/ton-triage-skill/tree/main/tvm-fift-hypothesis-proving) skill to craft such PoCs. Reports related to DEBUG opcodes are out of scope. Only reports for latest `global_version` are accepted.

Explicitly out-of-scope:

*   issues related to non-final LS
*   issues related to Ton Storage, Payment Channels, http-proxy and rldp-http-proxy
*   issues related to blockchain explorer (C++ based from monorepo)
*   issues related to incorrect configuration of validator control interface
*   ability to crash libemulator by supplying incorrect data
*   TonLib
*   FunC compiler
*   Fift compiler
*   Catchain 1.0

## Smart Contracts (FunC)

[](#smart-contracts-func)

Standard smart contracts - [https://github.com/ton-blockchain/ton/tree/master/crypto/smartcont](https://github.com/ton-blockchain/ton/tree/master/crypto/smartcont):

*   Network config - `config-code.fc`;
    
    *   Known peculiarities of Config contract is that if validator voted positively for some proposal his vote (under specific conditions) can be replayed in different rounds without active validator participation.
*   Elector - `elector-code.fc`;
    
    *   Known peculiarities of Elector are not bounty issues by themselves, including `max_stake`\-related stake accounting/recovery behavior and ignoring bounce messages semantics. Also reports for elector-code issues should take into account that `election_id` is different each round, thus signatures for slashing fines can not be replayed.
*   Wallets - `simple-wallet-code.fc`, `wallet3-code.fc`;
    
    *   Deleted-wallet redeploy/reuse behavior by itself is not considered a vulnerability; wallet deletion should be treated as final, and old externals are expected to expire via short `valid_until`.
*   other smart contracts in `crypto/smartcont/` are usually considered smart contract examples and are generally out of scope.
    

Wallet V4 and subscription smart contracts - [https://github.com/ton-blockchain/wallet-contract](https://github.com/ton-blockchain/wallet-contract). Wallet plugins (for all versions) are provided as examples and are out of the scope.

Multisig V2 - [https://github.com/ton-blockchain/multisig-contract-v2](https://github.com/ton-blockchain/multisig-contract-v2)

Highload V3 - [https://github.com/ton-blockchain/highload-wallet-contract-v3](https://github.com/ton-blockchain/highload-wallet-contract-v3)

Nominator pool - [https://github.com/ton-blockchain/nominator-pool](https://github.com/ton-blockchain/nominator-pool) . For nominator pool 2 frequently arising reports are not considered as issues: [Stake withdrawal for low nominator stakes](https://github.com/ton-blockchain/nominator-pool/issues/15), [Stake withdrawal in anticipation of slashing losses may shift losses to other nominators](https://github.com/ton-blockchain/nominator-pool/issues/14)

Fungible, Non-Fungible, Semi-Fungible tokens - [https://github.com/ton-blockchain/token-contract](https://github.com/ton-blockchain/token-contract) . Note that sale, ICO, and other supplementary contracts are provided as examples only and should not be considered reference implementations. Issues in those contracts are out of scope.

TON DNS - [https://github.com/ton-blockchain/dns-contract](https://github.com/ton-blockchain/dns-contract)

## Python

[](#python)

MyTonCtrl validator tools - [https://github.com/ton-blockchain/mytonctrl](https://github.com/ton-blockchain/mytonctrl).

HTTP API - [https://github.com/toncenter/ton-http-api](https://github.com/toncenter/ton-http-api), [https://toncenter.com](https://toncenter.com).

Python SDK - [https://github.com/toncenter/pytonlib](https://github.com/toncenter/pytonlib).

## Frontend

[](#frontend)

All issues related to sites and frontend should be sent to [hackenproof page](https://hackenproof.com/programs/ton-society).

Note that the standard recommendations from the OWASP (e.g. adding the recommended HTTP headers) will not be highly appreciated or will rejected.

The most valuable are real vulnerabilities and critical bugs.

We do not accept reports about open IP addresses or open ports, if this does not lead to an attack (ddos is not considered in this case).

Web Site - [https://ton.org](https://ton.org).

## Third-party

[](#third-party)

Third-party TON services that you can find for example on [https://ton.app](https://ton.app) are also interested in finding security bugs.

In particular, popular products like [https://tonkeeper.com](https://tonkeeper.com), [@wallet](https://t.me/wallet), [@cryptobot](https://t.me/cryptobot), [@donate](https://t.me/donate), [https://tonwhales.com](https://tonwhales.com), [https://getgems.io](https://getgems.io), [https://disintar.io/](https://disintar.io/), [https://tonscan.org](https://tonscan.org).

Please contact them directly if you find a vulnerability.

## About

TON security bug bounty description

### Resources

[Readme](#readme-ov-file)

[Activity](/ton-blockchain/bug-bounty/activity)

[Custom properties](/ton-blockchain/bug-bounty/custom-properties)

### Stars

**289** stars

### Watchers

**22** watching

### Forks

[**68** forks](/ton-blockchain/bug-bounty/forks)

[Report repository](/contact/report-content?content_url=https%3A%2F%2Fgithub.com%2Fton-blockchain%2Fbug-bounty&report=ton-blockchain+%28user%29)

## Used by

## Contributors