HAMA-SUSHI
- Aliases / services
- はま寿司 / 株式会社はま寿司 / はまずし / HAMA-SUSHI / HAMA-SUSHI Co., Ltd. / 滨寿司
- Official website
- https://www.hama-sushi.co.jp/
Each response applies only to its stated service scope. “Not listed” does not mean unpatched or unaffected.
Response status by service
Listed services and systems
- Response status
- Not listed
- Response information checked
- 2026-10-25 Rechecked: 2026-10-27
A sushi chain operated by HAMA-SUSHI Co., Ltd. This page covers its Japanese online services, including Hama Navi, reservations and takeaway orders.
The reviewed official materials do not identify a response to the PHP vulnerability. The notice as of 17:00 on October 24 reports restored reservations, while app/web takeaway ordering and web enquiries remain suspended. This describes availability at the notice date and does not verify PHP remediation.
Scope: No response information means that an official response to the PHP vulnerability has not been verified. It does not establish inaction, absence of impact or completed remediation. PHP use itself has not been verified.
This recheck could not revalidate all listed information against current official sources. The previous verification date is retained. Check official notices or support for current availability and required action.
What users should do
Check official notices and in-app guidance for the availability of the features you use and any instructions for users. Ask the operator about the specific service if you need confirmation of PHP remediation.
Official service URL
Source URLs
- HAMA-SUSHI company informationhttps://www.hama-sushi.co.jp/company/Service and operation documentation
- Reservation restoration and maintenance notice, October 24, 17:00https://www.hama-sushi.co.jp/topics/2026/1024000874.htmlService and operation documentation
Related official sources
- HAMA-SUSHI company informationOfficial information directoryConfirms the legal operator and business; it is not evidence of PHP remediation.
- Reservation restoration and maintenance notice, October 24, 17:00Official notice; link to this PHP incident unconfirmedReports availability by service without identifying PHP or the relevant CVE.
Comments