How to Protect iOS Apps from Liberty Lite Jailbreak Detection Bypass
Learn to Block Liberty Lite Jailbreak Detection Bypass in iOS apps, in mobile CI/CD with a Data-Driven DevSecOps™ build system.
What is Liberty Lite?
Liberty Lite is a very popular, easy to use, general-purpose Jailbreak detection bypass tweak that works with all recent iOS versions and allows users to evade/bypass/hide in-app jailbreak detection mechanisms. It is developed by famed patch developer, Ryley Angus. Since it’s the “Lite” version of the original Liberty Cydia tweak, a major feature is missing from this tweak. Users can’t selectively enable and disable Cydia Substrate or, in Electra’s case, Comex’s Substitute with this version.
Why Block Liberty Lite Jailbreak Detection Bypass in iOS Apps?
Hackers use Jailbreak Bypass tools like Liberty Lite to evade Jailbreak detection/protections. Jailbreaking makes it easier to hack iOS apps and to compromise the mobile security model. So if a mobile app is protected with Jailbreak detection, hackers will try to either bypass the protection or hide the fact that the device is Jailbroken and can continue to do whatever activity they used Jailbreak to achieve over a longer period of time and without being noticed.
Hackers combine Jailbreak tools with Jailbreak detection bypass tools to kill two birds with one stone. For example, hackers combine the use of Jailbreak tools like CheckRa1n, Unc0ver, Zylon, PlankFilza, Chimera, etc, (which they use to Jailbreak iOS), alongside Jailbreak Bypass or Jailbreak hiding tools like Liberty Lite. The first set of tools is used to achieve Jailbreak state, while the second set of tools is used to conceal the existence of jailbreaking.
Blocking Liberty Lite in iOS apps is automatically enabled when Block Jailbreak Detection Bypass is enabled in the Fusion Set.
Prerequisites for Using Block Jailbreak Bypass Tools:
To use Appdome’s mobile app security build system to Block Liberty Lite Jailbreak Detection Bypass , you’ll need:
- Appdome account (create a free Appdome account here)
- A license for Block Jailbreak Bypass Tools
- Mobile App (.ipa for iOS)
- Signing Credentials (see Signing Secure Android apps and Signing Secure iOS apps)
Block Liberty Lite Jailbreak Detection Bypass on iOS apps using Appdome
On Appdome, follow these 3 simple steps to create self-defending iOS Apps that Block Liberty Lite Jailbreak Detection Bypass without an SDK or gateway:
-
Upload the Mobile App to Appdome.
-
Upload an app to Appdome’s Mobile App Security Build System
-
Upload Method: Appdome Console or DEV-API
-
iOS Formats: .ipa
-
Block Jailbreak Bypass Tools Compatible With: Obj-C, Java, Swift, Flutter, React Native, Unity, Xamarin, Cordova and more
-
-
Build the feature: Block Jailbreak Bypass Tools.
-
Building Block Jailbreak Bypass Tools by using Appdome’s DEV-API:
-
Create and name the Fusion Set (security template) that will contain the Block Jailbreak Bypass Tools feature as shown below:
-
Follow the steps in Sections 2.2.1-2.2.2 of this article, Building the Block Jailbreak Bypass Tools feature via Appdome Console, to add the Block Jailbreak Bypass Tools feature to this Fusion Set.
-
Open the Fusion Set Detail Summary by clicking the “...” symbol on the far-right corner of the Fusion Set. Copy the Fusion Set ID from the Fusion Set Detail Summary (as shown below):
Figure 2: Fusion Set Detail Summary
Note: Annotating the Fusion Set to identify the protection(s) selected is optional only (not mandatory). -
Follow the instructions below to use the Fusion Set ID inside any standard mobile DevOps or CI/CD toolkit like Bitrise, App Center, Jenkins, Travis, Team City, Circle CI or other system:
-
Build an API for the app – for instructions, see the tasks under Appdome API Reference Guide
-
Look for sample APIs in Appdome’s GitHub Repository
-
Figure 1: Fusion Set that will contain the Block Jailbreak Bypass Tools feature
Note: Naming the Fusion Set to correspond to the protection(s) selected is for illustration purposes only (not required). -
-
Building the Block Jailbreak Bypass Tools feature via Appdome Console
To build the Block Jailbreak Bypass Tools protection by using Appdome Console, follow the instructions below.
-
Where: Inside the Appdome Console, go to Build > Anti Fraud Tab > Mobile Malware Prevention section.
-
How: Check whether is toggled On (enabled), otherwise enable it . The feature Block Jailbreak Bypass Tools is enabled by default, as shown below. Toggle (turn ON) Block Jailbreak Bypass Tools, as shown below.
If needed, Customize the Threat Notification to be displayed to the mobile end-user in a standard OS dialog notification when Appdome Blocks Liberty Lite Jailbreak Detection Bypass.Figure 3: Block Liberty Lite Jailbreak Detection Bypass option
Note: The App Compromise Notification contains an easy to follow default remediation path for the mobile app end user. You can customize this message as required to achieve brand specific support, workflow or other messaging. -
When you select the Block Jailbreak Bypass Tools you'll notice that your Fusion Set you created in step 2.1.1 now bears the icon of the protection category that contains Block Jailbreak Bypass Tools
Figure 4: Fusion Set that displays the newly added Block Jailbreak Bypass Tools protection
-
Select the Threat-Event™ in-app mobile Threat Defense and Intelligence policy for Block Jailbreak Bypass Tools:
-
Threat-Events™ OFF > In-App Defense
If the Threat-Events™ setting is cleared (not selected). Appdome will detect and defend the user and app by enforcing Block Liberty Lite Jailbreak Detection Bypass.
-
Threat-Events™ ON > In-App Detection
When this setting is used, Appdome detects the use of Liberty Lite and passes Appdome’s Threat-Event™ attack intelligence to the app’s business logic for processing, enforcement, and user notification. For more information on consuming and using Appdome Threat-Events™ in the app, see section Using Threat-Events™ for Block Jailbreak Bypass Tools Intelligence and Control in Mobile Apps.
-
Threat-Events™ ON > In-App Defense
When this setting is used, Appdome detects and defends against Liberty Lite Jailbreak Detection Bypass (same as Appdome Enforce) and passes Appdome’s Threat-Event™ attack intelligence the app’s business logic for processing. For more information on consuming and using Appdome Threat-Events™ in the app, see section Using Threat-Events™ for Block Jailbreak Bypass Tools Intelligence and Control in Mobile Apps.
-
-
Click Build My App at the bottom of the Build Workflow (shown in Figure 3).
-
Congratulations! The Block Jailbreak Bypass Tools protection is now added to the mobile app -
-
Certify the Block Jailbreak Bypass Tools feature in iOS Apps
After building Block Jailbreak Bypass Tools, Appdome generates a Certified Secure™ certificate to guarantee that the Block Jailbreak Bypass Tools protection has been added and is protecting the app. To verify that the Block Jailbreak Bypass Tools protection has been added to the mobile app, locate the protection in the Certified Secure™ certificate as shown below:
Figure 5: Certified Secure™ certificate
Each Certified Secure™ certificate provides DevOps and DevSecOps organizations the entire workflow summary, audit trail of each build, and proof of protection that Block Jailbreak Bypass Tools has been added to each iOS app. Certified Secure provides instant and in-line DevSecOps compliance certification that Block Jailbreak Bypass Tools and other mobile app security features are in each build of the mobile app
Using Threat-Events™ for Liberty Lite Jailbreak Detection Bypass Intelligence and Control in iOS Apps
Appdome Threat-Events™ provides consumable in-app mobile app attack intelligence and defense control when Liberty Lite Jailbreak Detection Bypass is detected. To consume and use Threat-Events™ for Liberty Lite Jailbreak Detection Bypass in iOS Apps, use AddObserverForName in Notification Center, and the code samples for Threat-Events™ for Liberty Lite Jailbreak Detection Bypass shown below.
The specifications and options for Threat-Events™ for Liberty Lite Jailbreak Detection Bypass are:
Threat-Event™ Elements | Block Liberty Lite Jailbreak Detection Bypass Method Detail |
---|---|
Appdome Feature Name | Block Jailbreak Bypass Tools |
Threat-Event Mode | |
OFF, IN-APP DEFENSE | Appdome detects, defends and notifies user (standard OS dialog) using customizable messaging. |
ON, IN-APP DETECTION | Appdome detects the attack or threat and passes the event in a standard format to the app for processing (app chooses how and when to enforce). |
ON, IN-APP DEFENSE | Uses Appdome Enforce mode for any attack or threat and passes the event in a standard format to the app for processing (gather intel on attacks and threats without losing any protection). |
Certified Secure™ Threat Event Check | |
Visible in ThreatScope™ | |
Developer Parameters for Blocking Liberty Lite Jailbreak Detection Bypass Threat-Event™ | |
Threat-Event NAME | JailbreakBypassDetected |
Threat-Event DATA | reasonData |
Threat-Event CODE | reasonCode |
Threat-Event REF | 6924 |
Threat-Event SCORE | |
currentThreatEventScore | Current Threat-Event score |
threatEventsScore | Total Threat-events score |
Threat-Event Context Keys | |
---|---|
message | Message displayed for the user on event |
failSafeEnforce | Timed enforcement against the identified threat |
externalID | The external ID of the event which can be listened via Threat Events |
osVersion | OS version of the current device |
deviceModel | Current device model |
deviceManufacturer | The manufacturer of the current device |
fusedAppToken | The task ID of the Appdome fusion of the currently running app |
kernelInfo | Info about the kernel: system name, node name, release, version and machine. |
deviceID | Current device ID |
reasonCode | Reason code of the occurred event |
buildDate | Appdome fusion date of the current application |
devicePlatform | OS name of the current device |
updatedOSVersion | Is the OS version up to date |
timeZone | Time zone |
deviceFaceDown | Is the device face down |
locationLong | Location longitude conditioned by location permission |
locationLat | Location latitude conditioned by location permission |
locationState | Location state conditioned by location permission |
wifiSsid | Wifi SSID |
wifiSsidPermissionStatus | Wifi SSID permission status |
threatCode | The last six characters of the threat code specify the OS, allowing the Threat Resolution Center to address the attack on the affected device. |
reason | Detection cause |
data | Detection cause data |
With Threat-Events™ enabled (turned ON), iOS developers can get detailed attack intelligence and granular defense control in iOS applications and create amazing user experiences for all mobile end users when Liberty Lite Jailbreak Detection Bypass is detected.
The following is a code sample for native iOS apps, which uses all values in the specification above for Block Jailbreak Bypass Tools:
Important! Replace all placeholder instances of <Context Key> with the specific name of your threat event context key across all language examples. This is crucial to ensure your code functions correctly with the intended event data. For example, The <Context Key> could be the message, externalID, OS Version, reason code, etc.
x
let center = NotificationCenter.default
center.addObserver(forName: Notification.Name("JailbreakBypassDetected"), object: nil, queue: nil) { (note) in
guard let usrInf = note.userInfo else {
return
}
let message = usrInf["message"]; // Message shown to the user
let reasonData = usrInf["reasonData"]; // Threat detection cause
let reasonCode = usrInf["reasonCode"]; // Event reason code
// Current threat event score
let currentThreatEventScore = usrInf["currentThreatEventScore"];
// Total threat events score
let threatEventsScore = usrInf["threatEventsScore"];
// Replace '<Context Key>' with your specific event context key
// let variable = usrInf["<Context Key>"];
// Your logic goes here (Send data to Splunk/Dynatrace/Show Popup...)
}
xxxxxxxxxx
[[NSNotificationCenter defaultCenter] addObserverForName: @"JailbreakBypassDetected" object:nil queue:nil usingBlock:^(NSNotification *org_note) {
__block NSNotification *note = org_note;
dispatch_async(dispatch_get_main_queue(), ^(void) {
// Message shown to the user
NSString *message = [[note userInfo] objectForKey:@"message"];
// Threat detection cause
NSString *reasonData = [[note userInfo] objectForKey:@"reasonData"];
// Event reason code
NSString *reasonCode = [[note userInfo] objectForKey:@"reasonCode"];
// Current threat event score
NSString *currentThreatEventScore = [[note userInfo] objectForKey:@"currentThreatEventScore"];
// Total threat events score
NSString *threatEventsScore = [[note userInfo] objectForKey:@"threatEventsScore"];
// Replace '<Context Key>' with your specific event context key
// NSString *variable = [[note userInfo] objectForKey:@"<Context Key>"];
// Your logic goes here (Send data to Splunk/Dynatrace/Show Popup...)
});
}];
xxxxxxxxxx
const { ADDevEvents } = NativeModules;
const aDDevEvents = new NativeEventEmitter(ADDevEvents);
function registerToDevEvent(action, callback) {
NativeModules.ADDevEvents.registerForDevEvent(action);
aDDevEvents.addListener(action, callback);
}
export function registerToAllEvents() {
registerToDevEvent(
"JailbreakBypassDetected",
(userinfo) => Alert.alert(JSON.stringify(userinfo))
var message = userinfo["message"] // Message shown to the user
var reasonData = userinfo["reasonData"] // Threat detection cause
var reasonCode = userinfo["reasonCode"] // Event reason code
// Current threat event score
var currentThreatEventScore = userinfo["currentThreatEventScore"]
// Total threat events score
var threatEventsScore = userinfo["threatEventsScore"]
// Replace '<Context Key>' with your specific event context key
// var variable = userinfo["<Context Key>"]
// Your logic goes here (Send data to Splunk/Dynatrace/Show Popup...)
);
}
x
RegisterReceiver(new ThreatEventReceiver(), new IntentFilter("JailbreakBypassDetected"));
class ThreatEventReceiver : BroadcastReceiver
{
public override void OnReceive(Context context, Intent intent)
{
// Message shown to the user
String message = intent.GetStringExtra("message");
// Threat detection cause
String reasonData = intent.GetStringExtra("reasonData");
// Event reason code
String reasonCode = intent.GetStringExtra("reasonCode");
// Current threat event score
String currentThreatEventScore = intent.GetStringExtra("currentThreatEventScore");
// Total threat events score
String threatEventsScore = intent.GetStringExtra("threatEventsScore");
// Replace '<Context Key>' with your specific event context key
// String variable = intent.GetStringExtra("<Context Key>");
// Your logic goes here (Send data to Splunk/Dynatrace/Show Popup...)
}
}
x
NSNotificationCenter.DefaultCenter.AddObserver(
(NSString)"JailbreakBypassDetected", // Threat-Event Identifier
delegate (NSNotification notification)
{
// Message shown to the user
var message = notification.UserInfo.ObjectForKey("message");
// Threat detection cause
var reasonData = notification.UserInfo.ObjectForKey("reasonData");
// Event reason code
var reasonCode = notification.UserInfo.ObjectForKey("reasonCode");
// Current threat event score
var currentThreatEventScore = notification.UserInfo.ObjectForKey("currentThreatEventScore");
// Total threat events score
var threatEventsScore = notification.UserInfo.ObjectForKey("threatEventsScore");
// Replace '<Context Key>' with your specific event context key
// var variable = notification.UserInfo.ObjectForKey("<Context Keys>");
// Your logic goes here (Send data to Splunk/Dynatrace/Show Popup...)
}
);
xxxxxxxxxx
window.broadcaster.addEventListener("JailbreakBypassDetected", function(userInfo) {
var message = userInfo.message // Message shown to the user
var reasonData = userInfo.reasonData // Threat detection cause
var reasonCode = userInfo.reasonCode // Event reason code
// Current threat event score
var currentThreatEventScore = userInfo.currentThreatEventScore
// Total threat events score
var threatEventsScore = userInfo.threatEventsScore
// Replace '<Context Key>' with your specific event context key
// var variable = userInfo.<Context Keys>
// Your logic goes here (Send data to Splunk/Dynatrace/Show Popup...)
});
x
import 'dart:async';
import 'package:flutter/material.dart';
import 'package:flutter/services.dart';
class PlatformChannel extends StatefulWidget {
const PlatformChannel({super.key});
State<PlatformChannel> createState() => _PlatformChannelState();
}
class _PlatformChannelState extends State<PlatformChannel> {
// Replace with your EventChannel name
static const String _eventChannelName = "JailbreakBypassDetected";
static const EventChannel _eventChannel = EventChannel(_eventChannelName);
void initState() {
super.initState();
_eventChannel.receiveBroadcastStream().listen(_onEvent, onError: _onError);
}
void _onEvent(Object? event) {
setState(() {
// Adapt this section based on your specific event data structure
var eventData = event as Map;
// Example: Accessing 'externalID' field from the event
var externalID = eventData['externalID'];
// Customize the rest of the fields based on your event structure
String message = eventData['message']; // Message shown to the user
String reasonData = eventData['reasonData']; // Threat detection cause
String reasonCode = eventData['reasonCode']; // Event reason code
// Current threat event score
String currentThreatEventScore = eventData['currentThreatEventScore'];
// Total threat events score
String threatEventsScore = eventData['threatEventsScore'];
// Replace '<Context Key>' with your specific event context key
// String variable = eventData['<Context Keys>'];
});
}
// Your logic goes here (Send data to Splunk/Dynatrace/Show Popup...)
}
Using Appdome, there are no development or coding prerequisites to build secured iOS Apps by using Block Jailbreak Bypass Tools. There is no SDK and no library to code or implement in the app and no gateway to deploy in your network. All protections are built into each app and the resulting app is self-defending and self-protecting.
Releasing and Publishing Mobile Apps with Block Jailbreak Bypass Tools
After successfully securing your app by using Appdome, there are several available options to complete your project, depending on your app lifecycle or workflow. These include:
- Customizing, Configuring & Branding Secure Mobile Apps
- Deploying/Publishing Secure mobile apps to Public or Private app stores
- Releasing Secured Android & iOS Apps built on Appdome.
Related Articles:
How to Detect Checkra1n iOS Jailbreak, Protect iOS Apps
How to Add Root Detection and Prevention to Android Apps
How to Build Jailbreak Detection, Protect iOS Apps
How Do I Learn More?
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 secure every app on the planet by making mobile app security easy. We hope we’re living up to the mission with your project.