Join our Newsletter — 33% off our NHI Course
Threats, Abuse & Incident Response

SIM Hijacking

← Back to Glossary
By NHI Mgmt Group Updated November 16, 2026 Domain: Threats, Abuse & Incident Response

SIM hijacking is the takeover of a mobile phone number by moving it to a different SIM card or eSIM under an attacker’s control. It works by abusing mobile carrier account recovery or support processes, then intercepting SMS-based one-time codes, password resets and calls tied to the number.

How SIM Hijacking Works

SIM hijacking is not a device hack in the usual sense, it is a control-plane takeover of the phone number itself. The attacker manipulates a carrier’s recovery or support workflow so the number is reassigned to a different SIM or eSIM, allowing the attacker to receive calls and text messages meant for the victim.

That makes the number a high-value trust anchor. Many services still treat possession of the phone number as evidence of account control, so hijacking it can bypass downstream protections that depend on SMS delivery or callback verification.

Why SIM Hijacking Is Dangerous

The main danger is that the attacker inherits the victim’s number without needing the handset. Once the number is ported or reactivated elsewhere, SMS one-time codes, password reset links, and voice calls tied to that number can be intercepted or redirected.

This is especially risky where the phone number is used as a recovery channel for banking, email, and identity platforms. A single successful takeover can cascade into broader account compromise when the number remains a shared recovery factor across multiple services.

Where Exposure Comes From

Exposure usually starts with carrier records, support scripts, or account recovery checks that can be socially engineered, guessed, or bypassed. Organisations should assume that phone-number control is only as strong as the weakest carrier-facing recovery path and any related customer-service exceptions.

The practical exposure review is straightforward: inventory which accounts use SMS or voice to recover access, identify where a number is a sole or primary factor, and verify whether the carrier offers stronger anti-port or anti-swap safeguards. NIST’s Digital Identity Guidelines are a useful reference point for moving away from SMS as a high-assurance authenticator, and the SIM Swap Fraud Guide covers the carrier-side controls and detection patterns in more depth.

Remediation and Detection

When SIM hijacking is suspected, the first priority is to restore control of the number and then invalidate any trust that was granted through it. That typically means resetting passwords, revoking active sessions, replacing recovery methods, and rotating any credentials or secrets that were delivered or reset through the compromised number.

Detection is partly operational and partly behavioural. Unexpected loss of mobile service, sudden inability to receive SMS, unexplained login prompts, or reset notifications can all indicate that the number has been moved. For the response workflow, carrier contact, account recovery review, and post-incident session review should be treated as one incident rather than separate events. The NIST Cybersecurity Framework 2.0 is a sensible organising model for the detect, respond, and recover work that follows.

Risk and Threat Considerations

SIM hijacking is dangerous because it turns a telecom support process into an account-takeover path. The attacker does not need malware on the phone if they can capture the number and the messages or calls that the organisation still treats as proof of identity.

Failure mechanism: Weak carrier verification, over-trusted SMS recovery, and reused number-based authentication let an attacker intercept authentication traffic and defeat account recovery protections.

Impact: The result can be mailbox takeover, financial fraud, loss of access to connected accounts, and persistent compromise if sessions and recovery factors are not revoked promptly.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

NIST SP 800-63, NIST SP 800-53 Rev 5 and CIS Controls v8 set the governance and control requirements practitioners need to meet.

FrameworkControl / ReferenceRelevance
NIST SP 800-63Digital Identity GuidelinesDefines authenticator assurance and discourages weak SMS-based recovery for high assurance
Recommendation — Prefer phishing-resistant authenticators and reduce reliance on phone-number based recovery for sensitive accounts.
NIST SP 800-53 Rev 5IA-5 — Authenticator ManagementPhone-number recovery often depends on managed authenticators and reset flows
IA-2 — Identification and Authentication (Organizational Users)User access decisions are affected when SMS resets and phone-based verification are abused
Recommendation — Manage authenticator issuance, rotation, and revocation so a hijacked number cannot sustain access. Require stronger authentication for users whose accounts could be reset through a hijacked number.
CIS Controls v8CIS-6 — Access Control ManagementLimits who can use recovery paths and how access is reassigned after compromise
Recommendation — Restrict recovery pathways and remove access quickly when a phone number compromise is suspected.

Practitioner Guidance

Why practitioners should care: SIM hijacking is one of the clearest examples of why SMS should be treated as a low-trust recovery path, not a strong possession factor. If a service depends on the phone number for resets, alerts, or step-up verification, the number itself becomes part of the attack surface.

Governance implication: Decide which accounts are allowed to use phone numbers for recovery, and require stronger methods for high-value users and administrators. Where possible, move critical recovery and authentication paths to phishing-resistant methods so a carrier-side incident cannot cascade into broader compromise. For organisations building a formal control set, NIST SP 800-53 Rev 5 Security and Privacy Controls provides useful control language around identification, authentication, and auditability.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on November 16, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org