2025 · Romania · J - Information and communication · Data theft from exposed internal application, published on a hacking forum
Analysed 2026-07-17
Open this case in the tool →Data theft from exposed internal application, published on a hacking forum
Expertise to Execution
Evidence coverage: 3/6 stages, weight 21/60
Decisive stage: entry (tie-break: pre-breach condition) · Alternative: Strategy to Execution
(1) Orange Romania, a major telecommunications operator processing customer identity and payment data, was under GDPR Art. 32 obligations to secure the platforms holding that data, and protecting an externally reachable business application with MFA, a secure connection, IP restriction and periodic testing is a basic, well-known technical requirement - ANSPDCP's decision itself calls these basic safety measures. (2) In February 2025 the attacker 'Rey' entered the internal ticketing (back-office) application through exploited vulnerabilities and a fraudulently obtained internal user's credentials, took roughly 12,000 files / 6.5GB, and after Orange refused to negotiate published 556k email addresses, phone numbers, CNPs, subscription details, partial card data, identity-document copies and IBANs on a hacking forum; ANSPDCP fined Orange 80,000 EUR in July 2026 for Art. 32, finding the platform publicly exposed without VPN, MFA or IP restriction and its security never periodically tested. (3) The classification rests on the entry stage: the unmet expectation is specialist-level and technical (standard controls and credential hygiene that needed no strategic decision to exist), and the chain broke in execution - the controls were simply not realised in the platform's architecture, with no source showing leadership knew of and deferred them; the regulator's own finding supplies the mechanism, so this is not reasoning from the attacker's technique. The egress stage shows a secondary Strategy-to-Execution pattern (crown-jewel data held unclassified and unminimised in a back-office tool), and it won a tie-break against it: the pre-breach entry condition is the stage furthest from the breach moment. The attacker's dwell-time claims are unverified and are not load-bearing; detection rests on inference. (4) RM22 (Expertise to Execution lens): authentication protections were not operationalised on the reachable system - ANSPDCP found MFA absent on the ticketing platform and Orange's own notification states the attack was made possible by an internal user's fraudulently obtained credentials, letting the attacker log in as a legitimate user (causal role: Enabling). RM27 (Expertise to Execution lens): the secure configuration of an externally reachable internal platform was not maintained - the regulator found it exposed on the public internet without a VPN connection or IP-based access restriction (causal role: Enabling). RM16 (Expertise to Execution lens): data ownership and classification did not reach the ticketing application - CNPs, identity-document copies, banking data and credentials sat in a non-critical back-office tool, and BleepingComputer verified records more than five years old and expired card data, so far more was exposed than the tool's purpose required (causal role: Amplifying). RM34 (Expertise to Execution lens): detection never surfaced the intrusion - the incident came to light only through the attacker's forum publication after failed extortion, with no internal detection documented anywhere and the attacker claiming a month of undetected access (causal role: Obscuring).
RM22 — Authentication / credential exposureRM27 — Configuration hardening / external exposureRM16 — Data governance / minimisation gapRM34 — Monitoring / detection / alert-handling gapinformationisbeautiful row: description matches HIBP's OrangeRomania entry (556.6k addresses, added 27-02-2025) for the February 2025 incident; the HIBP page was used only as a lead - no leaked data was consulted. The ANSPDCP decision of 17-07-2026 covers two incidents: the Art. 32 finding (80,000 EUR) concerns this row's ticketing platform; the Art. 25 fine (20,000 EUR) concerns a separate mobile-app invoice-disclosure incident and is not part of this classification. Actor attribution rests on the attacker's own claim reported by BleepingComputer (HellCat affiliate 'Rey'); Orange called the March 2025 Babuk republication of the same leak not a new attack. Attacker claims of over a month's access and about three hours of undetected exfiltration are unverified and were used only for the non-decisive detection stage, marked inference. Orange's public framing of a non-critical application with no impact on customers sits uneasily against the CNP, identity-copy and IBAN data the regulator confirmed was stolen; this is post-breach framing, so RM44 (which requires a pre-breach statement) was not coded. An earlier ANSPDCP fine against Orange Romania (investigation completed December 2024, published 27-01-2025, excessive retention of identity documents) concerns a different processing matter, so RM21 was not coded for limited comparability. Public disclosure was preceded by the attacker's leak, but the Art. 33 notification to ANSPDCP was made by the operator and the regulator found no notification failing for this incident.