TokenPocket Wallet. BTC, ETH, BSC, HECO, TRON, DOTlatest release: 1.2.9 last analysed 13th April 2021
Help spread awareness for build reproducibility
Please help us spread the word discussing transparency with TokenPocket Wallet. BTC, ETH, BSC, HECO, TRON, DOT via their Twitter!
Do your own research!
Try out searching for "lost bitcoins", "stole my money" or "scammers" together with the wallet's name, even if you think the wallet is generally trustworthy. For all the bigger wallets you will find accusations. Make sure you understand why they were made and if you are comfortable with the provider's reaction.
The Analysis ¶
From the description:
You can store, send and receive your Bitcoin (BTC), Ethereum (ETH), EOS, TRON (TRX), IOST, Cosmos and Biance (BNB) easily.
so it’s a BTC wallet and according to the following also self-custodial and open source:
Features of the Multi-Crypto Wallet
- An open-sourced decentralized wallet, keep your cryptocurrencies safe
• It is an open-sourced and non-custodial decentralized wallet that stores your private keys on users’ device, you can store, send and receive all your tokens within the wallet.
And indeed, on their website we can find a link to their repository on GitHub.
A quick look at the code though reveals several issues:
- Minification is a sort of obfuscation and they minify.
applicationIdis not vip.mytokenpocket.
- The repository was last active two years ago while the app on Google Play was last updated two weeks ago.
- The description sounds very different to the Play Store description:
Only supports SWTC Blockchain for now, we will support Ethereum Blockchain and so on in the future.
So for now we have to file it as “no source” and recommend to be careful as some things don’t add up. At least the “open source” claim is probably false. In any case the app is not verifiable as is.
Without public source of the reviewed release available, this product cannot be verified!
As part of our Methodology, we ask:Is the source code publicly available? If not, we tag it
A wallet that claims to not give the provider the means to steal the users’ funds might actually be lying. In the spirit of “Don’t trust - verify!” you don’t want to take the provider at his word, but trust that people hunting for fame and bug bounties could actually find flaws and back-doors in the wallet so the provider doesn’t dare to put these in.
Back-doors and flaws are frequently found in closed source products but some remain hidden for years. And even in open source security software there might be catastrophic flaws undiscovered for years.
An evil wallet provider would certainly prefer not to publish the code, as hiding it makes audits orders of magnitude harder.
For your security, you thus want the code to be available for review.
If the wallet provider doesn’t share up to date code, our analysis stops there as the wallet could steal your funds at any time, and there is no protection except the provider’s word.
“Up to date” strictly means that any instance of the product being updated without the source code being updated counts as closed source. This puts the burden on the provider to always first release the source code before releasing the product’s update. This paragraph is a clarification to our rules following a little poll.
We are not concerned about the license as long as it allows us to perform our analysis. For a security audit, it is not necessary that the provider allows others to use their code for a competing wallet.
Share onTwitter Facebook LinkedIn
Or embed a widget in your website
<iframe src="https://walletscrutiny.com/widget/#appId=android/vip.mytokenpocket&theme=auto&style=short" name="_ts" style="min-width:180px;border:0;border-radius:10px;max-width:280px;min-height:30px;"> </iframe>
<iframe src="https://walletscrutiny.com/widget/#appId=android/vip.mytokenpocket&theme=auto&style=long" style="max-width:100%;width:342px;border:0;border-radius:10px;min-height:290px;"> </iframe>