Japanese Hotel Chain Ransomware Hit Business Systems but Not Membership Server

A ransomware infection at the Washington Hotel chain in Japan, reported at around 22:00 local time on 13 February 2026, affected business systems. A separate membership server was reported unaffected.

That second sentence is the entire file, and it is the kind of detail that normally goes unremarked because nothing happened.

This desk files intrusions that succeeded, which produces a systematic bias: our database is a record of controls that failed. Controls that worked appear only as absences, and absences do not generate incidents to write about.

A separated membership system holding customer data survived an event that took the business estate. Nobody will be commended for it. The person who argued for the separation, possibly years earlier, against colleagues who found it inconvenient, will not be identified.

A hotel membership database is a travel history: who stayed where, when, how often, and frequently with whom. That is a behavioural record with obvious sensitivity, held by an industry not usually thought of as a data business.

Graded medium — the incident and the segmentation outcome are as reported, and the scope of business-system impact has not been quantified.