← Breach analysis by the Dual Vulnerabilities framework

MENA government & oil-and-gas entities espionage (Gaza Cybergang, 2016)

2016 · MENA region · O - Public administration and defence · APT espionage campaign via spear-phishing with data theft

Analysed 2026-11-06 by Hermes

Open this case in the tool →

What happened

APT espionage campaign via spear-phishing with data theft

Dual vulnerability type

Expertise to Execution

Evidence coverage: 3/6 stages, weight 19/60

Decisive stage: entry (clearest evidence) · Alternative: Strategy to Execution

Why this classification

(1) The victims in this row are government entities and an unnamed oil-and-gas organisation in the MENA region; as a critical-energy target the organisation was expected to keep its Office estate patched against a publicly fixed remote-code-execution vulnerability and to run monitoring and egress controls able to see a commodity RAT. No source documents any victim-specific doctrine, so the expectation is sector-grounded. (2) In practice, from June 2017 the campaign sent spear-phishing lures with malicious RTF documents exploiting CVE-2017-0199 - a vulnerability whose Microsoft fix had been available since April 2017 - on non-patched Windows systems, installed Downeks/Quasar/Cobaltstrike RATs, and at one oil-and-gas organisation in the region infiltrated systems and pilfered data for more than a year until external Kaspersky researchers found the intrusion in mid-2017. (3) The classification rests on the entry stage, where both DV questions are evidenced: the knowledge that was not acted on was material (a published, available patch), and the chain broke in execution (exploited systems remained non-patched roughly two months after the fix); this is a gap within the material column, Expertise to Execution. The detection and egress stages show the same material-column pattern - a >1-year undetected dwell time with discovery by an outside party, and a year of data exfiltration that was never interrupted - but no source states why those controls failed, so their origin/break readings are inference and they corroborate rather than decide; the doctrinal column (leadership knowledge or strategy) is simply undocumented for these victims, which is why Strategy to Execution is not chosen. The spear-phishing vector is the attacker's move and not load-bearing; the victim-side condition is the unexecuted patch. (4) RM18 (Expertise to Execution lens): CVE-2017-0199 was known and remediable from April 2017, yet the June-July 2017 attacks ran on non-patched victim systems, patch execution lagging behind the published fix (causal role: Enabling). RM34 (Expertise to Execution lens): detection tooling and alert handling at the oil-and-gas organisation did not surface a year-long Cobaltstrike/Quasar presence, and it took an external vendor to notice, so the activity stayed invisible (causal role: Obscuring). RM35 (Expertise to Execution lens): data pilfered through the RAT's file-collection and upload capability left the network for more than a year without being detected or interrupted at a critical-energy operator, amplifying the intelligence impact (causal role: Amplifying).

Evidence by stage

Risk markers

Sources

Notes

Data quality: the row's name field (used as the victim label) holds the actor name 'Gaza Cybergang aka Molerats (APT)', not a victim organisation; per the description the actual victims are government entities and oil-and-gas organisations in the MENA region, and the DV is assessed against those victims. They are unnamed, so the classification reflects the vendor-documented campaign pattern, strongest at the single oil-and-gas victim with the >1-year dwell time. Country taken from eurepoc_extra.receiver_country, which is a region ('Mena Region'), not a country; multi-organisation campaign. Year from eurepoc_extra.start_date (01.01.2016); the documented CVE-2017-0199 spike dates from June 2017, within the recorded campaign window. Sector set from the dataset's first receiver category (Government / ministries); energy (D) applies to the oil-and-gas victims as well. The kaspersky.de article (SAS 2019, SneakyPastes) describes the group's later 2019 campaign and is cited as context on the group only. Social-engineering success (political lures) is documented but RM24 was not coded: no source shows the victim-side awareness/verification condition the marker requires. Disclosure was by the IT-security company (source_disclosure), so the response stage yields no victim-side evidence.