2023 · India · O - Public administration and defence · Social media account takeover
Analysed 2026-11-06 by Hermes
Open this case in the tool →Social media account takeover
Strategy to Execution
Evidence coverage: 1/6 stages, weight 8/60
Decisive stage: entry (clearest evidence) · Alternative: Expertise to Execution
(1) The strategic expectation at the victim was explicit: a senior officer stated that everyone in the cyber cell is required to use secure platforms such as iOS or Microsoft, with stronger firewall and malware protection, whenever they log into the official pages or websites as an admin. (2) In practice, an admin in the cyber cell logged into the verified Facebook page from an Android device - described by the officer as not a secure platform against malware - clicked a link containing malware sent by the attackers, and lost admin control; the page was defaced for several hours (renamed to Bidhannagar City, banner changed) until control was regained through Meta. (3) The officer's own statement that the protocol wasn't followed and we faced the attack shows a doctrinal expectation that existed and was communicated but was not realised in the operational routine of the admins: the break is in execution, not in any leadership decision - the knowing-doing gap sits between the protocol and the admin's device practice. The classification rests on the entry stage (clearest evidence, the only stage with a documented victim-side gap); detection was within hours, there was no data egress, recovery via Meta succeeded the next morning, and a complaint was filed - those stages show no documented gap, so the entry vector is load-bearing here and is documented from the victim's own account, not inferred. RM11 (Strategy to Execution lens): the specific existing admin-device platform protocol was not translated into the admins' actual login routines, as the officer himself attests (causal role: Perpetuating). RM24 (Strategy to Execution lens): the awareness and acceptable-use requirement for admins was not enforced as an effective procedure, so an officer with page-admin rights clicked an attacker's malicious link (causal role: Enabling). RM28 (Strategy to Execution lens): endpoint and malware-protection requirements were not enforced across devices - the admin logged in from an Android handset explicitly described as unprotected against this kind of malware (causal role: Enabling).
RM11 — Policy-practice gapRM24 — Human-factor / social-engineering susceptibilityRM28 — Endpoint / malware-protection gapThe description matches the stated victim (no data-quality issue). The whole mechanism rests on one Times of India article (10-07-2023, reprinted in full by ET CISO) quoting an unnamed senior police officer - the protocol, the Android login and the malicious link are the victim's own unattributed account, not an independent forensic finding; the initial explanation given, a random virus attack, is the officer's framing. Actor unattributed (EuRepoC: Not attributed); a complaint was lodged with the Cyber Crime police station but no follow-up reporting on the investigation or arrests was found in later searches. No data breach, disruption or economic impact (EuRepoC impact fields all nil); hijacking scored at intensity 1 (empowerment). TOI page opened but body not extractable in this environment; the full identical text was read on the ET CISO reprint, cited first. The EuRepoC mitre_initial_access value (Phishing) was used as context only.