CYBER INCIDENTS → SECURITY DECISIONS

Beyond the breach.
What it means for your defenses.

What happened, how it changes your security posture, and which teams should pay attention. Thoughtful breach analysis in English and Japanese.

Source-led reporting. Practical next steps.Read the latest

Latest analysis

A closer look. A clearer next step.

38 articles

Lawson store in Minamisōma, Fukushima. Archive photo, 2008; it shows a store, not the systems involved.

Photo: Kuha455405, CC BY-SA 3.0, via Wikimedia Commons (cropped)

Lawson ID: 2.15 million accounts leaked through the app's own “show me my data” mechanism.

Names, plus phone numbers, addresses and possibly dates of birth, for 2,155,345 Lawson ID accounts; Lawson corrected on 24 October that email addresses did not leak. What to check.

SIEMEmail SecurityIT OperationsLegal / PrivacyThird-party Risk
·Updated ·15 min readRead the analysis

Photo: L26, CC BY 3.0, via Wikimedia Commons (cropped)

Sagawa Express: when a parcel-tracking lookup puts 100 days of delivery data in scope.

Sender and recipient details for about 100 days of parcels may have leaked through a tracking lookup. What that means for your own public lookup services, and for companies that ship with a carrier.

Third-party RiskIT OperationsLegal / PrivacyEmail SecuritySIEM
·Updated ·12 min readRead the analysis

Burger King at Aeon Lake Town, Koshigaya, Saitama. Archive photo, 2010; it shows a restaurant, not the systems involved.

Photo: Wiki591801, CC BY 3.0, via Wikimedia Commons (cropped)

Burger King Japan app breach: about 11.18 million member records, and a risk score for what the company exposes online.

BK Japan says its app's member system was accessed from 2 to 7 October. What leaked, what the dates show, and an outside-in risk card for its internet-facing systems, scored without the details.

Email SecuritySIEMIT OperationsLegal / PrivacyThird-party Risk
·15 min readRead the analysis

Times CAR car-sharing signage and a vehicle. Archive photo, 2017, showing the former Times Car Plus branding.

Photo: Carauto, CC BY-SA 4.0, via Wikimedia Commons (cropped)

Times Car: ID documents kept for seven years, and a staff list for phishers.

About 6.6 million accounts and identity documents for 1.6 million. Updated with Japanese licence images for sale on a dark-web site and 40,000 lawsuit sign-ups.

Legal / PrivacyThird-party RiskEmail SecuritySIEMIT Operations
·Updated ·19 min readRead the analysis

Official logo: © Daiwa Securities Co. Ltd.. Source. Shown to identify the subject of independent reporting.

Daiwa supplier incident: possible exposure of 220,000 records and what security teams should do.

Daiwa’s supplier inquiry-data incident explained: reported scope, unknowns, fraud implications, team actions and scoped KQL/Splunk hunting templates.

Third-party RiskSIEMEmail SecurityEDRLegal / PrivacyIT Operations
·Updated ·15 min readRead the analysis

Official logo: © GMO Research & AI, Inc.. Source. Shown to identify the subject of independent reporting.

infoQ: every member's record taken, and ¥2.87 million in points turned into Amazon gift codes.

A software vulnerability exposed all 948,498 records of the GMO survey site infoQ, and 611 accounts had points exchanged without consent. What points operators, SOCs and members should check.

IT OperationsSIEMEmail SecurityLegal / PrivacyThird-party Risk
·10 min readRead the analysis

Official logo: © Osaka Metropolitan University. Source. Shown to identify the subject of independent reporting.

Osaka Metropolitan University: ransomware on the virtualisation platform, about 500 servers down and most backups encrypted.

All five campuses lost their systems on 2 October. Data on at least 130,000 students and graduates may have leaked. What a shared virtualisation platform and reachable backups mean for recovery.

IT OperationsSIEMEDRLegal / PrivacyEmail SecurityThird-party Risk
·11 min readRead the analysis

Election operations in practice: a polling station in Higashi-Osaka, 2014. Illustrative archive photo; no incident at this location is alleged.

Photo: MASA, CC BY-SA 4.0, via Wikimedia Commons (cropped)

Election security: protect voter data, operations and evidence.

An evidence-led analysis of election security: identity, voter data, suppliers, DDoS, AI impersonation, recovery and scoped KQL/Splunk examples.

SIEMEDREmail SecurityIT OperationsThird-party RiskLegal / Privacy
·15 min readRead the analysis

Hardware security keys illustrate phishing-resistant authentication. The pictured products are not alleged to be compromised.

Photo: Tony Webster, CC BY 2.0, via Wikimedia Commons (cropped)

TA419: the MFA prompt was real, and the session was still stolen.

A China-aligned actor that targets think tanks in the US and Japan relays Microsoft's real sign-in through a fake browser window. What stops it, who acts, and how to hunt for it.

Email SecurityIT OperationsSIEMEDRLegal / Privacy
·16 min readRead the analysis

The Pentagon, photographed in 2018. Context image for the personnel-data report; not a photograph of the affected system.

Photo: Touch Of Light, CC BY-SA 4.0, via Wikimedia Commons (cropped)

Pentagon personnel-data exposure: patching does not close the data question.

A long reported exposure window shifts the review toward retention, historical evidence, data ownership, and targeted impersonation.

SIEMLegal / PrivacyIT OperationsEmail Security
·3 min readRead the analysis