44. Mobile Device Security – Android, iPhone, Bluetooth and Wi-Fi
44.4 Signs a Phone May Be Compromised – Practical Checklist
Quick answer: the short, self-contained version of this lesson is the guide Signs Your iPhone May Be Compromised.
No invented percentages. Symptoms can be malware – or a bad battery / chatty app. Checklist → investigate → do not panic-format first.
Suspicious signals (combine, don't obsess on one):
- Unknown apps you did not install; icons that vanish but process remains
- Accessibility / Device admin granted to apps you do not recognise
- Battery / data use jumps with phone idle (still check which app – not proof alone)
- Settings changed: unknown VPN profile, proxy, APN, or configuration profile
- SMS / call oddities: 2FA messages for logins you did not start
- Account alerts: Google / Apple / bank "new sign-in" you do not recognise
- Overlays that ask for bank PIN outside the real bank app
- Friends report spam from your WhatsApp / email
Document: screenshot, note time, do not factory-reset before capturing basics if company IR needs evidence – then follow 44.5.
| Red team (attacker) does | Blue team (defender) detects / stops |
|---|---|
| Hides malware icon; keeps Accessibility | Periodic permission audit; MDM inventory |
| Steals session cookies / tokens quietly | Account login alerts; revoke sessions early |
| Uses overlay on banking app | Official bank apps only; warn on fake skins |
Ravindra Bagale's Tip
Students go straight for a factory reset and ignore the evidence and password reuse. Checklist → change passwords from a clean device → then wipe. Remember this.
Ravindra Bagale's Tip – मराठी
Students एकदम factory reset मारतात आणि evidence / password reuse कडे दुर्लक्ष करतात. Checklist → clean-device वरून password change → मग wipe. हे लक्षात ठेवा.
Ravindra Bagale's Tip – हिंदी
Students सीधे factory reset कर देते हैं और evidence / password reuse को नज़रअंदाज़ करते हैं. Checklist → clean-device से password change → फिर wipe. यह याद रखो.
Lab
Pair with Zoya: she lists 8 checklist items; you mark which need MDM screenshot vs home-user action. Fictional Shraddha Bagale staff phone – write 6-line "first hour" notes. No scanning classmates' phones.
Extended teaching notes
Why this lesson matters
Cameras, sensors and plant controllers often ship with weak defaults. Segment them from IT, change passwords, block inbound internet, and watch outbound traffic.
Real examples
Global: Mirai showed what default passwords on routers/cameras can do at scale. Indian SME (sample): a factory puts PLCs on a separate VLAN reachable only via a jump host.
Mini case study
Suppose we are on a purple-team exercise for an Indian mid-size company (sample data). Red notes a technique from this lesson against a lab clone. Blue must show the control that stops it, the log that would have fired, and the ticket that hardens production. That is the standard this course trains you for.
Defender's worksheet (do this today)
- Write the lesson title, date and the exact lab target you are allowed to use.
- List three owned systems (VMs, apps, or cloud accounts) where this lesson applies.
- Run one safe check from the lesson on a lab system only. Paste the command and output.
- Write a two-sentence fix you would give a teammate.
- Name one related public advisory (CERT-In, CISA, NVD, or a vendor bulletin) with its date.
Indian workplace (sample data)
Suppose we are a junior analyst at Infosys, TCS, Wipro or a fintech SOC in Bengaluru/Pune. Turn this lesson into one checklist item with an owner, a due date and a place to store evidence (ticket + screenshot).
Global practice
Compare your notes with OWASP, CIS Benchmarks, NIST CSF/IR guidance or a cloud Well-Architected security question. Write five lines on what overlaps.
Everyday analogy
Explain the risk and the fix to a family member without jargon. If they can repeat the warning, you understand it well enough to teach juniors.
Key terms
- Control: a safeguard (patch, config, process, detection).
- Finding: a weakness backed by evidence.
- Remediation: the fix plus how you verified it.
- Scope: systems you have written permission to touch.
- Least privilege: only the access the task needs.
- Defence in depth: several layers so one failure does not end the story.
Common mistakes
- Skipping written permission "just for a quick scan".
- Practising on hostel, office or public targets without authorisation.
- Collecting tool output without writing the fix.
- Copying attack steps onto production to "verify". Defenders verify with versions, configs and patches.
- Publishing screenshots that contain secrets, cookies or internal hostnames.
Recap
- Evidence, fix, owner, date.
- Own lab only.
- Fix > spectacle.