nodhom.com
bd_dc75a1db8ed1b862 · schema v1 · pii pii-v2
Full breach record for nodhom.com →Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group Hyflock on its public extortion blog. It has not been validated by the victim or any regulator. Treat attribution and counts as the threat actor's assertion until a regulatory filing or victim disclosure corroborates them.
Source: Ransomware.live
Post text · scraped from the leak site
Nodhom - Company Profile Nodhom is an unfunded company based in Riyadh (Saudi Arabia), founded in 2015, it is owned by a private entity named Ettesaq Ltd (https://www.ettesaq.com/). It operates as a Cloud based ERP software provider for SMBs. Nodhom has not raised any funding yet. The company has 3958 active competitors, including 58 funded and 162 that have exited. Its top competitors include companies like Workday, Oracle and SAP. Company Details Cloud based ERP software provider for SMBs. It brings together accounting, inventory, order management, procurement, HR, and more for enhanced business decisions. It allows users to manage reports, dashboard overviews, record history, system set up management, integrations, and etc. It enables user access to a subscription based pricing module. Website nodhom.com (http://nodhom.com/) Founded Year 2015 Location Riyadh, Saudi Arabia (https://tracxn.com/d/geographies/saudi-arabia/___pcaRzSx7V6lM1peTKubyaIgeBwBLDSZ-hRILoZ2k4g) Head Office: Ettesaq Company Ltd. | Palms Square, Riyadh 13322 - 3816, Saudi Arabia Contacts: WhatsApp (https://api.whatsapp.com/send?phone=966550815509&text=.) Phones: +966 55 081 5509 +966 11 243 0001 Email: [REDACTED-EMAIL] Website Contact page: https://nodhom.com/contact-us/ LinkedIn: https://www.linkedin.com/showcase/nodhom Twitter: https://twitter.com/nodhom YouTube: https://www.youtube.com/channel/UCDrztOStYh6r-8XsNyH0jrw
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Oct 1, 2026
Claim posted
—
No filing yet · watching
Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.
Claim → filing
—
Compliance clock
Not assessable
Evidence ladder
Attacker assertion only. Establishes: claim date, group, alleged victim.
Unlocks: incident narrative, operational impact. Still no compliance clock.
Unlocks: discovery date, data types, affected count, compliance clock.
Unlocks: materiality, stated response, full audit trail. Ceiling removed.
No regulatory filing corroborates this yet — it is the attacker's own assertion. Watch this entity to be notified the moment a filing corroborates or contradicts it.
Source ceiling
- actor name
- victim claim
- ransom/leak status
- discovery date
- materiality
- notification
- affected count
- confirmed data types
- compliance clock
The ✕ fields stay blank until a regulatory filing or victim disclosure lands.