{ "id": "f8155a56-aba6-4e1a-abfa-37eb8c34ace0", "created_at": "2026-04-09T02:24:19.754766Z", "updated_at": "2026-04-10T03:36:01.416488Z", "deleted_at": null, "sha1_hash": "92d02bb62451bedf62a941ff4465f416aa484d7f", "title": "One month later, Ranhill still hasn't fully recovered from cyberattack - DataBreaches.Net", "llm_title": "", "authors": "", "file_creation_date": "0001-01-01T00:00:00Z", "file_modification_date": "0001-01-01T00:00:00Z", "file_size": 112898, "plain_text": "One month later, Ranhill still hasn't fully recovered from\r\ncyberattack - DataBreaches.Net\r\nPublished: 2023-08-31 · Archived: 2026-04-09 02:06:36 UTC\r\nOn July 26, DataBreaches reported that DESORDEN had attacked  Ranhill Utilities Berhad, a provider of water\r\nand power supply in Malaysia.\r\nAt the time, DESORDEN claimed, in part:\r\nThe initial data breach was initiated on Nov 2021. For over 18 months, DESORDEN has been in their\r\nsystems. On 17th July 2023, our group infiltrated their LIVE Billing System which handles online\r\npayment for more than a million of their customers. Between 18th July to 19th July, DESORDEN stole\r\nall of the databases in their billing system, deleted their backups and removed the databases entirely. On\r\n19th July 2023, DESORDEN informed Ranhill management about the data breach and provided a\r\ndeadline to respond by 21st July 2023. On 20th July, Ranhill company took all of their systems offline\r\nand brought the systems back online on 21st July 2023, without responding to DESORDEN (Live\r\nBilling System was still unrecoverable). On 23rd July 2023, DESORDEN launched a 2nd attack on\r\ntheir critical online system, AquaSmart which is Ranhill operational tool for managing water-related\r\nactivities, repair scheduling and reservoir monitoring. Since 23rd July 2023, Ranhill systems are mostly\r\ntaken offline without notifying the public.\r\nRanhill did not respond to this site’s inquiries at the time.\r\nMore than one month later, it appears that Ranhill has still been unable to fully  recover. DataBreaches previously\r\nreported complaints on Facebook about the payment app not working. It still isn’t working, and Ranhill does not\r\neven reply Facebook to customers who are frustrated and complaining about the inability to pay, as a “Wake up,\r\nRanhill” message posted a few days ago suggests. Another customer complains because they have not received\r\ntheir bills for the past three months and can’t get them because the website is (still) down.\r\nRanhill has not responded to them.\r\nhttps://www.databreaches.net/one-month-later-ranhill-still-hasnt-fully-recovered-from-cyberattack/\r\nPage 1 of 3\n\nSo What Has Ranhill Done In Response to the Attack?\r\nIt’s hard to tell. Ranhill never replied to DataBreaches’ inquiries in July, and DataBreaches emailed them again on\r\nAugust 27 with a cc: to their investors relations email address.  A copy was also sent to the country’s data\r\nprotection regulator.  In that email to the firm, DataBreaches posed a number of questions:\r\n1. Did the attack impact the production or delivery of clean water at all?\r\n2. Has Ranhill been unable to restore the payment system? People complain about months of impairment. Why\r\nhasn’t Ranhill even answered these customers on Facebook?\r\n3. Has Ranhill notified law enforcement about the attack? If so, when did it notify them?\r\n4. Has Ranhill notified any regulators about the attack? If so, which regulators and when did it notify them?\r\n5. Has Ranhill notified employees that their information has been stolen? If so, when did it notify them and what\r\nis the company doing to help them protect themselves from fraud?\r\n6. Has Ranhill notified all of its investors about the massive data theft and theft of backups? If so, when and how\r\ndid it notify them?\r\nNo response has been received from Ranhill or the data protection regulator.\r\nhttps://www.databreaches.net/one-month-later-ranhill-still-hasnt-fully-recovered-from-cyberattack/\r\nPage 2 of 3\n\nAt one point, DESORDEN had indicated that the data would be put up for sale, but DataBreaches has not seen\r\nany sign of that yet.\r\nSource: https://www.databreaches.net/one-month-later-ranhill-still-hasnt-fully-recovered-from-cyberattack/\r\nhttps://www.databreaches.net/one-month-later-ranhill-still-hasnt-fully-recovered-from-cyberattack/\r\nPage 3 of 3", "extraction_quality": 1, "language": "EN", "sources": [ "MISPGALAXY", "Malpedia" ], "references": [ "https://www.databreaches.net/one-month-later-ranhill-still-hasnt-fully-recovered-from-cyberattack/" ], "report_names": [ "one-month-later-ranhill-still-hasnt-fully-recovered-from-cyberattack" ], "threat_actors": [ { "id": "e5ccc758-f2a5-417b-ba5c-70edf39bc048", "created_at": "2022-10-25T16:07:24.481513Z", "updated_at": "2026-04-10T02:00:05.005021Z", "deleted_at": null, "main_name": "Desorden", "aliases": [], "source_name": "ETDA:Desorden", "tools": [], "source_id": "ETDA", "reports": null }, { "id": "b4f79ca0-e94b-4abe-a61e-ea3d2a2458ad", "created_at": "2022-10-25T16:07:24.444096Z", "updated_at": "2026-04-10T02:00:04.994412Z", "deleted_at": null, "main_name": "ALTDOS", "aliases": [ "0mid16B", "ALTDOS", "Desorden", "GHOSTR" ], "source_name": "ETDA:ALTDOS", "tools": [ "Agentemis", "Cobalt Strike", "CobaltStrike", "cobeacon" ], "source_id": "ETDA", "reports": null } ], "ts_created_at": 1775701459, "ts_updated_at": 1775792161, "ts_creation_date": 0, "ts_modification_date": 0, "files": { "pdf": "https://archive.orkl.eu/92d02bb62451bedf62a941ff4465f416aa484d7f.pdf", "text": "https://archive.orkl.eu/92d02bb62451bedf62a941ff4465f416aa484d7f.txt", "img": "https://archive.orkl.eu/92d02bb62451bedf62a941ff4465f416aa484d7f.jpg" } }