Village Building
bd_622847133301097f · schema v1 · pii pii-v1
Full breach record for Village Building →2 incidents on fileThreat-actor claim — not a regulatory filing
This row is a claim by the ransomware group INC Ransom 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
Village Building Co. delivers an outstanding return to our shareholders and investors whilst balancing the entrepreneurial spirit of Village with best practice risk management and corporate governance. This is achieved through the creation of well planned, highly liveable and environmentally responsible urban communities predominately within Australia's eastern capital cities and urban corridors. At Village, we strive to create value for money opportunities for homebuyers across the market. What's in a name? Our name, Village Building Co., reflects our desire to not only develop land and construct housing, but to also create entire communities or villages. It also reflects the understanding that the company's success is reliant on its relationships with its stakeholders in the same way that the success of a community is reliant on the collaboration of its residents. Our stakeholders include our shareholders and other investors, employees, financiers, suppliers, customers, local communities and relevant governments.
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Apr 22, 2024
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.