2018 · Palestine · O - Public administration and defence · Targeted mobile surveillanceware campaign against end users
Analysed 2026-11-06 by Hermes
Open this case in the tool →Targeted mobile surveillanceware campaign against end users
No DV evidenced
Alternative: none defensible
(1) There is no victim organisation to hold a strategic expectation: the row describes a targeted espionage campaign (Desert Scorpion surveillanceware, tied by Lookout to the earlier FrozenCell family) deployed against over 100 individual persons of interest in Palestine - people affiliated with Fatah, government employees, security services and students (Lookout; CyberScoop) - so the doctrinal-material and knowing-doing axes of the DV framework, which measure where an organisation's own strategy or expertise fails to reach execution or leadership, have no subject here. (2) What the record documents is the attacker's campaign, not a victim lifecycle: a long-running Facebook profile promoted a malicious chat app called Dardesh in the Google Play Store; after download and interaction it dropped a second-stage payload masquerading as a settings app that exfiltrated messages, contacts, files, location and audio (Lookout, report of 16 April 2018; CyberScoop). Entry is fully described from the attacker side (social engineering via Facebook plus delivery through an authorized app store); the victims are individual handsets. Detection came from outside: Lookout (and ClearSky, per Lookout) identified the campaign and notified Google on 3 April 2018, which removed the app and acted via Play Protect; disclosure was by the IT-security company, matching euRepoC's source_disclosure. No Palestinian organisation's containment, detection, egress governance, recovery or disclosure conduct appears anywhere in the reporting. (3) This is the case the decision rule reserves Unknown for: reporting confirms impact (surveillance of 100+ individuals, non-sensitive personal data per euRepoC) and attacker TTPs only; across all six lifecycle stages no source documents a victim-side origin-break chain, and the trust condition that is visible - users extend more trust to Play Store apps, which Lookout says decreases the vetting a user would otherwise apply - is a property of the app-store ecosystem for individual users, not a documented gap in any organisation's assurance programme, so it is described here rather than coded. The case is atypical for the framework (state-linked espionage against a population of individuals), and that is flagged in Notes. (4) Skipped: no lens sentences for Unknown; no risk marker coded because every candidate condition (individual users deceived via social media, novel multi-stage mobile malware undetected on handsets) falls under the exclusion clauses of RM24 and RM28, which require an organisational condition, and no organisation-specific gap is documented for any other marker.
Atypical case: euRepoC records a state-linked espionage campaign whose receivers are End user(s) / specially protected groups in Palestine; the DV framework has no victim organisation here, so DV-Type is Unknown, the stage/distribution keys are null and confidence is not issued. Data quality: the case file carries no receiver_name, and the victim as written in the task/case name is the campaign name (Campaign Desert Scorpion ... (2016-2017)), kept as written; the actual victim population is 100+ individual persons of interest in Palestine per Lookout and CyberScoop. The row name's 2016-2017 refers to the earlier FrozenCell-period activity of the same actor; euRepoC's own dates (start 26.02.2018, end 28.03.2018) match the two observed Dardesh app updates that Lookout reports, and the description matches the stated campaign (no description/victim mismatch beyond the name being a campaign title). Year taken from eurepoc_extra.start_date (2018); Country from receiver_country (Palestine). Sector: the method spec would leave Sector blank for a diffuse end-user campaign, but the output check requires exactly one CBS SBI entry, so it is coded O from the government-employee, security-service and public-institution affiliation Lookout and CyberScoop report among the targets; the victims themselves are individuals, not an organisation. Attribution (APT-C-23, tied to Hamas) rests on vendor technical reports (euRepoC attribution_basis: IT-security community attributes attacker; attribution_type: Technical report) and does not affect the victim-side assessment. Lookout additionally notes past operational-security failures of this actor that left exfiltrated content publicly accessible; no leaked data was accessed or used for this classification, per the research boundaries. No related_rows in the case file. Link check: lookout.com blocks automated access (HTTP 403); the page was opened and read during research. Link check: blog.lookout.com blocks automated access (HTTP 403); the page was opened and read during research. Unattended run: no consent-gated actions were required.