AppSuit UnitThe library inside your application
becomes the first target of attack
A code asset protection solution that blocks hacking and analysis of .so / .jar libraries at the source Fully protects the app's core internal logic and SDK from reverse engineering
The moment a library is exposed your core code assets are analyzed as is
It's not the app, but the library inside it that becomes the first target of attack. The moment .so / .jar files are distributed outside the app, anyone can analyze them, and without a dedicated protection solution, the core algorithms and SDK structure are exposed as is.
STAGE 01 · Analysis
Logic theft through external library analysis
Reverse-engineers .so and .jar files to steal core algorithms and authentication logic.
STAGE 02 · Exposure
Reverse engineering of SDK and API structures
Analyzes the internal structure of distributed SDKs to understand API call methods and internal logic, then abuses them.
STAGE 03 · Tampering
Malicious code injection through forgery·tampering
Tampers with unprotected libraries to inject malicious code and infect the entire app.
STAGE 04 · Spread
Third-party library security weaknesses
If a supplied 3rd-party library is hacked, every app that uses that library is exposed to risk in a chain reaction.
* The moment a library is distributed outside the app, it becomes something anyone can analyze. Without a dedicated protection solution, core code assets are exposed as is.
From obfuscation to encryption and integrity protection full-layer coverage for library security
Covers every stage of code asset protection to block reverse engineering at the source.
OBFUSCATION
Code obfuscation
- Identifier obfuscation
- String obfuscation
- API call obfuscation
- API module
ENCRYPTION
Library encryption
- Code section encryption
- ELF header modification
- Disassembly blocking
- File integrity protection
INTEGRITY
Tamper prevention·internal logic protection
- Integrity verification
- API protection
- Internal logic concealment
- 3rd-party library protection
Protection targets and application scope
Safely protects code assets across four areas that protect library assets from multiple angles.
Protection targets
- .so libraries
- .jar libraries
- SDK files
- API modules
Application environments
- Android apps
- JDK 1.8 or higher
- Native code
- Payment·authentication SDKs
Protection scope
- Core algorithms
- Authentication logic
- Encryption keys
- Internal API structure
Delivery security
- 3rd-party delivery
- Technology leak prevention
- Unauthorized copy blocking
- Reverse engineering defense
.jar three-stage obfuscation + .so ELF header·encryption precision protection
By concealing the code structure itself rather than the code content, it makes reverse engineering analysis impossible. It blocks disassembly itself to fully protect native code.
Fully protect .jar with three-stage obfuscation
Identifier + string obfuscation
Obfuscates class·function·variable identifiers and strings within the library to fundamentally block source code structure analysis.
API call obfuscation
Obfuscates API calls to make it difficult to identify when and how specific APIs are called.
Conceals the code structure itself rather than the code content, making reverse engineering analysis impossible
Fully protect .so with ELF header modification + encryption
ELF header modification
Modifies the ELF header to minimize exposed information and dramatically increases the difficulty of analysis.
Code section encryption
Encrypts the code section of the .so file to make disassembly impossible, fundamentally blocking internal code analysis.
Makes disassembly itself impossible to fully protect native code
Three simple steps, apply security with your existing environment unchanged
Applied instantly via a web service upload/download approach with no separate development environment setup. Security is completed at the build stage, so it does not affect runtime performance.
‘Web upload approach’ with no SDK integration·build environment changes
Upload a library file and download the security-applied file. Simply swap it into your existing build.
Upload the library
Just prepare the file with no separate SDK integration
Upload the .so / .jar library file to be secured to the AppSuit Unit web service
Configure security options
Customize protection strength to fit the client's requirements
Set detailed modules such as obfuscation scope, encryption level, and integrity protection options
Apply the secured library
Just swap the library with no changes to existing code
Download the secured library and apply it as is to your existing app build
Proven technology, certified trust
The core differentiators of AppSuit VPNBlock that complete access control.
Direct .so / .jar library protection
Directly protects the library file itself rather than the entire app. A solution optimized for companies that deliver payment·authentication SDKs.
SDK and internal logic protection
Fully conceals the SDK's internal structure with three-stage obfuscation extending to identifiers·strings·API calls.
Extended protection for third-party libraries
Applies the same level of protection not only to in-house libraries but also to 3rd-party libraries.
No changes to your existing development environment
Uploading·downloading libraries to a web service requires no separate development environment setup.
Block chain-hacking risk at the source
Unit blocks the chain risk in which one hacked library endangers every app that uses it.
Enterprise-verified references
A proven solution applied at major domestic and global companies such as Samsung Electronics·LG Electronics·Initech.
Positioning within the AppSuit product suite
Unit focuses on protecting code assets at the Library layer.
Positioning within the AppSuit product suite
Areas covered by Unit
- Direct .so / .jar protection
- Code obfuscation and encryption
- Tamper prevention and integrity
Handled by other modules
- Premium — Comprehensive whole-app security
- Air — App source code obfuscation
- AV — Malware detection·analysis
Frequently Asked Questions
Considering adopting AppSuit Unit?
Adopt a security layer that protects your app's core internal code and libraries. The web upload approach allows instant application with no changes to your existing environment.