Triada
Techniques Used
| Domain | ID | Name | Use | |
|---|---|---|---|---|
| Mobile | T1532 | Archive Collected Data | ||
| Mobile | T1407 | Download New Code at Runtime |
Triada utilizes a backdoor in a Play Store app to install additional trojanized apps from the Command and Control server.[2] |
|
| Mobile | T1646 | Exfiltration Over C2 Channel |
Triada utilized HTTP to exfiltrate data through POST requests to the command and control server.[2] |
|
| Mobile | T1643 | Generate Traffic from Victim |
Triada can redirect ad banner URLs on websites visited by the user to specific ad URLs.[2][3] |
|
| Mobile | T1631 | .001 | Process Injection: Ptrace System Calls |
Triada injects code into the Zygote process to effectively include itself in all forked processes. Additionally, code is injected into the Android Play Store App, web browser applications, and the system UI application.[2][1] |
| Mobile | T1636 | .004 | Protected User Data: SMS Messages |
Triada variants capture transaction data from SMS-based in-app purchases.[1] |
| Mobile | T1418 | Software Discovery |
Triada is able to modify code within the com.android.systemui application to gain access to |
|
| Mobile | T1474 | .003 | Supply Chain Compromise: Compromise Software Supply Chain |
Triada was added into the Android system by a third-party vendor identified as Yehuo or Blazefire during the production process.[2][4] |