← Breach analysis by the Dual Vulnerabilities framework

HGS push-service hijack and data-theft claim (hades_hgs, 2024)

2024 · Turkey · H - Transport and storage · Extortion via compromised push-notification service, with unverified claim of mass data theft

Analysed 2026-11-06 by Hermes

Open this case in the tool →

What happened

Extortion via compromised push-notification service, with unverified claim of mass data theft

Dual vulnerability type

Expertise to Execution

Evidence coverage: 1/6 stages, weight 8/60

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

Why this classification

(1) The expectation at a state-run toll operator serving millions of drivers, integrated with a third-party push-notification service, is that service credentials stay server-side and access to them is restricted - the vendor (OneSignal) itself published this practice and recommended IP allow-listing. (2) In practice the OneSignal API keys were embedded in the client-side files of the shipped HGS app, two young hackers extracted them and pushed profanity and a $25,000 ransom demand to users, and claimed - without verification, against PTT's explicit denial - that a database of 5 million users' personal and financial data had been taken. (3) The gap is within the material column: the remedy was known, published technical knowledge held by the specialists who built the integration, and it was never realised in the application's architecture; no source documents any strategic artefact being deferred or any leadership decision failing, so this is Expertise to Execution, resting on the entry stage (the only stage with a documented gap; the egress stage is contested and unverified and is not load-bearing). The entry vector here IS the whole documented incident, so it is load-bearing; the classification does not rest on the attacker's technique but on the victim's unimplemented key-handling practice. RM29 (Expertise to Execution lens): the OneSignal push API key sat as a secret inside the client-side code of the production app, a secure-development practice the app's own technical teams were expected to apply but did not, which is what let the attacker use the victim's own messaging channel (causal role: Enabling). RM27 (Expertise to Execution lens): the push API accepted calls from anywhere - the recommended IP allow-list and configuration hardening of the integration were absent, leaving the notification service externally exposed (causal role: Enabling). RM13 (Expertise to Execution lens): trust in the OneSignal SaaS integration was not matched by victim-side safeguards on the shared boundary; the provider's platform itself was never breached, so the failure sits at the unverified, unhardened third-party integration the technical team operated (causal role: Enabling).

Evidence by stage

Risk markers

Sources

Notes

The row's description presents the theft of data of over 5 million users as fact; reporting confirms only the hijack of the app's push-notification channel (10 December 2024) - the database-theft and Dark-Web claims come from the attackers themselves (karar.com, 14 December) and PTT officially denied any data loss; the EuRepoC row's own intelligence_impact also scores it as minor exfiltration with no leaking. The row dates the incident 13/14 December 2024, the push-service attack itself ran on 10 December 2024. Suspects' claim that the attack was 'a joke' is their own statement as reported by press. The same actor handle later claimed a Turknet breach (Türkiye Today, background only, not cited in the scoring). The attribution-source lead medyanotu.com could not be opened (extraction failed); the arrest facts were taken from Dünya and HaberEkspres instead. No consent-gated actions were needed in this run.