Adversaries may look for details about the network configuration and settings, such as IP and/or MAC addresses, of devices they access or through information discovery of remote systems.
Adversaries may use the information from System Network Configuration Discovery during automated discovery to shape follow-on behaviors, including determining certain access within the target network and what actions to do next.
On Android, details of onboard network interfaces are accessible to apps through the java.net.NetworkInterface
class.[1] Previously, the Android TelephonyManager
class could be used to gather telephony-related device identifiers, information such as the IMSI, IMEI, and phone number. However, starting with Android 10, only preloaded, carrier, the default SMS, or device and profile owner applications can access the telephony-related device identifiers.[2]
On iOS, gathering network configuration information is not possible without root access.
Adversaries may use the information from System Network Configuration Discovery during automated discovery to shape follow-on behaviors, including determining certain access within the target network and what actions to do next.
ID | Name | Description |
---|---|---|
S1061 | AbstractEmu |
AbstractEmu can collect device IP address and SIM information.[3] |
S0310 | ANDROIDOS_ANSERVER.A |
ANDROIDOS_ANSERVER.A gathers the device IMEI and IMSI.[4] |
S0292 | AndroRAT |
AndroRAT collects the device’s location through GPS or through network settings.[5] |
G1028 | APT-C-23 |
APT-C-23 can collect the victim’s phone number, device information, IMSI, etc.[6] |
S0540 | Asacub |
Asacub can collect various pieces of device network configuration information, such as mobile network operator.[7] |
S1079 | BOULDSPY |
BOULDSPY can collect network information, such as IP address, SIM card info, and Wi-Fi info.[8] |
S0432 | Bread |
Bread collects the device’s IMEI, carrier, mobile country code, and mobile network code.[9] |
S0529 | CarbonSteal |
CarbonSteal has collected device network information, including 16-bit GSM Cell Identity, 16-bit Location Area Code, Mobile Country Code (MCC), and Mobile Network Code (MNC). CarbonSteal has also called |
S0425 | Corona Updates |
Corona Updates can collect device network configuration information, such as Wi-Fi SSID and IMSI.[11] |
S0315 | DualToy |
DualToy collects the connected iOS device’s information including IMEI, IMSI, ICCID, serial number and phone number.[12] |
S0478 | EventBot | |
S0522 | Exobot |
Exobot can obtain the device’s IMEI, phone number, and IP address.[14] |
S0405 | Exodus |
Exodus One queries the device for its IMEI code and the phone number in order to validate the target of a new infection.[15] |
S0509 | FakeSpy |
FakeSpy can collect device networking information, including phone number, IMEI, and IMSI.[16] |
S1093 | FlyTrap |
FlyTrap can collect IP address and network configuration information.[17] |
S0577 | FrozenCell |
FrozenCell has collected phone metadata such as cell location, mobile country code (MCC), and mobile network code (MNC).[18] |
S0535 | Golden Cup |
Golden Cup can collect the device’s phone number and IMSI.[19] |
S0536 | GPlayed |
GPlayed can collect the device’s IMEI, phone number, and country.[20] |
S0406 | Gustuff |
Gustuff gathers the device IMEI to send to the command and control server.[21] |
S1077 | Hornbill |
Hornbill can collect a device's phone number and IMEI, and can check to see if WiFi is enabled.[22] |
S0463 | INSOMNIA |
INSOMNIA can collect the device’s phone number, ICCID, IMEI, and the currently active network interface (Wi-Fi or cellular).[23] |
S0407 | Monokle |
Monokle checks if the device is connected via Wi-Fi or mobile data.[24] |
S0316 | Pegasus for Android |
Pegasus for Android checks if the device is on Wi-Fi, a cellular network, and is roaming.[25] |
S0291 | PJApps |
PJApps has the capability to collect and leak the victim's phone number, mobile device unique identifier (IMEI).[26] |
S0326 | RedDrop |
RedDrop collects and exfiltrates information including IMEI, IMSI, MNC, MCC, nearby Wi-Fi networks, and other device and SIM-related info.[27] |
S0403 | Riltok | |
S0411 | Rotexy |
Rotexy collects the device's IMEI and sends it to the command and control server.[29] |
S0313 | RuMMS |
RuMMS gathers the device phone number and IMEI and transmits them to a command and control server.[30] |
S0324 | SpyDealer |
SpyDealer harvests the device phone number, IMEI, and IMSI.[31] |
S0328 | Stealth Mango |
Stealth Mango collects and uploads information about changes in SIM card or phone numbers on the device.[32] |
S1082 | Sunbird | |
S0329 | Tangelo | |
S0545 | TERRACOTTA |
TERRACOTTA has collected the device’s phone number and can check if the active network connection is metered.[33] |
S1056 | TianySpy | |
S0427 | TrickMo |
TrickMo can collect device network configuration information such as IMSI, IMEI, and Wi-Fi connection state.[35] |
S0506 | ViperRAT |
ViperRAT can collect network configuration data from the device, including phone number, SIM operator, and network operator.[36] |
S0489 | WolfRAT |
WolfRAT sends the device’s IMEI with each exfiltration request.[37] |
S0318 | XLoader for Android |
XLoader for Android collects the device’s IMSI and ICCID.[38] |
S0490 | XLoader for iOS |
XLoader for iOS can obtain the device’s IMEM, ICCID, and MEID.[38] |
S0311 | YiSpecter |
YiSpecter has collected compromised device MAC addresses.[39] |
ID | Mitigation | Description |
---|---|---|
M1006 | Use Recent OS Version |
Android 10 introduced changes that prevent normal applications from accessing sensitive device identifiers.[2] |
ID | Data Source | Data Component | Detects |
---|---|---|---|
DS0041 | Application Vetting | Permissions Requests |
Application vetting services could look for usage of the |