Nhava Sheva (JNPT) container terminal outage (February 2022)
February 2022 · Nhava Sheva (Mumbai), IN. A public, sourced maritime cyber case.
At a glance: who, what, when, where, impact, type
Six facts, taken from the public sources below. Nothing here is inferred.
Who
What
When
Where
Impact
Type
Incident types in this case. Each button opens our threat page: what it is, how it spreads, how to recover.
What happens in this kind of case
When the management information system of one terminal goes down, the port has a choice it made months earlier: a written interim procedure, or a stopped terminal. Containers still arrive by sea and by road; what stops is the paperwork that lets them in and out: the gate pass, the delivery order, the release.
A terminal with an interim manual procedure written and rehearsed before the incident runs slower for a few days and keeps its vessels. A terminal without one sees its ships diverted to the neighbour, and the neighbour keeps them.
February 2022 at Nhava Sheva is the case that showed terminals that the manual procedure is not an IT document: it is the difference between a diverted ship and a stopped terminal.

What to do, and what we recommend
Four measures that would have changed the last week of February 2022 for any container terminal. Each one opens the page where we explain how.
There will always be problems. The question is whether you see them.
The manual procedure kept containers moving. A SIEM is what gives you the days before, so the procedure stays in the drawer. Do you have yours?

Report an incident, in confidence
Ongoing or past, suspected or confirmed: a human reads it, and we call you back within 15 minutes during office hours when it is still running. Logs and screenshots can follow by email.

Sources, as published
We keep only what the sources say. Dates and sites are those of the original articles.

Port Technology International · February 2022
Cyberattack prompts system outage at JNPT container terminal

Splash247 · February 2022
Cyber attack hits state-run terminal at India's top container port
Every public incident on the map
18 public, sourced cyber incidents across global ports and carriers, 2011 to 2026. Open any card for the full story and its public source.
2011-2013 · Antwerp, BE · Criminal intrusion
June 2017 · Copenhagen (HQ) — worldwide, DK · Collateral malware
May 2020 · Bandar Abbas, IR · Nation-state intrusion
Jan + May 2020 · Melbourne, AU · Ransomware
July 2021 · Durban, ZA · Ransomware
Aug-Sep 2021 · Houston, US · Nation-state intrusion
February 2022 · Antwerp / Amsterdam-Rotterdam-Antwerp + German coast, BE · Ransomware
February 2022 · Nhava Sheva (Mumbai), IN · Ransomware
December 2022 · Lisbon, PT · Ransomware
April 2023 · Montreal, CA · Hacktivist DDoS
July 2023 · Nagoya, JP · Ransomware
November 2023 · Melbourne, AU · Criminal intrusion
August 2024 · Seattle, US · Ransomware
November 2026 · Copenhagen (HQ) — isolated subsidiary system, DK · Criminal intrusion
2022-2023 (public figures) · Los Angeles, US · Threat pressure (not a breach)
When one port sees a threat, every member is warned.
The Port Cyber Alliance turns one port’s incident into every member’s early warning. Join the alliance and share the signal.
