cyberstrikeus T1625.001 System Runtime API Hijacking
Sub-technique of: T1625
High-Level Description
Adversaries may execute their own malicious payloads by hijacking the way an operating system runs applications. Hijacking execution flow can be for the purposes of persistence since this hijacked execution may reoccur at later points in time.
On Android, adversaries may overwrite the standard OS API library with a malicious alternative to hook into core functions to achieve persistence. By doing this, the adversary’s code will be executed every time the overwritten API function is called by an app on the infected device.
Kill Chain Phase
- Persistence (TA0028)
Platforms: Android
What to Check
- Identify if System Runtime API Hijacking technique is applicable to target mobile environment
- Check Android devices for indicators of System Runtime API Hijacking
- Verify mitigations are bypassed or absent (2 known mitigations)
- Assess detection coverage (1 detection strategies)
How to Test
Identify Attack Surface
Determine if the target mobile environment is susceptible to System Runtime API Hijacking by examining the target platforms (Android).
Assess Existing Defenses
Review whether mitigations for T1625.001 are in place. If defenses are absent or misconfigured, this technique may be exploitable.
Remediation Guide
M1002 Attestation
Device attestation could detect unauthorized operating system modifications.
M1004 System Partition Integrity
Android Verified Boot can detect unauthorized modifications made to the system partition, which could lead to execution flow hijacking.
Detection
Detection of System Runtime API Hijacking
Risk Assessment
| Finding | Severity | Impact |
|---|---|---|
| System Runtime API Hijacking technique applicable | High | Persistence |
CWE Categories
| CWE ID | Title |
|---|---|
| CWE-276 | Incorrect Default Permissions |