Skip to content

Back to the catalog

SecTor 2025 | Ghost SIM Attack: Hacking Mobile Network Authentication Policies
youtu.bevideo

SecTor 2025 | Ghost SIM Attack: Hacking Mobile Network Authentication Policies

Security researchers from Ethon Shield introduce the Ghost SIM attack, demonstrating how extracting non-cryptographic SIM metadata without the secret key (Ki) enables cellular network impersonation across 2G, 3G, 4G, and 5G networks. The exploit takes advantage of permissive, event-based or time-based carrier authentication policies that skip cryptographic verification during network attachment. Defenses include enforcing SIM PINs on end-user devices and mandating cryptographic authentication on all initial network attachments by cellular operators.

TL;DR Security researchers from Ethon Shield introduce the Ghost SIM attack, demonstrating how extracting non-cryptographic SIM metadata without the secret key (Ki) enables cellular network impersonation across 2G, 3G, 4G, and 5G networks.
Document

Overview

In this technical briefing presented at SecTor, security researchers Miguel and Pedro from Ethon Shield (a telecommunications security firm based in Madrid, Spain) introduce the Ghost SIM Attack. Traditional SIM cloning requires extracting a card’s secret cryptographic key ($K_i$) through cryptanalysis or physical side-channel analysis, while modern SIM swapping relies heavily on social engineering customer service representatives.

The Ghost SIM attack establishes a middle ground: it extracts essential, non-cryptographic Elementary Files (EFs)—such as the IMSI and ICCID—from a victim’s device and clones them onto a programmable SIM card. The cloned "Ghost SIM" exploits permissive, event-based or time-based authentication policies enforced by mobile network operators to attach to 2G, 3G, 4G, and 5G networks without ever possessing the secret cryptographic key ($K_i$). This document provides an exhaustive technical reference of the presentation, covering SIM architecture, extraction vectors (smartcard readers, AT commands, ADB), network authentication flows, real-world operator testing across North America, Europe, and Asia, live and recorded exploit demonstrations (including WhatsApp 2FA account takeover), and concrete remediations for operators and end users.


Contents

0:00 Introduction and Problem Definition

Miguel opens the presentation by outlining the current threat landscape regarding mobile identity theft. Historically, mobile fraud relied heavily on SIM card swapping attacks driven by social engineering. Attackers impersonate victims to convince mobile network operators to transfer phone numbers to an attacker-controlled SIM card, leading to downstream account takeovers and financial fraud.

flowchart TD
    subgraph Traditional Attacks
        A[Social Engineering SIM Swap] -->|Con Customer Support| D[Take Over Number]
        B[Full SIM Cloning] -->|Side-Channel / Break Comp128| C[Extract Secret Key Ki] --> D
    end
    subgraph Ghost SIM Attack
        E[Extract Public SIM Metadata IMSI, ICCID] -->|No Ki Needed| F[Write to Programmable SIM]
        F --> G{Weak Operator Auth Policy?}
        G -->|Yes: No Auth Challenge| H[Attach Cloned SIM to 2G / 3G / 4G / 5G Network]
        G -->|No: Auth Challenge| I[Attachment Rejected]
    end

The speaker defines the core thesis of their research:

"The Ghost SIM attack extracts essential SIM card information to take advantage of weak authentication policies to perform fraud in 2G, 3G, 4G, and 5G mobile networks."

To validate this thesis, Miguel breaks down the inquiry into three architectural questions:

  1. SIM Storage & Extraction: What data structures exist within a SIM card, how is identity information stored, and what vectors allow extracting this information without physical destruction?
  2. Authentication Policies: What constitutes an operator's authentication policy, how does authentication operate across generations (2G through 5G), and what causes an authentication policy to be considered "weak"?
  3. Exploitation Feasibility: Why can an attacker maintain network connectivity and commit fraud across cellular generations without possessing the cryptographic root key ($K_i$)?

At 2:03, Miguel introduces the research team from Ethon Shield, a Madrid-based cybersecurity company specializing in telecommunications and baseband research, before handing the stage over to Pedro.


2:23 SIM Card Hacking History and SIM Swapping Fraud

Pedro provides historical context on smartcard and SIM security evolution from the 1990s onward:

  • 1993–1998 (The Pay-TV Satellite Era): Microcontrollers such as the Microchip PIC16C84 (surface-mount implementation paired with external EEPROM, known as "GoldWafer") and PIC16F876 ("Silver card") gained notoriety in satellite television pay-TV pirating. Hackers used smartcard programmers (e.g., Phoenix/Smartmouse readers) to emulate smartcards.
  • 1997–1998 (The Fall of COMP128v1): GSM operators utilized the COMP128-1 algorithm for authentication. Researchers reverse-engineered and broke COMP128v1, demonstrating that the card's secret key ($K_i$) could be extracted after querying the SIM card with approximately $2^{18}$ challenge-response pairs. Software-based emulators (such as SIM-EMU) allowed users to clone physical SIM cards within ~8 hours of physical extraction using standard PC/SC smartcard readers.
  • 2015 (Side-Channel Vulnerabilities in 3G/4G): At Black Hat USA 2015, researchers Yu Yu, Junrong Liu, F-X Standaert, Zheng Guo, Dawu Gu, Sun Wei, Yijie Ge, and Xinjian Xie published research titled "Cloning 3G/4G SIM Cards with a PC and an Oscilloscope: Lessons Learned in Physical Security." By measuring the power consumption variations of SIM chips using an oscilloscope during cryptographic operations, they extracted $K_i$ from Milenage-based 3G and 4G USIM cards in 1 to 2 hours.
  • Fraudster Evolution: Because physical side-channel attacks require expensive laboratory hardware (oscilloscopes, decapping tools, differential power analysis setups), criminals abandoned hardware attacks in favor of social engineering SIM swaps.

Pedro references data illustrating the explosion of SIM swap fraud over time 5:27:

PeriodKey MilestoneNotable Countries
2007 – 2010First reported cases of SIM duplication fraudSouth Africa, Brazil
2011 – 2013Large-scale incidents; "SIM hijacking" terminology emergesUS, Mexico, Spain
2014 – 2016The term "SIM swap fraud" becomes mainstreamUS, UK
2017 – 2019Surge in attacks driven by cryptocurrency exchange account takeoversUS, Europe, LATAM
2020 – 2025Global prevalence; operators face stricter regulatory mandatesWorldwide

Pedro cites an FBI Internet Crime Complaint Center (IC3) report noting that across thousands of reported incidents, SIM swapping losses exceeded $26 million within single reporting periods, highlighting the criminal incentive to bypass cellular identity mechanisms.


6:10 SIM Card Internals and Filesystem Architecture

Pedro explains the underlying data structures of SIM/USIM cards:

Key SIM Parameters

  • ICCID (Integrated Circuit Card Identifier): The globally unique hardware serial number of the SIM card chip (up to 20 digits).
  • IMSI (International Mobile Subscriber Identity): The primary user identity within the mobile network. It is structured hierarchically: $$\text{IMSI} = \text{MCC (3 digits)} + \text{MNC (2–3 digits)} + \text{MSIN (up to 10 digits)}$$ Where $\text{MCC} + \text{MNC}$ forms the PLMN (Public Land Mobile Network) identifying the carrier and country, and the MSIN identifies the individual subscriber line.
  • $K_i$ (Authentication Key): A 128-bit secret cryptographic key assigned by the operator and stored in secure, non-readable SIM storage. It is shared exclusively between the SIM card and the Home Subscriber Server / Authentication Center (HSS/AuC).
  • OP / OPc (Operator Code): Operator-specific configuration parameters used in 3G/4G/5G Milenage algorithms to derive cryptographic run-time parameters.

Smartcard Pinout (ISO/IEC 7816-2)

  • C1: $V_{CC}$ (Power supply)
  • C2: RST (Reset signal)
  • C3: CLK (Clock signal)
  • C4: RFU (Reserved for future use)
  • C5: GND (Ground)
  • C6: $V_{PP}$ (Programming voltage, legacy)
  • C7: I/O (Input/Output data line)
  • C8: RFU (Reserved for future use)

SIM Filesystem Hierarchy

SIM cards follow a hierarchical filesystem defined by telecommunication standards (3GPP TS 31.102 / TS 51.011):

  • MF (Master File, 3F00): The root directory.
  • DF (Dedicated Files): Intermediate directories (e.g., DF_GSM at 7F20, DF_TELECOM at 7F10).
  • EF (Elementary Files): Individual data files storing parameters:
  • EF_IMSI (6F07 under ADF_USIM / 3F00/7F20): Stores the subscriber IMSI.
  • EF_ICCID (2FE2 under MF): Stores the ICCID.

Each Elementary File enforces an access control list (ACL) based on privileges:

  • Always (ALW): Readable/writable without authentication.
  • PIN1 / CHV1: Requires user PIN entry.
  • ADM (Administrative): Requires carrier-level administrative keys (ADM PIN) to modify.

Pedro points out an industry security gap: Many mobile carriers ship SIM cards with the PIN disabled by default. Consequently, EF_IMSI and EF_ICCID are world-readable over the I/O pin without supplying a PIN.

Extracting Data via Smartcard Reader

At 7:38, Pedro demonstrates reading a physical SIM plugged into a USB smartcard reader using the open-source utility pySim-shell.py:

Using PC/SC reader interface
pySim-shell (MF)> select ADF.USIM
pySim-shell (MF/ADF.USIM)> select EF.IMSI
pySim-shell (MF/ADF.USIM/EF.IMSI)> read_binary_decoded
{
    "imsi": "21407XXXXXXXXXX"
}
pySim-shell (MF/ADF.USIM)> select EF.ICCID
pySim-shell (MF/EF.ICCID)> read_binary_decoded
{
    "iccid": "893407XXXXXXXXXXXXX"
}

8:25 Smartphone Architecture and Attack Surfaces (AT Commands & ADB)

Pedro asks the audience: "How many operating systems does a smartphone terminal have?" Audience members guess numbers ranging from two to four. Pedro clarifies that a modern smartphone contains three distinct operating systems:

  1. User OS: Android or iOS (running on the application processor / SoC).
  2. SIM Card OS: Java Card runtime environment (running on the secure smartcard IC).
  3. Baseband OS: A Real-Time Operating System (RTOS) such as Nucleus, ThreadX, or proprietary microkernels (running on the baseband processor / modem).
flowchart LR
    subgraph Smartphone Host
        A[User OS: Android / iOS] <-->|RIL / SMD| B[Modem RTOS: Baseband]
    end
    subgraph External Interfaces
        C[USB Port: CDC-ACM / ADB] -->|Direct AT Commands| B
        C -->|ADB Shell| A
    end
    B <-->|ISO 7816 APDU| D[SIM Card: Java Card OS]

To extract SIM parameters without physically removing the SIM tray, an attacker can leverage hardware communication interfaces between the host SoC and the baseband modem:

Vector 1: The AT Command Interface 9:16

Originating from the 1981 Hayes Smartmodem standard, AT (Attention) commands remain integrated into all modern cellular basebands. 3GPP standards (TS 27.007) standardize AT commands for cellular interactions:

  • AT+CGMI – Returns modem manufacturer.
  • AT+CGMM – Returns modem model.
  • AT+CGMR – Returns firmware version.
  • AT+CGSN – Returns IMEI (International Mobile Equipment Identity).
  • AT+CIMI – Returns the IMSI directly from the SIM.
  • AT+CRSM – Restricted SIM Access: Passes raw APDUs directly to the SIM filesystem.

Pedro highlights research from USENIX Security 2018 ("Attention Spanned: Comprehensive Vulnerability Analysis of AT Commands Within the Android Ecosystem"), which discovered undocumented AT commands exposed over USB interfaces. For example, on certain LG G4 devices, sending AT%KEYLOCK=0 instantly bypassed the Android lock screen.

Vector 2: Direct USB-to-Modem Serial Endpoints 10:40

When a smartphone is connected via USB to a host PC, it may expose a USB CDC-ACM communications device (/dev/ttyACM*).

Pedro demonstrates sending AT+CRSM commands directly through /dev/ttyACM0 to query Elementary Files:

  • To read EF_IMSI (6F07), the command format passes the APDU read instruction: ``bash echo -e 'AT+CRSM=176,28423,0,0,9\r\n' > /dev/ttyACM0 # Output: +CRSM: 144,0,"082901010000001090" ``
  • To read EF_ICCID (2FE2 / decimal 12258): ``bash echo -e 'AT+CRSM=176,12258,0,0,10\r\n' > /dev/ttyACM0 # Output: +CRSM: 144,0,"98440702101000000190" ``

The hexadecimal strings match the IMSI and ICCID decoded earlier via the PC/SC hardware reader.

Vector 3: Android Debug Bridge (ADB) 11:35

If USB Debugging is active, an attacker with physical access can open an ADB shell. Android’s Radio Interface Layer (RIL) communicates with the modem via internal shared memory driver (SMD) device nodes (e.g., /dev/smd7, /dev/smd11, or /dev/at_mdm0).

From an ADB shell session, an attacker can directly inject AT commands into the modem device nodes:

adb shell
cat /dev/smd7 &
echo -e "AT+CRSM=176,28423,0,0,9\r\n" > /dev/smd7

This returns the encoded IMSI and ICCID even while the user-facing screen lock remains active.

Android OS Security Matrix

Pedro summarizes security constraints across Android versions 13:42:

FunctionAndroid < 4.4.2Android 4.4.2 – Android 10Android 11+Android 15+ (Identity Check)
Enable ADBNo unlock requiredUnlock + accept RSA key requiredSame as 4.4.2Requires unlock + biometric authentication
Use ADB (authorized host)Full access even if lockedPartial access when lockedSome critical operations require unlockingSame as Android 11
AT commands via USBAlmost always accessible, even if lockedSome OEMs blocked them; Google didn't enforce yetSince Android 9 Pie, most commands are blocked when lockedSame as Android 11
Biometric authenticationNot availableOptional for screen unlockLockdown mode allows disabling biometrics temporarilyMandatory biometrics for sensitive settings

14:38 Mobile Network Authentication Procedures and Policies

Miguel returns to explain mobile network core architectures and authentication protocols.

Network Architecture Overview

Cellular networks consist of two primary subsystems:

  1. Radio Access Network (RAN): Base stations (BTS in 2G, NodeB in 3G, eNodeB in 4G, gNodeB in 5G) managing radio links over the air interface.
  2. Core Network (CN): Handles call routing, mobility management, internet connectivity, and subscriber databases (HLR/AuC in 2G/3G, HSS/MME in 4G, UDM/AUSF in 5G).

Authentication Protocols by Generation

  • 2G (GSM): Utilizes unilateral authentication. The network challenges the mobile device with a random challenge ($RAND$), and the SIM calculates a response ($SRES$) using $K_i$ and the A3 algorithm. Crucially, the mobile station never authenticates the network. This unilateral trust boundary enables IMSI catchers (Stingrays) and fake base stations.
  • 3G, 4G, and 5G: Implement mutual authentication via the Authentication and Key Agreement (AKA) protocol (e.g., UMTS-AKA, EPS-AKA, 5G-AKA). Both the network and the mobile device independently compute authentication vectors ($RAND, AUTN, XRES$). The SIM verifies the network token ($AUTN$) to ensure the base station is legitimate, preventing rogue base stations from intercepting traffic.
sequenceDiagram
    autonumber
    participant UE as Mobile Device (UE)
    participant Core as Mobile Core Network
    Note over UE,Core: Standard Initial Registration
    UE->>Core: Registration Request (IMSI / TMSI)
    Core->>UE: Authentication Request (RAND, AUTN)
    Note over UE: UE computes RES using Ki
    UE->>Core: Authentication Response (RES)
    Core->>UE: Security Mode Command (Ciphering / Integrity)
    Core->>UE: Registration Accept
    Core->>UE: Registration Complete

Authentication Policies: Time-Based vs. Event-Based

An operator's authentication policy governs when an authentication handshake is required. Executing an authentication challenge requires cryptographic overhead and signaling bandwidth across the core network. Consequently, operators do not authenticate subscribers on every transmission. Policies fall into two categories 16:37:

  1. Time-Based Authentication Policy: Subscribers are challenged only after a specific timer expires. Operator A: Authentication timer set to 24 hours. Operator B: Authentication timer set to 30 minutes. * An attacker attempting a Ghost SIM attachment against Operator A has an exploitable window of up to 24 hours, whereas Operator B closes the window in 30 minutes.
  2. Event-Based Authentication Policy: The network challenges the subscriber only after $N$ events occur (e.g., $N$ SMS messages, $N$ voice calls, or $N$ routing area/tracking area updates).

Measuring Operator Policies via Automated Testing

At 18:12, Miguel presents their custom testing apparatus: a laptop controlling a Quectel cellular modem via automated scripts while capturing signaling frames via Wireshark.

In an automated SMS test 18:58, the script registered with a legitimate SIM, then systematically transmitted outbound SMS messages:

  • SMS #1 through #15 passed without authentication challenges.
  • Upon transmitting SMS #16, the network triggered a DTAP (MM) Authentication Request.
  • This proved the operator enforced an event-based authentication ratio of $1:16$ for SMS traffic.

At 19:30, Miguel displays an empirical comparison of four 2G operators:

Event Type / MetricOperator AOperator BOperator COperator D
Registrations CS (Circuit Switched)20202020
Authentication Procedures Triggered111513
Registrations PS (Packet Switched)20201921
Authentication Procedures Triggered20201520
SMS Sent20201423
Authentication Procedures Triggered12117
Phone Calls Placed2020149
Authentication Procedures Triggered2121

Analysis of the Table:

  • Packet Switched (Data) Attachments: Highly protected. Operators A, B, and D challenged nearly 100% of packet-switched registrations.
  • Circuit Switched (Voice/SMS) Attachments: Weakly enforced. Operators A and B challenged only 1 out of 20 CS registration attempts.
  • Phone Calls: Operators A, B, C, and D challenged calls only 1 to 2 times out of 10–20 calls.

20:30 The Ghost SIM Attack Mechanism

The Ghost SIM attack takes advantage of these permissive authentication gaps:

  1. Prerequisite: Attacker gains brief physical or logical access to the target phone (or SIM card).
  2. Extraction: The attacker extracts EF_IMSI and EF_ICCID (along with operator profile metadata) via a smartcard reader, USB serial AT commands, or an ADB shell. The secret key ($K_i$) is neither extracted nor required.
  3. Cloning: The extracted metadata is programmed onto a blank, programmable smartcard (e.g., a Sysmocom sysmoUSIM-SJS1 card) using the known default ADM PIN.
  4. Network Attachment: The cloned programmable SIM (the Ghost SIM) is inserted into the attacker’s phone. The attacker attempts a network registration. Case A (Strict Policy): The core network responds with an Authentication Request. Because the Ghost SIM lacks $K_i$, it cannot generate the correct $SRES$ or $RES$ token. The network rejects the registration with a Location Updating Reject 21:58. Case B (Permissive Policy): The core network skips the authentication handshake and directly issues a Location Updating Accept 22:22. The Ghost SIM is now registered under the victim's identity.
flowchart TD
    A[Victim Phone] -->|Extract IMSI / ICCID| B(Attacker Script)
    B -->|Write Metadata via ADM PIN| C[Programmable Sysmocom SIM]
    C -->|Insert| D[Attacker Phone: Ghost SIM]
    D -->|Registration Request| E{Core Network Policy}
    E -->|Triggers Auth Challenge| F[Requires Ki: Fails & Disconnects]
    E -->|No Auth Challenge| G[Location Updating Accept]
    G --> H[Cloned Device Connected: Intercept SMS / 2FA]

23:25 Live Demonstration and Hardware Implementation

Pedro demonstrates a portable, standalone hardware implementation of the attack:

  • Hardware Unit: A Raspberry Pi 3 housed in an acrylic casing equipped with a small LCD screen, a connected USB smartcard reader holding a Sysmocom programmable SIM, a power bank, and a USB cable.
  • Operation: When an attacker connects a target smartphone to the Raspberry Pi via USB: 1. The script detects the mobile device (/dev/ttyACM0). 2. The system executes automated AT commands to read nine standard Elementary Files (1/9 through 9/9). 3. The LCD displays "Mirroring SIM..." while writing the parameters to the programmable card using its administrative PIN. 4. The screen flashes green with "SIM Mirrored".

During the live stage attempt in Toronto 27:30, Pedro inserts the freshly mirrored Ghost SIM into an attacker phone and toggles Airplane Mode. The live attempt fails to attach immediately because the Canadian operator challenged the registration request (matching their statistical observation that initial attachment success on Canadian carriers is roughly 1 in 15 attempts).


27:57 Recorded Demonstrations (Singapore and Canada)

To substantiate the exploit, the speakers display recorded field demonstrations conducted in international cellular markets:

Demo 1: Singapore (4G LTE Data & SMS) 28:00

  • Setup: Three phones (Victim phone on the left, Fraudulent Ghost SIM phone in the middle, Legitimate auxiliary device on the right).
  • Execution: Elementary files are cloned via the laptop script into a Sysmocom SIM.
  • Results:
  • The Ghost SIM phone toggles Airplane Mode and immediately attaches to the Singaporean carrier's 4G LTE network.
  • The attacker browses the web, loading the Singapore Airlines homepage (singaporeair.com).
  • The auxiliary phone sends an SMS to the victim’s phone number. The incoming text message lands directly on the attacker's Ghost SIM phone 29:22.

Demo 2: Canada (4G LTE Data Connection) 29:28

  • Setup: Samsung Galaxy smartphone on a Canadian carrier in Montreal/Toronto.
  • Execution: A laptop extracts SIM metadata over USB, writes to the programmable SIM, and inserts it into a Samsung Galaxy S22.
  • Results:
  • Upon exiting Airplane Mode, the device registers on 4G LTE.
  • The attacker searches Google and opens whatismyipaddress.com, verifying active internet connectivity and displaying a public Canadian IP address mapped to Montreal 30:58.

31:08 Global Operator Vulnerability Matrix

Pedro presents a consolidated vulnerability matrix detailing empirical testing across telecommunication operators worldwide:

Vulnerability Status:
[ Vulnerable ] Exploitation Confirmed (Ghost SIM attached successfully)
[    N/A     ] Technology Decommissioned or Not Available on Prepaid
[    Red     ] Protected / Secure (Authentication challenged 100% of the time)

The on-screen table displays testing results across European and Asian operators 31:08:

Country / Operator2G CS2G PS3G CS3G PS4G PS5G PS (SA)
EUR Country #1 Operator #1 (Spain)VulnerableVulnerableVulnerableVulnerableVulnerableVulnerable
EUR Country #1 Operator #2 (Spain)VulnerableProtected (Red)VulnerableProtected (Red)VulnerableVulnerable
EUR Country #2 Operator #3 (Netherlands)VulnerableProtected (Red)N/AN/AVulnerableN/A*
EUR Country #3 Operator #4 (Germany)VulnerableProtected (Red)N/AN/AVulnerableN/A*
EUR Country #4 Operator #5 (Germany)VulnerableProtected (Red)N/AN/AVulnerableN/A*
ASIA Country #1 Operator #6 (Singapore)N/AN/AN/AN/AVulnerableN/A*
ASIA Country #1 Operator #7 (Singapore)N/AN/AN/AN/AVulnerableN/A*

\Note on 5G Standalone (SA) testing:* Pedro clarifies that true 5G Standalone (SA) prepaid SIM cards could only be obtained in Spain without signing long-term identity contracts. In other foreign jurisdictions, 5G prepaid offerings were Non-Standalone (NSA, utilizing the 4G LTE core), meaning 5G SA tests were recorded as N/A due to regulatory/contract limitations rather than technical immunity.

Key Architectural Insights from the Matrix:

  1. 5G Standalone is Vulnerable: In Spain, 5G SA networks with native 5G cores attached to the Ghost SIM without issuing an authentication challenge.
  2. 4G LTE is Universally Vulnerable: Every single tested operator across Europe and Asia allowed Ghost SIM attachments on 4G LTE packet-switched data networks.
  3. Decommissioning Legacy Networks Does Not Fix the Problem: Singapore decommissioned 2G and 3G completely, yet its 4G network remained fully vulnerable to Ghost SIM attachments.

34:20 Post-Exploitation: WhatsApp 2FA Hijacking

Pedro explores the real-world impact of the attack, focusing on two-factor authentication (2FA) bypass and identity theft.

WhatsApp Account Hijacking Walkthrough 35:40

  1. Target Identification: The victim's phone number is mirrored into a Ghost SIM.
  2. Victim Neutralization: To prevent race conditions on incoming traffic, the attacker places the victim's physical device into Airplane Mode or powers it off.
  3. Ghost SIM Initialization: The attacker inserts the Ghost SIM into a Samsung Galaxy A52 and connects to the cellular network via 4G LTE.
  4. Registration: The attacker launches a fresh installation of WhatsApp and submits the victim’s phone number.
  5. Verification Trigger: WhatsApp attempts automated verification via a flash phone call. The attacker’s device receives the incoming phone call 36:12. The attacker ignores the call to test the SMS fallback. After the one-minute timer expires, the attacker selects "Send SMS".
  6. Code Interception & Takeover: At 36:50, the carrier network routes the one-time passcode (OTP) SMS directly to the Ghost SIM device. WhatsApp reads the incoming SMS (WhatsApp code: 891-222), verifies subscriber ownership, and prompts to restore the victim's backed-up chats from cloud storage 36:58.

37:05 Limitations and Key Facilitators (CVEs)

Pedro details the technical limitations and exploitation prerequisites for executing the Ghost SIM attack.

Attack Prerequisites

  • Physical access to the victim's smartphone or SIM card.
  • If targeting the SIM via USB:
  • Screen unlocked OR an unpatched screen lock bypass vulnerability.
  • USB Debugging enabled (for ADB vector) OR 3GPP AT commands exposed over USB.
  • If targeting the physical SIM directly:
  • SIM PIN disabled (the default setting for many carriers).

Enabling Vulnerabilities (Facilitators)

Attackers can leverage known Android vulnerabilities to bypass physical access barriers:

Screen Lock Bypasses (NIST NVD):

  • CVE-2019-16273
  • CVE-2023-43484
  • CVE-2020-0028
  • CVE-2023-20943
  • CVE-2024-0044
  • CVE-2024-31320

Exposed ADB and Modem Ports:

  • Thousands of Android devices worldwide expose ADB listening over TCP port 5555 without authentication. Pedro references data from the Shadowserver Foundation showing ~7,000 publicly exposed ADB instances on the open internet 38:28.
  • Recent baseband modem vulnerabilities allow executing arbitrary AT commands:
  • CVE-2025-26412 (SIMCom modems: Undocumented AT commands grant root privilege on modem firmware) 38:50.
  • CVE-2016-4030, CVE-2016-4031, CVE-2016-4032.

39:14 Countermeasures for Users and Operators

Pedro outlines defensive actions for both subscribers and cellular network operators:

User Countermeasures 39:30

  • Always Activate the SIM Card PIN: Enabling the SIM PIN locks the filesystem. Without the user PIN, Elementary Files (EF_IMSI, EF_ICCID) cannot be read over ISO 7816, AT commands, or ADB.
  • Never Leave Phones Unattended: Physical access remains the primary attack vector.
  • Strict Lock Screen Configurations: Disable lock screen widgets, USB debugging, and notification previews.
  • Deactivate USB Debugging & 3GPP AT Commands: In Android Developer Options, ensure USB Debugging is turned off when not actively in use, and disable the "3GPP AT commands" toggle if provided by the device OEM.

Operator Countermeasures 40:05

  • Mandatory Cryptographic Authentication on Initial Attach: Operators must configure core network nodes (MME, SGSN, AMF) to enforce mandatory cryptographic challenges ($K_i$-based AKA) on all initial registration requests across both Circuit-Switched (CS) and Packet-Switched (PS) domains.
  • Stricter Time Counters: Reduce periodic authentication timers (e.g., in VoLTE/VoNR and data registration), challenging subscribers every 3,600 seconds rather than allowing 24-hour windows.
  • Event-Based Counter Hardening: Eliminate high $1:N$ ratios for SMS and calls. While authenticating every single SMS may cause signaling overhead, operators should establish dynamic, risk-based thresholds rather than predictable static counters.

Pedro concludes the formal presentation at 41:09, directing attendees to their complete academic paper published on ResearchGate: "Ghost SIM Attack: How to take advantage of weak authentication policies in 2G, 3G, 4G and 5G mobile networks."


41:46 Audience Q&A

Q1: Difficulty of Extracting Elementary Files 42:02

  • Question: In terms of getting those Elementary Files off the SIM card, was that already broken or was it an easy thing to do once you had debugger access? Are SIM cards fairly locked down?
  • Answer (Pedro): Extracting the files is straightforward copy-and-paste if the PIN is disabled because the 3GPP specification standardizes those files as world-readable. The real difficulty lies in reverse-engineering the network operator's specific authentication policies to determine the minimal parameter subset needed to attach to the network without provoking a cryptographic challenge.

Q2: Concurrent Operation and Dual-SIM Behavior 43:15

  • Question: What happens with the original SIM card? Would both phones receive calls and SMS at the same time?
  • Answer (Pedro & Miguel): Cellular networks do not support simultaneous ringing across duplicated identities; it creates a race condition in the core network's paging subsystem. Whichever device responds to the page first receives the call or SMS. Attackers mitigate this by either forcing the victim's phone into Airplane Mode, powering it off, or forcing the Ghost SIM onto a different Radio Access Technology (RAT)—for example, locking the Ghost SIM to 2G while the victim remains on 4G.

Q3: Impact of 5G SUPI and SUCI Privacy Enhancements 43:52

  • Question: In 5G, they upgraded the IMSI to SUPI (Subscription Permanent Identifier) and SUCI (Subscription Concealed Identifier). Does that change anything in this case?
  • Answer (Pedro): No. SUCI is an ephemeral encryption of the SUPI designed to prevent eavesdroppers on the radio interface from identifying subscribers. However, the underlying identity files still reside in the USIM filesystem, which the attacker reads directly. Because the Spanish 5G Standalone core network accepted the Ghost SIM registration without issuing an authentication challenge, the SUCI/SUPI mechanism offered no defense against this attack.

Q4: Applicability to eSIMs 44:27

  • Question: Is there any difference between a physical SIM and an eSIM regarding this attack?
  • Answer (Pedro): Researching eSIM profiles and embedded secure elements (eSE) constitutes future work. The presentation and published paper focus strictly on physical SIM cards, though the core network authentication policies remain fundamentally identical regardless of the subscriber profile form factor.

Q5: Forensic Artifacts Left on Target Devices 46:48

  • Question: Does this attack leave any forensic trace on the victim's device? Is there any way to discover if this happened?
  • Answer (Pedro & Miguel): If extracted via USB serial or AT commands, almost no traces remain because baseband modems execute commands entirely within volatile memory; rebooting the device clears active states. ADB interactions may leave command history logs if logged by system daemons, but physical SIM removal or serial extraction leaves zero device artifacts. From the network operator's perspective, the cloned Ghost SIM appears as the legitimate subscriber unless the network explicitly requests the terminal's hardware IMEI and correlates it with anomalous baseband switches.

Data & Visuals Index

TimestampTypeDescription
0:30SlideCore thesis defining the Ghost SIM attack and key research questions.
2:03SlidePresentation outline and speaker introductions (Ethon Shield, Madrid).
2:29SlideHistorical smartcard microcontrollers: PIC16C84 (GoldWafer) and PIC16F876 (Silver card).
3:14SlideCOMP128v1 cryptanalysis news clipping and SIM-EMU emulator timeline.
4:48SlideBlack Hat USA 2015 side-channel attack citation (oscilloscope power analysis on USIMs).
5:27TableHistorical timeline of SIM swapping fraud from 2007 to 2025 with FBI IC3 statistics.
6:09DiagramSIM card pinout (ISO 7816-2) and IMSI structure decomposition (MCC, MNC, MSIN).
6:39DiagramSIM card filesystem tree structure (MF, DF, EF) and elementary file access control list.
7:38DemoShell recording of pySim-shell.py extracting EF_IMSI and EF_ICCID via PC/SC reader.
8:24DiagramGeneric smartphone internal architecture: Application Processor SoC, Modem RTOS, SIM Java Card.
9:16SlideHistory and syntax of Hayes AT command set and 3GPP cellular AT commands.
10:06SlideUSENIX Security 2018 study citation on AT command screen lock bypasses.
10:55DemoDual-terminal session executing AT+CRSM commands over /dev/ttyACM0 to extract IMSI.
11:36DiagramAndroid RIL and ADB communications architecture routing AT commands to baseband.
12:40DemoInjecting AT+CRSM via ADB shell through modem SMD device /dev/smd7.
13:42TableSummary of Android security controls across versions (< 4.4.2 through Android 15).
14:38DiagramMobile network 101 registration and authentication signaling ladder (UE to Core).
16:37DiagramComparison of time-based vs. event-based mobile network authentication policies.
18:12DemoTest rig setup: laptop controlling Quectel cellular modem board with Wireshark.
18:58Code/CaptureWireshark packet trace displaying authentication triggered after 16 consecutive SMS messages.
19:30TableExperimental authentication procedure policy results across four 2G operators (A, B, C, D).
20:30DiagramStep-by-step schematic overview of the complete Ghost SIM attack vector.
21:58Code/CaptureWireshark trace showing network authentication failure and Location Updating Reject.
22:22Code/CaptureWireshark trace showing network authentication bypass and Location Updating Accept.
22:32DiagramStandalone field exploit setup (Raspberry Pi 3, reader, programmable SIM).
23:45DemoLive hardware demonstration displaying automated SIM extraction on custom LCD screen.
28:00DemoVideo demonstration of Ghost SIM attaching to 4G in Singapore, web browsing, and receiving SMS.
29:28DemoVideo demonstration of Ghost SIM attaching to 4G in Canada and confirming public IP address.
31:08TableGlobal operator vulnerability matrix across 7 operators in Spain, Netherlands, Germany, and Singapore.
35:40DemoVideo walkthrough hijacking victim WhatsApp account via voice and SMS 2FA codes.
37:05SlideAttack prerequisites and Android system limitations.
37:49SlideAndroid lock screen bypass CVE list (CVE-2019-16273 through CVE-2024-31320).
38:14SlideExposed ADB statistics from Shadowserver Foundation and modem AT CVEs.
39:14SlidePractical user countermeasures (SIM PIN, lock screen, AT/ADB disabling).
40:05SlideOperator countermeasures: mandatory authentication, counter review.
41:09SlideQR code and link to full academic white paper on ResearchGate.

Key Takeaways

  • $K_i$ Extraction is Not Mandatory for Cellular Impersonation: While cloning cryptographic root keys ($K_i$) remains difficult, cloning basic Elementary Files (EF_IMSI, EF_ICCID) into a programmable SIM card allows an attacker to impersonate subscribers on networks that fail to issue cryptographic challenges.
  • Cellular Authentication Policies are Inconsistent: Operators optimize for signaling overhead and network capacity by spacing out authentication challenges using time-based counters (up to 24 hours) or event-based counters (e.g., challenging only 1 in 16 SMS or 1 in 20 registration attempts).
  • 4G LTE and 5G SA are Vulnerable: Insecurity is not limited to legacy 2G/3G networks. The research proved that 4G LTE packet networks across multiple continents—and native 5G Standalone in Spain—permit Ghost SIM attachments when authentication challenges are skipped.
  • Modern Privacy Enhancements (SUPI/SUCI) Do Not Prevent This Attack: 5G SUPI concealment protects over-the-air radio eavesdropping, but does not prevent an attacker from reading the stored USIM identity files and presenting them to an unchallenging core network.
  • Enabling the SIM PIN Neutralizes the Extraction Vector: Activating the standard 4-digit SIM PIN prevents unauthorized readers, USB serial interfaces, and ADB commands from querying EF_IMSI and EF_ICCID.
  • Operators Must Enforce Strict Attachment Verification: Carriers can mitigate the Ghost SIM attack by requiring full cryptographic authentication ($K_i$-based AKA) on all initial network attachments across circuit-switched and packet-switched domains.

Transcript

Englishen40.2k chars
SIM card swapping attacks have been and are a reality nowadays. Based on social engineering, attackers are able to transfer their victim's phone number into a new SIM card, resulting in fraud. Today, we present to you a new technique that also results in fraud in mobile networks in all technologies, the goim attack. Awesome. The go sim attack extracts essential sim card information to take advantage of weak authentication policies to perform fraud in 2G, 3G, 4G and 5G mobile networks. This short sentence summarizes the key ideas and key aspects of our presentation today. We will see how to perform the attack, what are the steps needed to perform the attack, and why does this attack work. But for you to understand this short sentence, we need to break it down and ask ourselves several questions. In the first place, the goim attack extracts essential sim card information. So one of the questions we need to answer is what's isa sim card and how does it store information and how are we able to extract this information? What are the techniques and methods? Furthermore, after extracting this incred weak authentication policies. So what are authentication policies? What is an authentication procedure in mobile networks? And what exactly do we mean when we say weak authentication policies? And finally, after we extract this SIM card information and take advantage of weak authentication policies, we are able to perform fraud. So we need to answer the question of how and why is this attack capable of performing fraud in all the generation generations of mobile networks. But before we start with the technical details let us present ourselves. Joining me today is Pedro and I'm Miguel. Both of us work at Ethon Shield which is a company based in Madrid, Spain which focuses on telco hacking. Now I I will let you with Pedro with he will start with the technical details of SIM card hacking. &gt;&gt; Okay, let me first take you back to the 90s. Uh Windows 95 was just shining, right? Linux between version one and version two and pay TV satellite hacking groups began to take on great importance. That's when I started playing around with smart cars hacking. They were two main big players. I don't know if you recall big microcontrollers 16F84 and 16F 876. They came up in a smart car form factor. That's the gold waffer and later arrived the silver car. They were the big players in pay satellite hacking and sorry. Yeah, I was just curious. I was starting to reading assembler switching on and off lights was like a new world to me. And suddenly one day searching on the internet what I could done with this hardware I discovered something called CMU standing for SIM card emulator. was like, "What? Really? Why? What? What do I need? Take all my money. I just want to clone my SIM card. Really?" So, I learned that the algorithm that kept some things I going to explain you later secret was broken in the between 97 and 98, the comp 128 algorithm was broken. So if we plug the SIM card into a reader, the same reader that I was using for the pay TV smart cards, I need to take two parameters. First was the identity. I will explain you later this parameter inc. And the big one is a secret key that need eight hours of the attack. We plug the SIM card, we go at night, have some rest, and next in the morning, we extract the secret key. So with those two parameters, I program them in a programmable SIM card and I have just a copy exact copy, a clone of the SIM card. So I started playing around with this new identity because for the network, I was exactly the same subscriber. So I could uh do fun and profit, right? do fraud calls all everything will be charged to the legitimate subscriber. Sometime later collaborative work show a new side channel attack vulnerability that allow these researchers using a very accurate osilloscope. They were measuring the power consumption of the chips and they will again are able to get the secret key. That attack will last between one hour and two hours. But of course that will attack object sorry to 3G and 4G SIM cards. Those are very complex attacks. Fraudsters don't like this complexity right? So they came up with a new idea deception or social engineering. Why standing or necessity of these technical gadgets where we could just ask the operator for a copy of the SIM card or transfer the subscriber, right? That started in 2007 between South Africa and Brazil and became spread over the world. I think FBI report from cyber crime 2024 they study something between a thousand cases and lasted for 26 million of dollars the impact of the swin swap I'm talking about sim car sim cars what's the sim car the sim cars kept first of all the subscriber identity what's called IMC international mobile subscriber identity among others identities temporary identities and I've talking before about the secret key, the KI, right? There are many other keys as the operator code and so on. They could exchange information towards the mobile using these contacts. How they exchange the information be because they are offering file system capabilities. Let me focus on two of them. the INC the identity and the integrated circuit serial number because we are going through some examples using these two files. As you see at the right, the files have permissions, security restrictions. If we want to read the MC, we need the PIN number. If we want to update the INC, we need administrator requirements. So all the SIM cards that they came up without any PIN number, they allow us to read the EMC directly. We don't know to guess the PIN number. That's a security feature. Some countries they offer SIM cards by default without PIN number. So it's well not a good practice. So think that we are have access to the H SIM card. It's just a very quick demonstration. We plug the sim card in our reader. We are going to use pyim shell. It's a very well-known interface because we'll give us human readable way to select the files. You see that we are selecting by name if stands for elementary file just a standard files and we are reading the content. So we are reading the IMC the identity of our victim. We are listing files just like ls and we are selecting now the integrated circuit file because we want also to check uh the content. For obvious reasons we are not going to disclose all the elementarymentarian files involved in the attack but we want to show you that once that we have physical access to your sim card we can just plug in the reader and extract information. That's a question for you guys. How many oss does a terminal have? Make your guess. Random numbers. &gt;&gt; Four. &gt;&gt; Three. &gt;&gt; Three. That's it. We have the pretty brand well-known. Okay. The Android and the iOS. That's for sure. And we have SIM cards. They are based on Java. Java cars from the third generation. And the bassband, the modem, they are running airs. So we have three different oss and they need to be connected right because bassband needs to let us Android know when we have a call or SMS or whatever and the same with the SIM card. So we draw this generic architecture to say okay our objective is the SIM card. We want to take information from the SIM card how we can approach. Let me introduce you the 80 commands from the 80s, the golden years, right? They were developed to handle the first generation of the modms. They are very well known. They all of them start with at acronym for attention plus some characters, four to five characters that is the instruction, the specific instruction. But I don't know if you are aware that we have a specific subset of these commands for the sim cars. Then we started to get on the road. is like hey we are talking now some of you may discover in your Android this option 3GPP8 commands there is not available in all the manufacturers because doesn't came from the Android branch of the OS some manufacturers implement these options if you want to allow these at commands some others don't on 2018 some researchers analyze a huge number of smartphones because there are and documents or let me say more polite proprietary commands analyzing the firmware they discover on the LG G4 for example a nice feature maybe today is a back door is an Android lock screen bypass 80 key lock equals zero and we will bypass the Android lock screen powerful right we were talking we need this 80 commands when we plug the smartphone towards our computer. We will have a new TTY ACM serial device and we will interact in the same way like before with these 80 commands. Let me show you the example. On the right screen, we will cut the results of the 80 commands. On the left, we will we will be typing the 80 commands. This time, we are not referring the files by name. It's pure identifier. We need to translate these identifiers with their decimal number. And you see on the right that the output of the two files that we are consulting reading is exactly the same value. What's the difference? Instead of plugging the SIM card, you see in the bottom right, we just plug the smartphone and the screen is unlock, right? We don't need to lock the screen. Sorry, we don't need to unlock. It's already locked. And the last method I want to introduce you more well known nowadays and more modern is the ADB Android debug bridge right we usually open these ADB shells to interact with the Android 80 commands were designed to interact with the modeling we can do phone calls receive SMS and so on but ADB is for debuggers engineers to interact with the Android that needs to map the modem again as a serial interface right is usually they map this through the radio interface layer the the API the real they map as SMD usually a surface mount device once we have mounted this device we can interact again with the model what do we need in order to interact yeah the USB debugging we need to activate developer options and inside developer options we need to activate USB debugging once we have this feature again on the left we will open ADB shell and we will type the 80 commands on the right. We will output the result of these 80 commands. The mobile the smartphone it's on the bottom right screen again is lock. We are typing copy and paste the 80 command the same two files as the beginning the identity and the integrated circuit serial number. Uh here we are. Come on, Pedro. Yes, that's the same result for the two files. So, we have 80 commands and ADB way to interact with the SIM card, but they require as you see in the bottom left that we interact with the options. Sometimes when we get our big team phone, we don't know if these options will be enabled by default. What do we need to enable the options? The third column we need to interact with the Android by default security requirements could be a ping could be a pattern sometimes is biometrics right it's up to the version of the Android we wanted to summarize all of these with using chat GPT because Android is so heterogeneous all the manufacturers they are introducing features in different time in different versions so yeah we want to enable ADB up to the Android version we have some different security requirements. Same to use ADB. Sometime at some moment they introduce the RSA authentication. So we need to authorize the host in order to interact using ADB. 80 commands they are not on the OM. So usually they are authorized and the biometric. We wanted to focus our investigation not covering all the different branches of Android and manufacturers. We wanted to cover investigation focusing on the authentication policy that I will handle to Miguel to continue. So now we have seen the different methods to extract SIM card information and if you remember in the first sentence after extracting this information we need to take advantage of weak authentication policies. So what are authentic authentication policies? But first we need to start with basis. A mobile network is a network that is has two main components. The radio access network and the core network which are interconnected between each other. The core network provides different services to the clients such as access to the internet calls, SMSs, mobility management. It stores different parameters in the database and the radio access network is connected to the clients over the air interface. So the clients are smartphones, IoT devices, cars, everything that has a physical SIM card or an embedded SIM card. So for the clients to be able to use the different services provided by the network, they need to successfully register. And within this registration procedure, we find the authentication procedure. The authentication is the procedure that ensures that both the client and the network are who they claim to be. In 2G networks at the beginning only the network authenticated the client. The client did not authenticate the network. That is why attacks such as fake base stations also known as stingrays or MC catchers were very common and are very common. But from 3G onwards there started to be mutual authentication which is much more secure. Both the network and the client authenticated each other. So how does this work? Well, both the SIM card and the mobile network have a pre-shared key as we saw at the beginning. The secret key KI this KI is used as the seed value to calculate the different parameters to successfully authenticate each other. So what is the authentication policy? The authentication policy defines how often and under what conditions the authentication procedure is triggered. It can be a timebased authentication policy andor an event-based authentication policy. In a timebased authentication policy, after the user registers successfully in the network, the operator will start a timer and after when the timer expires, it will trigger an authentication on the subscriber. In an event- based policy, the after a set number of events, the which are operator dependent, the network will authenticate the user. Generally these events includes SMSS, phone calls, mobility updates, service requests. It's totally operator dependent. So when we say that we take advantage of weak authentication policies, what do we mean? Well, let me give you an example. Imagine two operators. The fir both of them have a timebased policy and the first operator the timer is of 24 hours and in the second operator the timer is of 30 minutes. If an attacker is cap is um capable of bypassing the authentication, the exploitable period in the operator that has a longer timer will increase. So that means that a longer timer will mean that it has a weaker authentication policy. So for our goim attack, it was very important to analyze and identify the authentication policy of different mobile operators across the globe. So we automated the tests. In this example, you can see at the right a keectel modem which has a legitimate SIM card inserted. It acts as a mobile device, but you can control it much more. And the test here is we were trying to analyze the authentication policy based on events of sending SMSS. So in this with with a script we start sending SMSs to a another mobile device and we are capturing the signaling traffic of the kek modem and then we can understand when does the network authenticate us and how many SMSs can we send without the network authentic triggering an authentication request. So you can see that in the mobile device you're continue sending SMSS with hello hello hello and the result of this test is this wire shark capture you can see at the beginning that there's a successful uh registration with a successful authentication and then we start sending SMSs and after some time after some a number of SMSs we receive an authentication procedure authentication request. So it in this example after 16 SMSs the network authenticators. So it has an eventbased policy of of SMSS of one over 16. In here uh it's a small table that we show the results of different operators um authentication policy in the 2G networks. Apart from the SMS test, we did other tests to analyze different events such as apart from the SMS test, we also start calling another mobile device and see when does the network authenticate us or registering into the circuit switch domain or registering into the package switch domain. So highlighted in red you can see the robust authentication policies. For example in the registration of the package se domain which the registration is the first me message you send to the network the network authenticate us every time. So it has a very robust authentication policy. On the other hand in the automated test of the phone calls the network in average authenticated us one in every 15 times. So it it was a weak authentication policy. So now that we have seen how to extract sim card information and we know we understand what is a weak authentication policy let's see what is the goim attack. So by extracting the sim card information we copy that information into a programmable sim card without needing the ki because it is important to highlight that the ki is not in an elementary file. It's not in an accessible part of the memory of the sim card. So we cannot just retrieve it. So we extract this SIM card information without the KI. We copy to a programmable SIM card and put this programmable SIM card which is now the GO SIM into a mobile device and we successfully connect to the network provided that the network does not authenticate us. That is why it's very important that the network has a weak authentication policy. So what are the steps for the attack? First, we need to have physical access into the victim's phone because we need to interact with the SIM card. Then we extract the SIM card information, copy that information into a programmable SIM card, and finally insert that programmable SIM card into a mobile device. To copy the information into a programmable SIM card, we use the programmable SIM cards of Sysmoc, which you may know when you um buy them, the Sysmo sends you an ADM pin number, the administrator PIN number, so you are able to read, write, and update the different files um of the SIM card. So you have total control of over the SIM card. So once you insert this SIM card into um your fraudulent mobile device, you try to connect to the network. In this example, the network authenticated us. This is a 2G example. So we get rejected by the network with the location updating reject. Why? Because we don't have the KI. So we cannot bypass the authentication. And in this example, we get accepted in the network because the network does not authenticate us as you can see. Location updating accept. So what how does this look in in real life a real design. So we can have a Raspberry Pi which has inside the software to extract the SIM card information. to the Raspberry Pi. You have a SIM card reader connected to it with the programmable SIM card from Sysmo and also a USB cable. So now we try to find the victim. Once we find the victim which is connected to a legitimate uh network, we connect the mobile device into our USB cable and we start extracting the SIM card information. Once we finish extracting this information, we copy it into the programmable SIM card and we have a go sim. We get our fraud mobile device and connect this goim into the fra mobile device and connect to the network. So now let's try &gt;&gt; for glory, right? We are the sector. So this is the Raspberry Pi. Let me introduce you. We don't want to weaponize the attack. We wanted to show you that we it's not computational requirement. We just need very small h microcontroller that could be done even with an Arduino. We are managing serial uh serial communications. We have the programmable with the SIM card, a small power bank and it's waiting for any phone to be connected. Right. On the other hand, let me switch back to the camera. Oh, &gt;&gt; we don't see the camera. [snorts] We have our big thing. &gt;&gt; I need your hands. &gt;&gt; You have to move to another screen. Yeah, there we are. &gt;&gt; Okay. More or less. &gt;&gt; I will put it like this so we can focus. Oh, I will do my my best as a camera. Here we see that this connected to the 4G. This is the victim. Sorry. We can &gt;&gt; so we bought SIM cards from different operators here in Canada and we yesterday we analyzed very quickly the authentication policies and we saw that in of the four of them three of them had a very robust authentication policy which is very impressive compared to our other studies and the last one had a it doesn't it didn't have a weak authentication policy but it didn't have a robust authentic ification policy is that a medium. So ah that's for obvious reason we're we're not going to answer that. Write it down. &gt;&gt; No. &gt;&gt; Okay. So it's on Toronto. We are using SIM cards just both these days. And let's go for the real demo. &gt;&gt; So we connect the victim's phone into the Raspberry Pi. One sec. &gt;&gt; No, one sec. You want me to reboot the Raspberry Pi? &gt;&gt; No. &gt;&gt; Okay. We bought we buy four different SIM cards here in Canada. None of them are using the PIN number, but two of them is the first time that we see that they are authenticating every initial attach. So, the attack won't work for sure. So we have the other two operators that let's cross our fingers. We have some backups but we really would like to show you on uh yeah this is an spoiler how we should end the demonstration. Now it's waiting for the phone. It's a very basic script. the text sorry I'm trying to take yeah now it's been a list of the elementary files we will access them reading they are very standard elementary files as just me introduced there is no file for the secret key obviously if not we will be cloning sim card we are just getting the information could be quicker I mean we could do the attacker really quick but we wanted to show you a normal demonstration not to perform the more efficient or quicker attack just for educational purposes. We are just reading all of them and at the end we will copy to the sysmocom sim file and we will plug we've been testing I forgot to mention on Samsung S22, Samsung A25, Samsung A52 and LG Nexus 5X. We only been playing with four different H smartphones. Now it's copying everything into the SIM card and it's finished. &gt;&gt; So now &gt;&gt; crossing fingers &gt;&gt; we have the go sim here and let's see when it's one by 15 we should have good chances. Let me Yeah, if we remove the airplane. &gt;&gt; No it didn't. &gt;&gt; Oh no good luck. This is why we came prepared with some videos. But you will see that the videos are from Canada. It's really complicated. We should need the complete study of the authentication policy in order to guarantee. But no pain, no gain, right? We wanted to do on live. This is from Singapore. It's the same setup. Instead of the Raspberry Pi, we are using the the laptop, but everything is exactly the same. We will show you we have I forgot him. The left is the victim in the middle is the attacker and the legitimate is just to demonstrate attack with SMS. Okay, we will demonstrate that the go SIM is registered in the network. So we are exactly the same as we are doing here. We are reading thementary files. We are copying all of them into the sysmo sim car. That's the go sim we introduced. This is the Samsung A52. And once we remove the airplane mode to avoid time and we can switch on and off, but this quicker just to remove it's connected to the network. I hope you will. Yes, we are assuming it's on 4G. We will open what's my no Singapore. Sorry, we were using what's my IP address. We wanted to show you that we can browse the internet. And now we are going to send to any phone number. We just take one legitimate phone number. So we will show you that we can send SMSS from one to the other between them. There we are. We received the SMS on the go sim. &gt;&gt; And yeah, that's from Canada. This second video we were hoping that uh we have more chances here. That's I think we recorded yesterday. They're showing that the Canadian SIM card is browsing the internet. Again, we do the the process from the laptop. Yeah, we will accelerate to avoid again and again over the video the time to reading the files here. I think we only take 4G. Yes. So, it's really quicker the attack when we focus on the technology. We are always a balance between success ratio if we copy a lot of information from different technologies or we want to attack only one technology. This is why it gets quicker and yeah it's this operator in Canada is not so weak as we have seen around the world. It's a balance. It's not robust because sometimes we are able to perform the attack to exploit the attack. Not today. We were hoping that we got some information. Best luck. Now we remove the airplane. It's connected to the network. I hope it get focused the screen. And we will open where is [snorts] what is my IP address now? &gt;&gt; Yes. Yes. &gt;&gt; Yeah. The state and what's my IP address to show you that we are in Toronto &gt;&gt; in Montreal. I think it was &gt;&gt; Montreal. Okay, now that we demonstrate and we exploit attack, there is a big question that should get into your minds or at least in my hacker mind. How long will it last? Okay, we did it right. But for how long? This will last for minute, an hour, one day. If it work in my room, will work here. That is already answer right [laughter] so we started in Spain country number one is Spain two different operators we anonymize of course the information we don't want to get any enemies from the operators but all of the operators listed over there they are no one repeated they are all of them different okay so in orange the first two lines in the Spain we successfully managed to exploit the attack on 2G 3G 4G G and 5G. When we are talking about 5G is the real 5G is standalone. You know that 5G non-standalone usually nowadays is using the 4G core. So we will get into the 4G column. So we get a very satisfying reaction from our point of view. We did to we managed to exploit but we wanted more. Where in the world? Michael take me to Netherlands. We travel to Netherlands. We bought again prepaid SIM cards. That's very important. Why? Because I don't know why. I don't get it. But when we want to get 5G SIM cards, we can't. It's not available on prepaid. They ask you contract and they require you a physical address and a bank account. This is why the 5G column is not available outside the Spain. In all the countries when you when we wanted to use what they call 5G ultra or 5G plus or whatever they want to name the real 5G, we couldn't because they are always being requested to sign a contract. But anyway, we travel to the Netherlands and to Germany. Three different operators and they switch off 3G. Yes, it's trending over the world to switch off or 2G or 3G, but we exploit on 2G and we exploited the attack on 4G. We've been in April in Singapore and yeah, why not to test again with another two different operators in Asia, different country, different culture. They switch off 2G and 3G. Of course, we didn't drive the whole country. I'm talking about countries but we do this test in very specific cities right we are not war driving the whole country take this in mind and in Singapore again we could exploit the attack on 4G so yeah when we are analyzing this table is like okay 2G and 3G the older technologies at least in the packet domains they protect because all the authentication the initial authenticators we they are not successful it's not vulnerable attack but 4G is also packet network right there is no circuit domain in the 4G and the same on 5G but they are vulnerable why is not this authentication policy balance or improve it's a very good question that came up with this table and now what okay we did it we exploited the attack what could we do if we are impersonating your IP address if I do any fraud if I commit any crime policy is going to be in your house, right? Not my house because IP belongs to you. And the second factor, authentication, we wanted to check how we can abuse the attack. We pick WhatsApp because we think that this a very popular uh messaging application and you know that when you set up the application for the first time, you're required to prove your identity, your mobile identity. So again another successful exploitation of the attack. This is our big team. We are doing the go sim procedure from the laptop. We will get the information from the elementary files. It's of course accelerated for the presentation purpose not to get waiting over time is just mirrored the the sim card. We get the information we take from the huben the new go sim attack. This phone call, this phone sorry on the laptop is the victim. We will the attacker sorry we will plug the go sim. We remove the airplane mode will be connected for sure. This is why we are using the demo video. It's connected on the 4G and we open WhatsApp assistant. Right. The first things that we'll ask the user is their phone number. as we were using our personal phone numbers. Sorry, we offiscate personal phone numbers. If you want to contact me or Miguel later, we could talk. We're offiscating for standard reasons. Yeah. First method to verify is using a phone call. Okay. I allow the application and we are waiting to receive the call. So that's the And there we are. We received the phone call. We didn't answer on purpose because we wanted to test the second method. You know that usually they provide two different methods or the phone call or the SMS. So our odds are getting interesting in terms of probability of statistics because it is should be authenticated the call right again we accelerated because they were some timer we have to wait for the phone call wait one minute now we are selecting the SMS and we are waiting for the OTP the code from the SMS and you will see in the top of the screen the SMS with the code application immediately the verified identity and now we can restore any backup that the big team has enabled has. So yeah, second factor authentications are also a part. I think at the very beginning talking about some limitations, right? Some requirements. If we want to enable at commands, we need to unlock the screen. We need to get physical access to our victim to our mobile. So yeah, there are some limitations for sure and we need to study the authentication policy. Is not a simple yes or no. They are very complex. They will change from one city to another. You know that the networks they're using usually different network manufacturers. So some regions could use one manufacturer, some regions any other. So security or authentication policies may be not the the same to them. And in the same page that we have limitations, we have some let's call key facilitators. We want to bypass the security the Android security lock. Yeah. If we search on NDS by I think the keywords are lock screen bypass and we found September 2025 different vulnerabilities that will allow us to bypass the Android lock screen. Same with the ADB. ADB should use RSA or the rotation to allow the host. But sometimes ADB by default as you see at the right uh shadow server is the service they are monitoring ADB listening by default on TCP port 5555. This only 7,000 devices in the world. Yeah, it's not the same as the amount of Android devices that spread but quite a number. and some other CBES from 2023 regarding that CBE that sorry ADB could be bypass and my favorite undocumented 80 commands. If you recall I mentioned at the very beginning this 2018 uh research from the investigators but this is brand new 2025 is not something from the past. This is the simcom that has an undocumented command that will provide you with a root permission on the model. So these kind of things will make this attack I mean we wanted to show you that could be weaponized organizations like NSO or things like that when they have a yes resources to weaponize these kind of attacks could be really powerful as users we wanted to let you know some counter measures for me this is just common sense but let's go through all of these activate the PIN number if you are not using PIN number in your SIM card you know what you are exposed. We can remove SIM card from the mobile phone and get into our reader and forget about the Android security measures. We will everything for your SIM card. Never leave your phone unattended. Sure. Paranoid screen lock. Never leave your screen unlock. And if you have these commands options, sorry, 3GPP at commands. If you have USB debugging, enable them because that's the power that can lead to any potential attacker. From the network point of view, operators should review this authentication policy. as I already introduced plus these like these two Canadians operators authenticate or the initial attachment that will make this attack really complicated to be successful because we need to get this initial attach always all these authentication based on counters even if they are chain base or one of n we should review and balance them we usually found in the one of n events the number n it equals 15. If we divide 14 by 15, you will see that the result is very close to 90. A huge success of uh probability, right, for the attack. So we understand that these parameters will require operators maybe some investment, some budget, some changes, but will provide a strong authentication policy. All this work is been two years of work. We wanted to do a short presentation. If you are interested to go through all the details, we just published today on research gate the paper. So you want to take a look and dive into the details. We already mentioned that we wanted to focus on the authentication policies and not on the Android device and all these circumstances. If you want to ask any questions, please you have there the microphone. Get close to the microphones. We will be more than happy to answer any question that you may have. &gt;&gt; Well, thank you first. &gt;&gt; Thank you. &gt;&gt; I had a quick question. So, um, you guys talked a lot about the authentication. I know that that's what the paper is about, but in terms of getting those elementary files off of the SIM card, was that already broken? Was that an easy thing for you guys to do or was there any like difficulty once you have debugger access to Android? I always thought that sim cards were fairly locked down getting those elementary files. Was that piece of cake or &gt;&gt; it's not a piece of cake? We need I mean the how to get information is copy and paste. You select the identifier and you get the the content. Mhm. &gt;&gt; The problem is to map what do you need in order to get through the authentication. I mean to looks like the same legitimate SIM card towards the network. &gt;&gt; It's very complex. There is no documentation. There is nothing towards I mean we didn't find anything. &gt;&gt; Okay, I understand. But the SIM card will just freely give that information because you're the authenticator. You could if you want to increase your probability of success you can select everything copy everything and paste everything on the programmable will take more time this another way. &gt;&gt; So those are the 95. How many files did you need to copy? &gt;&gt; It's up to the operator. &gt;&gt; Who knows? Okay. Thank you. &gt;&gt; There's no uh a number I can give you. &gt;&gt; I understand. Thank you. &gt;&gt; You're welcome. &gt;&gt; Uh I'm just curious what happens with the original SIM card. Would that receive calls SMSS at the same time? Absolutely. We playing again. It's up to the operator. We have been playing all my life. I've been playing with it kind of situations. It's up to them. Usually could be a race condition. I don't know if you are up to these paging messages, how the network let the subscribers know that they have services. It's up to them how often they want to authenticate and uh how close the victim and the attacker are close to the network. Okay, I have another question. So in the 5G they have upgraded the MC to SUP and SUI keys. Does that change anything in this case or still able to do it? &gt;&gt; No, remember in the Spain we were able to success the attack on 5G standalone. &gt;&gt; Okay. &gt;&gt; Once we read the information from the SIM card, we copy because all these identities are available &gt;&gt; stored in the SIM card, right? &gt;&gt; So we get and that's it. As long as we are not getting any authentication procedure, we will manage. &gt;&gt; Gotcha. Thank you. &gt;&gt; You're welcome. &gt;&gt; Just a just a quick question. Very good um meeting by the way um presentations. Um just want to have a quick question that nowadays we are more using more and more eims especially with the new iPhone. Um just wondering if is there any difference between a physical sim and the eim? &gt;&gt; It's in our future work. Yeah, in the paper you will see that it's in the future work. there is a lot of room for future work. We were getting focused because we wanted to to to finish the the work, right? We could play with iOS. We didn't been playing with Apple iOS. We didn't playing with EIM. It's a very nice question. I really would like to give you an answer, but we'll be okay. &gt;&gt; We didn't testing with the EIM. &gt;&gt; Okay. Thank you. &gt;&gt; You're welcome. &gt;&gt; Hi. Uh during your presentation you mentioned is clone the orange sim card to a programmable uh sim card. &gt;&gt; No. &gt;&gt; Yeah. And if uh &gt;&gt; if you both in there to like like two phone and uh you received a phone call like both will receive or only one &gt;&gt; only one. Yeah. I think it's the the first question they will raise. If we have the both SIM cars connected to the network, only one can handle the service, the SMS or the call, it's up to the race condition, but only one will receive the event both of them. &gt;&gt; Uh so when you like do the clone, how you make sure the programmable SIM card receive the phone call like when you do the demonstration? &gt;&gt; Yeah, if we have physical access, we can just switch off or airplane mode, right? because we have to get the the big team phone. &gt;&gt; Okay. &gt;&gt; Okay. So, we can &gt;&gt; we we if at the beginning there are two options. If you turn the airplane mode and then you use the go sim, you will always receive the SMS or the phone calls. But if both of them are connected, it's a race condition. &gt;&gt; Okay. &gt;&gt; Another way could be to switch technology on settings. We can set the preference technology 2G. If one is connected to 4G and the other one is connected to 2G, we can play with this different radio access technology to assure to guarantee that we will receive service from the go. There are many ways to play with this kind of things. &gt;&gt; Okay, thank you. &gt;&gt; You're welcome. &gt;&gt; One last one. I just wanted to know does it leave any trace on the device that was connected to? So there's no way to discover if this happened to to &gt;&gt; I'm thinking I don't think so &gt;&gt; in the ADB maybe. &gt;&gt; I don't know. &gt;&gt; I don't think so. I'm thinking about forensics right now. &gt;&gt; Yes. &gt;&gt; But uh it's not my strongest point &gt;&gt; but I ADB sure will &gt;&gt; maybe in ADB. Yes. But I would guess in the others in the other two methods no I &gt;&gt; Yes. Because the the bassbands usually they are using volatile memory. I mean if they get the device at the same moment of the attack they could take some forensic but once the mobile is switch off everything is gone. And if when they are doing forensic from the operator point of view from the network point of view that this is usually what they are doing we are the subscriber. There is no way to distinguish between us. If we receive an identity request from the go sim and we answer with our with our email, we leave the trace &gt;&gt; but everything needs to be in place. If we didn't receive any identity request from the network, they wouldn't understand the attack. &gt;&gt; Okay. Thank you very much. &gt;&gt; You're welcome. Thank you all of you. Thank you.

Organisations named here

  • Ethon Shield
  • Federal Bureau of Investigation (FBI)
  • Quectel
  • Samsung
  • SIMCom
  • Sysmocom

CVEs named here

  • CVE-2016-4030
  • CVE-2016-4031
  • CVE-2016-4032
  • CVE-2019-16273
  • CVE-2020-0028
  • CVE-2023-20943
  • CVE-2023-43484
  • CVE-2024-0044
  • CVE-2024-31320
  • CVE-2025-26412

Technologies named here

  • Android
  • pySim-shell
  • 2G GSM mobile networks
  • 3G UMTS mobile networks
  • iOS
  • SIM-EMU
  • Wireshark
  • 4G LTE mobile networks
  • Linux
  • Windows
  • 5G Standalone and Non-Standalone mobile networks
  • ADB
  • SIMCom modems
  • Python
  • LG G4 smartphone
  • Samsung Galaxy S22
  • Samsung Galaxy A25
  • Samsung Galaxy A52
  • LG Nexus 5X
  • Android OS
  • Shadowserver Foundation
  • NIST
  • WhatsApp

Techniques named here

  • Ghost SIM attack
  • SIM swapping and cloning
  • Side-channel power analysis on smartcards
  • Android lock screen bypass
  • SMS and voice call interception for 2FA bypass