株式会社ホクヨー
bd_cd24c2eabf6ce63d · schema v1 · pii pii-v1
Full breach record for 株式会社ホクヨー →Press / market disclosure — not a breach-notification filing
A media or market posting that confirms an incident but carries no breach-notification fields, so compliance clocks aren't assessable. The summary below is extracted from the coverage and machine-translated to English — verify against the source.
Summary
machine-translatedHokyo discloses system disruption due to ransomware infection; recovery complete but personal data leak under investigation | Security News Security Measures Lab. Hokyo Co., Ltd.: The company Hokyo announced that a computer system failure due to a ransomware infection occurred on March 26, 2026. Although the company claims to have completed the restoration of its systems and that its operations are not disrupted, it is currently conducting an investigation with external experts to determine if there has been a leak of personal data. Relevant parties should closely monitor the management of this incident, particularly the identification of the intrusion vector after recovery and the misuse of credentials. Linked ransomware group: safepay.
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Mar 26, 2026
Press report
—
No filing yet · watching
Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.
Attack → press
—
Compliance clock
Not assessable
Linked disclosures
Why this link?Ransomware claims (1)
- Leak Sitesafepaybd_ce0bdbb02c6bdfd32026-05-04 · +40dCandidate
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.
If an SEC 8-K, state-AG notice or victim statement lands, DisclosureLens merges it into an incident and links it here.
Source ceiling
- incident type + narrative only (may be machine-translated)
- discovery date
- materiality
- affected count
- data types
- compliance clock
The ✕ fields stay blank until a regulatory filing or victim disclosure lands.
safepay
According to ransomware.live, SafePay emerged in September 2024 as a rapidly growing ransomware operation that explicitly disavows the RaaS model and manages all operations internally, claiming over 300 victims worldwide by mid-2025 with a high-profile early attack against UK telematics firm Microlise stealing 1.2 TB of data.