SHINDO2
Mam Create
RansomwareSize not disclosed
LEAK UNCLEARInvestigating
Open in the live monitor ▶- Disclosed
- Apr 8, 2026
- Detected
- Apr 7, 2026
- Detection to disclosure
- 1 day
- Leak
- Unknown
- Type
- Ransomware
- Status
- Investigating
- Security spend
- Not checked yet
- Compensation
- Not announced
What leaked
UnspecifiedData including personal data (no leak confirmed)
Who is affected
- Stakeholders (details unknown)
Cause
Ransomware encrypted some internal servers
Timeline
- Detected
- First disclosure
Response
- Blocked the entry point
- Forensic investigation
Disconnected affected systems; investigating and restoring with outside experts and police
What you should do
- Expect targeted phishing posing as HR or interview contacts
- Check the company's notice to see if you're affected
Lessons for companies
- Offline backups with restore drills; segment the network
- Report to the PPC: preliminary in 3–5 days, final in 30 (60 if malicious)
- Run red teaming and AI-assisted hardening, and publish how much you invest
Sources
- Cybersecurity-jp.com News · Apr 16, 2026