libalphasdk.so
libalphasdk.so is a malicious native library identified in compromised SmartTube Android app releases for smart TVs and set-top boxes. Reverse-engineering of SmartTube version 30.51 found the hidden library embedded in the APK even though it was not present in the public open-source code, indicating it was likely injected during the release build process after the app’s signing key was leaked. Investigators reported the library had been present since SmartTube version 30.27, suggesting the compromise began roughly one month before discovery. The library reportedly runs in the background without user consent and periodically collects and transmits data over an encrypted communication channel. At the time of reporting, no DDoS botnet behavior or other additional malicious activity had been observed, though the library was assessed as capable of enabling harmful functionality in the future. The activity is associated with the SmartTube supply-chain/signing-key compromise rather than a named threat actor. Affected targets are SmartTube users on Android-based smart TVs and set-top boxes. Reported indicators related to the incident include MD5 hashes 0ba2cc482828aff5eab9dcfd66b769e3, 0c3bec3debae6bfba4104748beabdb56, 0ee8e0f0cb8db222ee021a1da9f26f40, 1c14f2a92b25a67b32eb5d67670f2f32, and 24b6611ee3f6ffefa2e830bb858e015c.
Techniques & procedures
8 distinct techniques documented for this family, organized by ATT&CK tactic.
Initial Access
1 technique
Initial Access
The developer admitted that their signing key had been leaked and that a library performing malicious behaviors had been included in their app.
Stealth
2 techniques
Stealth
A user who reverse-engineered the compromised SmartTube version number 30.51 found that it includes a hidden native library named libalphasdk.so. This library does not exist in the public source code, so it is being injected into release builds.
This library runs in the background without user consent and periodically collects and sends data through an encrypted communication channel.
Defense Impairment
1 technique
Defense Impairment
The developer identified the issue, stopped the existing signature key, and created a new signature key. They also changed the app identifier (package name).
Discovery
1 technique
Discovery
The library runs silently in the background without user interaction, fingerprints the host device, registers it with a remote backend, and periodically sends metrics and retrieves configuration via an encrypted communications channel.
Command and Control
2 techniques
Command and Control
The library runs silently in the background without user interaction, fingerprints the host device, registers it with a remote backend, and periodically sends metrics and retrieves configuration via an encrypted communications channel.
The library runs silently in the background without user interaction, fingerprints the host device, registers it with a remote backend, and periodically sends metrics and retrieves configuration via an encrypted communications channel.
Exfiltration
1 technique
Exfiltration
This library runs in the background without user consent and periodically collects and sends data through an encrypted communication channel.
Recent activity
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.