Course 42 - Mobile Malware Analysis Fundamentals | Episode 5: Fundamentals, App Structure, and Knowledge Review

Android Security & APK Architecture — Advanced Study Template1. Android Security ModelAndroid security is built around several fundamental objectives:- Protecting user and application data- Isolating applications from one another- Controlling privileges- Providing secure inter-process communication- Restricting unauthorized access to system resourcesThe architecture combines traditional Linux security mechanisms with Android-specific controls.2. Linux FoundationAndroid is built on the Linux kernel, which provides fundamental capabilities such as:- Process management- Memory management- Networking- Device drivers- Filesystem access- User and group permissionsAndroid builds additional security mechanisms on top of these Linux primitives.3. Android Application SandboxOne of Android's most important security mechanisms is the application sandbox.Applications normally execute under distinct Linux identities, which limits their ability to interact with other applications.Conceptually:Android System │ ┌────┼────┐ │ │ │ App A App B App C │ │ │ UID A UID B UID C │ │ │ Sandbox Sandbox Sandbox This isolation helps prevent a compromised application from automatically accessing another application's private data.Security principleCompromise of one application should not automatically imply compromise of every application on the device.4. SELinuxAndroid also uses SELinux (Security-Enhanced Linux) to provide Mandatory Access Control (MAC).This adds another layer beyond traditional Linux discretionary permissions.Conceptually:Application Request ↓ Linux Permissions ↓ SELinux Policy ↓ Allow / Deny Even if a process has certain Linux-level permissions, SELinux policies can impose additional restrictions on what that process is allowed to do.5. Android Application Package — APKAndroid applications are distributed primarily as APK files.An APK is an archive containing the application's:- Compiled code- Resources- Manifest- Assets- Configuration- Supporting componentsA simplified structure looks like:Application.apk │ ├── AndroidManifest.xml ├── classes.dex ├── resources.arsc ├── res/ ├── assets/ ├── lib/ └── META-INF/ For malware analysts, understanding this structure is fundamental.6. AndroidManifest.xmlThe Android Manifest is one of the most important files during APK analysis.It can contain information about:- Package identity- Application components- Permissions- Services- Activities- Broadcast receivers- Content providers- Intent filters- Application configurationMalware-analysis perspectiveThe manifest is often an excellent first point of investigation.For example, suspicious permissions or unexpected exported components can provide early indicators worth investigating further.7. ActivitiesAn Activity generally represents a user-facing application component.Examples include:- Login screens- Settings screens- Main application interfaces- FormsActivities define how users interact with the application.Security relevanceAn analyst may examine:- Exported activities- Intent filters- Deep links- Input handling- Inter-component communication8. ServicesServices perform operations that may continue without a conventional foreground UI.They can be used for tasks such as:- Background processing- Network operations- Synchronization- Long-running application tasksMalware relevanceMalware may attempt to use background components to maintain functionality while minimizing visible user interaction.9. IntentsIntents are messaging objects used to request actions or communicate between Android components.They can facilitate communication between:- Activities- Services- Broadcast receivers- Other applicationsConceptually:Component A │ │ Intent ▼ Component B Security relevancePoorly protected component interfaces can sometimes create security issues involving unauthorized interaction or data exposure.10. Broadcast ReceiversBroadcast Receivers respond to broadcast messages generated by the system or applications.They can be used to react to events such as:- System state changes- Application events- Connectivity-related events- Other broadcastsFrom a malware-analysis perspective, receivers can be interesting because they may reveal how an application responds to specific system events.11. DEX FilesAndroid applications contain compiled bytecode in DEX (Dalvik Executable) format.The primary file is commonly:classes.dex Additional DEX files may appear when an application contains enough code to require multiple files.The code is executed through Android's runtime environment.12. Dalvik vs. ARTHistorically, Android applications ran using the Dalvik Virtual Machine (DVM).Modern Android uses the Android Runtime (ART).Older Android ↓ Dalvik ↓ classes.dex Modern Android ↓ ART ↓ classes.dex Understanding this distinction is important when studying older Android malware samples versus modern applications.13. Content ProvidersContent Providers provide a standardized mechanism for managing and sharing structured data between applications and system components.Conceptually:Application A │ ▼ Content Provider │ ▼ Protected Data │ ▼ Application B Access is controlled through Android's permission and component security mechanisms.Security relevanceContent Providers can become important during security analysis because improperly exposed providers may unintentionally reveal sensitive information.14. Binder IPCBinder is one of the fundamental communication mechanisms in Android.It provides high-performance Inter-Process Communication (IPC) between processes.Conceptually:Process A │ │ Binder IPC ▼ Android System Service │ ▼ Process B Binder is heavily integrated into Android's architecture and is used by applications and system services to communicate.Why it mattersWithout a secure and efficient IPC mechanism, Android's application isolation model would be considerably more difficult to implement.15. APK Static Analysis WorkflowA basic APK investigation can begin by extracting the archive.For example:unzip application.apk -d application/ You can then examine the resulting structure:application/ ├── AndroidManifest.xml ├── classes.dex ├── resources.arsc ├── res/ ├── assets/ └── lib/ The analyst can then investigate the individual components.Typical initial workflowAPK ↓ Extract ↓ Manifest Analysis ↓ Identify Components ↓ Inspect Permissions ↓ Analyze DEX ↓ Inspect Resources ↓ Continue with Static/Dynamic Analysis 🔓 16. Android RootingRooting refers to obtaining elevated or superuser-level privileges on an Android device.Depending on the technique, this may involve exploiting vulnerabilities or modifying the software environment.Conceptually:Normal Application ↓ Restricted Privileges ↓ Android Security Boundaries X Rooted Research Device ↓ Elevated Privileges ↓ Expanded System Visibility 17. Why Root Access Matters for Malware AnalysisA controlled rooted research device can provide researchers with greater visibility into:- Application data- Filesystem contents- Running processes- System services- Runtime behavior- Network activity- Protected application directoriesThis makes rooting particularly useful for dynamic malware analysis.However, rooting also reduces some of the protections normally provided by Android, so it should be performed only in an isolated research environment.18. Android Security ArchitectureThe major security mechanisms can be viewed together: Android │ ┌───────┴────────┐ │ │ Linux Android Kernel Security │ │ Permissions Sandbox │ │ └───────┬────────┘ │ SELinux │ ▼ Application Isolation │ ▼ Secure IPC / Binder 19. iOS vs. AndroidSecurity ConceptiOSAndroidApplication isolationSandboxSandboxLow-level foundationXNU / DarwinLinuxMandatory access controlsMultiple platform mechanismsSELinuxApplication packageIPAAPKRuntimeNative / platform runtimesARTIPCPlatform-specific mechanismsBinderPrivilege modificationJailbreakingRootingApplication codeNative binariesDEX + native codeSecurity researchOften requires jailbreakOften benefits from root20. Key Malware-Analysis ArtifactsWhen analyzing an Android APK, pay particular attention to:AndroidManifest.xmlLook for:- Permissions- Exported components- Services- Receivers- Providers- Intent filtersclasses.dexLook for:- Application logic- Suspicious APIs- Network functionality- Credential handling- Obfuscation- Embedded URLs or domainsres/May contain:- UI resources- XML configuration- Images- Other application resourcesassets/May contain:- Configuration files- Embedded data- Scripts- Additional resourceslib/May contain native libraries such as:.so These can require separate native-code analysis.🎯 Key Takeaways- Android is fundamentally built on the Linux kernel.You can listen and download our episodes for free on more than 10 different platforms:https://linktr.ee/cybercode_academy