AirGap Vault - Tezos, Cosmos, Ethereum, Bitcoin

less than 1 minute read

Published:

Wallet Logo

This app was first launched on 6th August 2018 and currently has more than 5000 downloads, a 4.0 stars rating from 37 users and the latest APK is version 3.2.0.

Our last analysis was done on 28th April 2020 based on data found in their Google Play description and their website and their source repository. We discuss verification with the provider in this issue.

We found these ways of contacting the developers:

Older reviews

Help spread awareness for build reproducibility

Please follow AirGap Vault - Tezos, Cosmos, Ethereum, Bitcoin and thank them for being reproducible via their Twitter!

Disclaimer

The following Analysis is not a full code review! We plan to make code reviews available in the future but even then it will never be a stamp of approval but rather a list of incidents and bad coding practice. We cannot find and tell you all the dark secrets the wallet providers might have.

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

Our test script. came to this conclusion:

Results for 
appId:          it.airgap.vault
apkVersionName: 3.2.0
apkVersionCode: 18088
apkHash:        951ee71325f9cee9237cc43235cd653363bf0d7f268e574e4b50856207c170e4

Diff:
Files /tmp/fromPlay_it.airgap.vault_18088/apktool.yml and /tmp/fromBuild_it.airgap.vault_18088/apktool.yml differ
Files /tmp/fromPlay_it.airgap.vault_18088/original/META-INF/MANIFEST.MF and /tmp/fromBuild_it.airgap.vault_18088/original/META-INF/MANIFEST.MF differ
Only in /tmp/fromPlay_it.airgap.vault_18088/original/META-INF: PAPERS.RSA
Only in /tmp/fromPlay_it.airgap.vault_18088/original/META-INF: PAPERS.SF

which is what we want to see for the verdict reproducible.

The huge docker image that needs to be recreated for each build feels like an overkill and might raise other issues once somebody actually does a code audit.

Verdict Explained

Reproducible: The provided Source Code matches the app released on Google Play

The app can be independently verified. If the provider puts your funds at risk on purpose or by accident, security researchers can see this if they care to look. It also means that inside the company engineers can verify that the release manager is releasing the app based on code known to all engineers on the team. A scammer would have to work under the potential eyes of security researchers. He would have to take more effort in hiding any exploit.

"Reproducible" does not mean "verified". There is good reason to believe that security researchers as of today would not detect very blatant backdoors in the public source code before it gets exploited, much less if the attacker takes moderate efforts to hide it.

To understand why some lines of difference are ok and others not one has to consider how app signing works. Android supports currently 3 signing schemes and in version 1 signing the signature is put inside the application file. As the tester must not have the release signing key, those files necessarily are missing or differ from the version on Google Play. The file "apktool.yml" was never part of the app and is generated by the analysis tool "apktool".