Join our Newsletter — 33% off our NHI Course
Home› Guides› Mobile Spyware Infection Response Playbook: Triage, Lockdown and…
Template Incident Response & Forensics

Mobile Spyware Infection Response Playbook: Triage, Lockdown and Recovery for Targeted Phones

PDF for newsletter subscribers · free to read online

← All guides
By NHI Mgmt Group, edited by Lalit Choda Updated 27 October 2026 10 min read
On this page

When an executive, lawyer or journalist on your staff receives a vendor threat notification, or their phone starts behaving oddly after a strange message, your normal EDR-led incident process has almost nothing to work with. Mercenary spyware is installed through exploit chains, often with no click, and leaves traces that only specialist tools and trained analysts can read. This playbook template covers suspected mercenary or commercial spyware on iPhone and Android devices: how to triage without destroying evidence, when to use the Mobile Verification Toolkit (MVT), how to contain with Apple Lockdown Mode and Android Advanced Protection, and how to handle the person and the data around the device. It is written for security operations, executive protection and legal teams, and follows NIST SP 800-61 Rev. 3. Adapt the bracketed text before adoption.

How to use this template

  • Replace text in square brackets, such as [Organisation], [Mobile Lead] and [Specialist Lab], with your own names. "Must" is mandatory; "should" is recommended.
  • Decision points are marked D1 to D5. Record each decision, who made it and when.
  • Platform features and menu paths reflect Apple, Google and MVT documentation as of October 2026; re-check them yearly.
  • Background on the spyware market, vendors and infection vectors is in the Commercial Spyware Guide; device acquisition methods are in the Mobile Forensics Guide. This playbook does not repeat them.

1. Scope and triggers

1.1 This playbook applies to any [Organisation]-owned or personally owned phone or tablet used for [Organisation] business, where targeted spyware is suspected. Stalkerware installed by someone with physical access to the phone is a different case with safeguarding concerns: route it to [HR and Safeguarding] and the Spyware and Stalkerware Guide.

TriggerHow it arrivesInitial severity
Apple threat notificationAlert on the Lock Screen and in Settings, email from [email protected], banner on account.apple.comHigh
Google or Meta (WhatsApp) security warning about state-backed or targeted attackIn-account or in-app noticeHigh
Researcher, journalist or government contact saying the person was targetedDirect contact, often via [Legal]High
Suspicious message or link received by a high-risk person (one-time links, unusual iMessage or WhatsApp attachments)User reportMedium
Symptoms: unexpected reboots, battery or data use, unknown profilesUser reportLow unless the person is high-risk

1.2 Verify the notification first. Apple says it never asks recipients to click links, open files, install apps or profiles, or share passwords or verification codes, and that a genuine notice also shows when the user signs in at account.apple.com. Fake "threat notifications" are themselves a phishing lure.

1.3 Relevant ATT&CK for Mobile techniques: T1660 Phishing and T1456 Drive-By Compromise (delivery), T1658 Exploitation for Client Execution and T1404 Exploitation for Privilege Escalation (exploit chain), then collection through T1636 Protected User Data, T1429 Audio Capture, T1512 Video Capture and T1430 Location Tracking.

2. Roles and contacts

RoleResponsibilityNamed contact
[Incident Manager]Owns the case, decisions D1 to D5, keeps the circle small[Name]
[Mobile Lead]Device handling, backups, MVT runs, MDM actions[Name]
[Specialist Lab]External analysis of exploit traces beyond public indicators[Retainer or partner]
[Executive Protection]Works with the targeted person, travel and physical safety[Name]
[Legal and Privacy]Consent for analysis of personal data, privilege, law enforcement, notification[Counsel, DPO]
Targeted personGives informed consent, supplies device and backup passwords, follows lockdown advice[Name]

2.1 Discuss the case out of band: not by SMS, iMessage or WhatsApp on the suspect phone, and not in rooms where it sits. Journalists, activists and human rights defenders on staff may also be eligible for the Access Now Digital Security Helpline, which Apple recommends to notified users; it runs 24/7, is free for civil society and vets requests against its mandate, so it is not a corporate service.

3. Detection and triage

  1. Do not wipe, reset or update yet. A factory reset or major update can remove traces. Keep the device powered and charged, and note the OS version and build.
  2. Get consent in writing. MVT describes itself as a tool for consensual forensic analysis. A phone holds the person's private life; [Legal and Privacy] confirm the scope of analysis, especially for personal devices.
  3. Preserve the trigger: screenshots of the notification, the email headers, suspicious messages with sender and time. Do not tap links.
  4. Take an acquisition. For iPhone, an encrypted local backup made with the phone unlocked, plus a sysdiagnose where the [Specialist Lab] asks for it. For Android, follow the lab's collection method. MVT's own documentation warns that the extracted backup decryption key is sensitive data; store it with the evidence, not on the analyst's laptop.
  5. Run MVT with current indicators. mvt download-iocs pulls public STIX2 indicator files, including the Amnesty International investigations repository (Pegasus, Predator) and the MVT project's own indicators. Run check-backup against the decrypted backup and save JSON output; matches are written to files with a "_detected" suffix.
  6. Escalate to the [Specialist Lab] with the acquisition and MVT output, whatever MVT returns.

D1: Severity. Critical: an MVT match, a lab confirmation, or a verified vendor notification for a person with access to board, legal, M&A or government matters. High: verified notification without confirmed traces. Medium: suspicious lure received by a high-risk person. A clean MVT result does not close the case: public indicators only cover known campaigns.

OptionWhat it givesLimits
MVT in house on a backupFast check against public indicators; JSON evidenceOnly known indicators; needs an analyst comfortable with the command line
Specialist lab or civil society helplineAnalysts who know current exploit traces, can use private indicatorsScheduling, eligibility, data leaving [Organisation]
Commercial mobile forensics platformFull file system where supported, court-ready reportsCost; not all detect spyware traces
Mobile threat defence app or MDM signalsOngoing alerts across a fleetWeak against zero-click exploit chains; not a substitute for analysis

4. Containment

D2: Swap the device now? For Critical cases, issue a clean replacement immediately and keep the suspect phone powered, isolated from [Organisation] networks and away from sensitive meetings. For High, the [Incident Manager] decides with the person; a replacement is the default where they handle restricted data.

  • Lockdown Mode on Apple devices: Settings, Privacy & Security, Lockdown Mode. Apple describes it as extreme, optional protection for the very few people who may be personally targeted. It blocks most message attachment types and link previews, complex web technologies, FaceTime calls from people not contacted in the past 30 days, wired accessory connections while locked, and installation of configuration profiles. It must be turned on per device.
  • MDM interaction: a device in Lockdown Mode cannot be enrolled in MDM or supervision, but devices enrolled before it was turned on stay managed. Enrol the replacement first, then turn on Lockdown Mode. See the Mobile Device Management Security Guide.
  • Advanced Protection on Android: Settings, Security & Privacy, Advanced Protection. It blocks sideloading, guards USB access while locked, can block 2G, enables Memory Tagging Extension for supported apps, and offers optional intrusion logging stored in the cloud with end-to-end encryption. Turn on intrusion logging on the replacement so a repeat attack leaves evidence.
  • Accounts: from a clean device, sign out other sessions, rotate passwords, move the person to passkeys or hardware security keys, and review recovery email and phone. Revoke the suspect device's corporate certificates, VPN and MDM-issued tokens.

5. Eradication

  1. Do not reuse the suspect device for [Organisation] work until the lab finishes. If it must return to service, update to the latest OS, then erase and set up as new without restoring the full backup.
  2. Hunt across colleagues: people in the same team, deal or trip may be targeted together. Offer them checks and Lockdown Mode.
  3. Review what the device could reach: mail, messaging, files, authenticator apps and passkeys synced to it, and corporate apps with long-lived tokens.
  4. Feed indicators from the lab (domains, process names) into [SIEM], DNS filtering and MDM compliance rules.

D3: Data compromise? Assume content on a confirmed infected device was readable from the first trace date. [Legal] decides what that means for clients, deals and regulators.

6. Recovery

  1. Restore only data the person needs (contacts, selected files), not a full backup that may carry traces.
  2. Keep Lockdown Mode or Advanced Protection on for high-risk staff by default; accept that some websites and attachments will not work.
  3. Agree a re-check rhythm with the [Specialist Lab], for example after travel to high-risk destinations and whenever indicators are updated.
  4. Brief the person on lures specific to them and a direct route to report anything odd.

D4: Close? The [Incident Manager] closes when accounts are re-secured, the lab has reported, and any affected colleagues have been checked.

7. Communication and notification

  • Need to know: the circle is the person, the [Incident Manager], [Mobile Lead], [Legal]. Rumour about who is targeted is itself harmful.
  • Regulators: if personal data of others on the device was likely accessed, [Legal and Privacy] applies the [Regulatory Register], for example GDPR Article 33 (72 hours from awareness of a personal data breach).
  • Law enforcement and government: [Legal] decides; some national cyber centres take reports of state-backed targeting.
  • Public statements: only with the person's agreement; vendors do not attribute notifications, and Apple says it does not attribute attacks to specific attackers or regions, so neither should [Organisation] without lab evidence.

8. Post-incident review

8.1 Within [10] working days, using the Post-Incident Review and Root Cause Analysis Template. D5: decide whether the person's role joins the high-risk device programme.

8.2 Record: notification date against first trace date; time to replacement device; whether a lab was on retainer; which accounts and data were reachable; and whether the person had Lockdown Mode or Advanced Protection before the event.

Implementation guidance

Prepare before the first notification. Phase 1: list high-risk roles (board, general counsel, deal teams, travelling executives, journalists) with the Executive Protection and Digital Footprint Guide. Phase 2: put a [Specialist Lab] on retainer, keep two spare enrolled phones per site, and practise an MVT run on a test iPhone backup so the team knows the flow. Phase 3: pilot Lockdown Mode with three volunteers for a month, record what breaks, then make it the default for high-risk roles; rollback is turning it off per device. Small organisations can rely on a lab partner and spare phones; large ones should add intrusion logging and fleet signals.

Framework mapping.

AreaNIST CSF 2.0NIST SP 800-53 Rev. 5
Validate reports and notificationsRS.MA-02, DE.AE-02IR-4, IR-6
Mobile device restrictionsPR.PS-01AC-19
Containment and eradicationRS.MI-01, RS.MI-02IR-4, SI-3
Stakeholder notificationRS.CO-02IR-6
Device disposal or reusePR.DS-01MP-6

Metrics. Time from notification to replacement device in hand; percentage of high-risk staff with Lockdown Mode or Advanced Protection on; percentage of notifications triaged by a lab within [5] working days; number of colleagues checked per confirmed case; days since the last practice run.

Common failure patterns.

  • Factory resetting the phone straight away, destroying the only evidence.
  • Treating a clean MVT result as proof the device is clean.
  • Discussing the case on the suspect phone or in front of it.
  • Turning on Lockdown Mode before enrolling the replacement in MDM, then being unable to enrol it.
  • Restoring the full old backup onto the new phone.
  • Re-securing the phone but leaving passkeys, recovery details and long-lived app tokens untouched.

Standards and references

Related NHI Mgmt Group resources: Commercial Spyware Guide · Mobile Forensics Guide · Mobile Device Security Guide · Executive Protection and Digital Footprint Guide · Incident Response Guide

PDF for subscribers

Take this guide with you

Every section, table and checklist in one PDF, with links to the sources and related guides. Subscribe to our weekly NHI & AI Identity Journal and we’ll email you a download link.

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
Researched and written by the NHI Mgmt Group editorial team using AI tools, under the editorial direction of Lalit Choda. Facts are drawn from the sources listed on this page and checked by our automated quality process. Last updated 27 October 2026. Spotted an error? Use our contact page.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM and Agentic AI security. nhimg.org

PDF Downloads for Newsletter Subscribers

Get the guide

Enter your details and we’ll email you a download link.

The full guide is free to read online. The PDF is a thank you for subscribing.

Fill in all fields marked * and tick the PDF box to continue.