Add Anti-Tampering for Mobile Apps
“Tampering: The illegal act of touching or making changes to something when you should not” (Cambridge Dictionary). Learn how to add anti-tampering for mobile apps in your Android and iOS apps without code or coding.
Your mobile application is your masterpiece. It is the summation of all of your hard work, design, testing, re-testing, customer feedback and more. You have created the best app you can, and now, someone can take it, change it as they see fit, replace its colors, schemes and make it do stuff you do not subscribe to. Sounds horrible right? Many apps today are tampered with, re-packaged, re-distributed, and modified at will by malicious parties looking to either re-use your unique advantage or harvest your users’ data by providing them with fake applications that look like yours.
As you may understand, tampering in any context, and especially when it comes to mobile applications is bad news. Tampering may be used to make your application do things you never intended it to do, like prompt your user for their credit card number, or send off their private communications to an extra destination.
Tamper Prevention (anti-tampering) is the act of hardening an application against such changes.
This Knowledge Base explains Appdome’s Anti-tampering capabilities, a key component of ONEShield™ by Appdome, which gets automatically added to every app as part of the Fusion process.
We hope you find it useful and enjoy using Appdome!
About No-Code Anti-Tampering for Mobile Apps
Tamper prevention, or how we call it at Appdome: “Anti-Tampering” is added automatically to every application as part of the fusion process. So whether you chose to integrate with Intune, TOTALDataTM Encryption or SSO with Okta, your built app will be tamper-proof. This is done by sealing your app and actively detecting modifications at run-time. This makes sure no one can re-distribute your app and steal your thunder.
Anti-Tampering will protect against the following static and dynamic modifications to the application:
- Resigning the application
- Modifying the Appdome adapter
- Modifying the application’s executable
- iOS: Main executable (see structure of an iOS application)
- Android: DEX files (see structure of an Android application)
- Moving the application’s sandbox under the name of a different package
It goes without saying that any modification that impacts the application in a bad way (deleting files) will also damage the built application.
What will happen if the application gets tampered?
Thanks to Appdome’s anti-tampering, any tampering will result in the application misbehaving in a random fashion, shortly after which it will terminate.
The reason for this “random” misbehaving is to not give the attacker a clear clue of what exactly went wrong and to make each “crash” unique.
Prerequisites for Using Appdome’s Anti-Tampering for Mobile Apps
In order to use Appdome’s no code implementation of Anti-Tampering, you’ll need:
- Appdome account – IDEAL or Higher.
- Mobile App (.ipa for iOS, or .apk or .aab for Android)
- Signing Credentials (e.g., signing certificates and provisioning profile)
How to add anti-tampering for mobile apps on Appdome
Follow these step-by-step instructions to add Anti-Tampering to any mobile app.
Upload a Mobile App to Your Account
Please follow these steps to add a mobile app to your Appdome account.
If you don’t have an Appdome account, click here to create an account.
Automatic Protection against tampering attempts on your app
As mentioned earlier, Anti-Tampering gets added automatically to every application as part of the fusion process.
After You Add Anti-Tampering for Mobile Apps on Appdome
After you have added Anti-Tampering to any Mobile App on Appdome, there are a few additional steps needed to complete your mobile integration project.
Add Context™ to the Appdome-Built App
Appdome is a full-featured mobile integration platform. Within Context™, Appdome users can brand the app, including adding a favicon to denote the new service added to the app.
For more information on the range of options available in Context™, please read this knowledge base article.
Sign the Anti-Tampering protected Appdome-Built App (Required)
In order to deploy an Appdome-Built app, it must be signed. Signing an iOS app and Signing an Android app is easy using Appdome. Alternatively, you can use Private Signing, download your unsigned app and sign locally using your own signing methods.
Make sure however that you sign with the same credentials you provided, otherwise you will trigger anti-tampering on your own application. Anti-Tampering is blind, it does not have any “backdoors” and can not be fooled.
If you want to make sure you signed with the correct signature you can use Appdome’s App Validation.
Deploy the Appdome-Built App to a Mobile Device
Once you have signed your Appdome-Built app, you can download to deploy it using your distribution method of choice. For more information on deploying your Appdome-Built apps, please read this knowledge base.
That is it – Enjoy Appdome’s anti-tampering protection for your app!
How Do I Learn More?
Anti-Tampering is just one protection measure and synergizes well with Appdome’s Anti-Debugging and Anti-Reversing.
If you are interested in protecting your app, check out Appdome ONEShield, a suite of app protection features.
If you have any questions, please send them our way at support@appdome.com or via the chat window on the Appdome platform.
Thank you!
Thanks for visiting Appdome! Our mission is to make mobile integration easy. We hope we’re living up to the mission with your project. If you don’t already have an account, you can sign up for free.