Ransomware stops container handling at the Port of Nagoya

Ransomware stops container handling at the Port of Nagoya. The disruption ran from 2023-07-04 (4 July 2023) to 2023-07-06 (6 July 2023), 3 days, affecting Nagoya. Nagoya averaged 7.7 calls per day during the event window against an expected 10.7 (-28.1%).

Key facts

Started
2023-07-04 (4 July 2023)
Ended
2023-07-06 (6 July 2023)
Status
ended
Severity
2 Moderate
Scope
port
Chokepoints
None
Ports
Nagoya
Lanes
None
Countries
Japan
Confidence
high: The timeline, the cause and the restart times come from the incident report published by the Nagoya Harbor Transportation Association, with consistent reporting by two technology outlets.
First reported
2023-07-05 (5 July 2023)
  • Severity basis: Port wide stoppage of 24 hours to 7 days; container work stopped at every Nagoya terminal from 2023-07-04 until 2023-07-06.

What happened

On 2023-07-04 (4 July 2023) the Nagoya Port Unified Terminal System stopped working at about 06:30 local time, and container work stopped at every terminal in the port. The Nagoya Harbor Transportation Association reported that a ransom note printed from a system printer at about 07:30, that the servers were found encrypted that afternoon, and that the Aichi Prefectural Police and the system maintenance company assessed the cause as a ransomware infection. Restoration from backups finished on 2023-07-06 (6 July 2023) and terminals restarted in sequence from 15:00, with the last resuming at 18:15. The association said no ransom amount was stated and that it did not contact the attackers. Press reports attributed the attack to the LockBit group.

Measured effect

Container ship port calls, Nagoya

Baseline (expected)
10.7 calls per day
Observed
7.7 calls per day
Change
-3.0 (-28.1%)
Standardised score
-0.9
Event window
2023-07-04 to 2023-07-06 (3 days)
Baseline window
2023-05-02 to 2023-06-26 (52 valid days)
Method
wfm-effect-1.2
Computed
2026-10-02 (2 October 2026), data revision 1:3d0e37bd5f73
Container ship port calls, NagoyaContainer ship port calls, Nagoya, 2023-04-25 (25 April 2023) to 2023-08-17 (17 August 2023): values ranged from 0 calls per day on 2023-08-13 to 23 calls per day on 2023-08-16, with a mean of 10.6 calls per day. The latest value, for 2023-08-17, was 18 calls per day. The shaded band marks the event window, 2023-07-04 to 2023-07-06.05101520252023-04-252023-06-212023-08-17
Container ship port calls, Nagoya, 2023-04-25 (25 April 2023) to 2023-08-17 (17 August 2023): values ranged from 0 calls per day on 2023-08-13 to 23 calls per day on 2023-08-16, with a mean of 10.6 calls per day. The latest value, for 2023-08-17, was 18 calls per day. The shaded band marks the event window, 2023-07-04 to 2023-07-06.

Source: IMF PortWatch (portwatch.imf.org), International Monetary Fund, using UN Global Platform AIS data. Statistics derived by World Freight Monitor. Terms. Retrieved 2026-11-10 (10 November 2026).

Container ship port calls, Nagoya (calls per day).
Datecalls per day
2023-04-2511
2023-04-268
2023-04-2716
2023-04-2814
2023-04-2912
2023-04-3010
2023-05-018
2023-05-028
2023-05-0312
2023-05-049
2023-05-059
2023-05-0611
2023-05-079
2023-05-0811
2023-05-098
2023-05-107
2023-05-1113
2023-05-1211
2023-05-1311
2023-05-1412
2023-05-157
2023-05-166
2023-05-1711
2023-05-1819
2023-05-1915
2023-05-208
2023-05-217
2023-05-2212
2023-05-239
2023-05-249
2023-05-2514
2023-05-2614
2023-05-2713
2023-05-289
2023-05-2911
2023-05-309
2023-05-3110
2023-06-0111
2023-06-028
2023-06-038
2023-06-0420
2023-06-059
2023-06-0610
2023-06-079
2023-06-0812
2023-06-0918
2023-06-1012
2023-06-1112
2023-06-124
2023-06-1310
2023-06-1410
2023-06-1512
2023-06-1619
2023-06-1713
2023-06-187
2023-06-197
2023-06-207
2023-06-2113
2023-06-2216
2023-06-2314
2023-06-2412
2023-06-259
2023-06-2610
2023-06-276
2023-06-289
2023-06-2914
2023-06-3016
2023-07-0113
2023-07-029
2023-07-0310
2023-07-045
2023-07-053
2023-07-0615
2023-07-0719
2023-07-0815
2023-07-099
2023-07-106
2023-07-119
2023-07-1210
2023-07-1316
2023-07-1416
2023-07-1514
2023-07-167
2023-07-1711
2023-07-186
2023-07-1910
2023-07-2020
2023-07-2114
2023-07-2210
2023-07-239
2023-07-2411
2023-07-257
2023-07-2611
2023-07-2713
2023-07-2813
2023-07-2915
2023-07-307
2023-07-3110
2023-08-015
2023-08-0214
2023-08-0310
2023-08-047
2023-08-0515
2023-08-066
2023-08-079
2023-08-084
2023-08-099
2023-08-105
2023-08-1110
2023-08-1211
2023-08-130
2023-08-140
2023-08-153
2023-08-1623
2023-08-1718

This is a measured change in public data during the event window, compared with a baseline before it. It shows timing, not cause. We describe an event as causing a change only when an official source says so.

Previous computations (1)
  • 2026-09-16, wfm-effect-1.0, revision 1:86c331405645: observed 7.7 against baseline 10.3 calls per day

Replay

Replay: Container ship port calls, NagoyaContainer ship port calls, Nagoya, 2023-05-05 (5 May 2023) to 2023-08-03 (3 August 2023): values ranged from 3 calls per day on 2023-07-05 to 20 calls per day on 2023-06-04. The shaded band marks the event window, 2023-07-04 to 2023-07-06.051015202023-05-052023-08-03
Container ship port calls, Nagoya, 2023-05-05 (5 May 2023) to 2023-08-03 (3 August 2023): values ranged from 3 calls per day on 2023-07-05 to 20 calls per day on 2023-06-04. The shaded band marks the event window, 2023-07-04 to 2023-07-06.

Source: IMF PortWatch (portwatch.imf.org), International Monetary Fund, using UN Global Platform AIS data. Statistics derived by World Freight Monitor. Terms. Retrieved 2026-11-10 (10 November 2026).

Container ship port calls, Nagoya (calls per day), daily values shown in the replay.
Datecalls per day
2023-05-059
2023-05-0611
2023-05-079
2023-05-0811
2023-05-098
2023-05-107
2023-05-1113
2023-05-1211
2023-05-1311
2023-05-1412
2023-05-157
2023-05-166
2023-05-1711
2023-05-1819
2023-05-1915
2023-05-208
2023-05-217
2023-05-2212
2023-05-239
2023-05-249
2023-05-2514
2023-05-2614
2023-05-2713
2023-05-289
2023-05-2911
2023-05-309
2023-05-3110
2023-06-0111
2023-06-028
2023-06-038
2023-06-0420
2023-06-059
2023-06-0610
2023-06-079
2023-06-0812
2023-06-0918
2023-06-1012
2023-06-1112
2023-06-124
2023-06-1310
2023-06-1410
2023-06-1512
2023-06-1619
2023-06-1713
2023-06-187
2023-06-197
2023-06-207
2023-06-2113
2023-06-2216
2023-06-2314
2023-06-2412
2023-06-259
2023-06-2610
2023-06-276
2023-06-289
2023-06-2914
2023-06-3016
2023-07-0113
2023-07-029
2023-07-0310
2023-07-045
2023-07-053
2023-07-0615
2023-07-0719
2023-07-0815
2023-07-099
2023-07-106
2023-07-119
2023-07-1210
2023-07-1316
2023-07-1416
2023-07-1514
2023-07-167
2023-07-1711
2023-07-186
2023-07-1910
2023-07-2020
2023-07-2114
2023-07-2210
2023-07-239
2023-07-2411
2023-07-257
2023-07-2611
2023-07-2713
2023-07-2813
2023-07-2915
2023-07-307
2023-07-3110
2023-08-015
2023-08-0214
2023-08-0310

This is a measured change in public data during the event window, compared with a baseline before it. It shows timing, not cause. We describe an event as causing a change only when an official source says so.

Timeline

  1. The terminal system stops at about 06:30. A ransom note prints at about 07:30, servers cannot restart, and by about 14:00 the physical and virtual servers are found encrypted. The police cyber attack unit is notified. [s1]
  2. The association states publicly that the cause is a ransomware infection and sets a target of restarting terminal work on the morning of 2023-07-06. A virus is then found in backup data, delaying restoration. [s1] [s2]
  3. Backup restoration finishes at about 07:15, a network fault is cleared at about 14:15, and terminals restart from 15:00, with the last terminals resuming at 18:15. [s1] [s3]

Cause

The Nagoya Harbor Transportation Association reported that the Aichi Prefectural Police and the system maintenance company assessed the cause as a ransomware infection, entering through a vulnerability in a remote access device. Press reports attributed the attack to the LockBit group. Attributed by: Nagoya Harbor Transportation Association. [s1] [s2] [s3]

Resolution

2023-07-06 (6 July 2023): Systems were restored from backups and terminal work resumed in sequence on 2023-07-06, with the final terminals restarting at 18:15. The association said it found no evidence of data leaving the organisation. [s1]

Corrections

No corrections to this record as of 2026-09-16 (16 September 2026).

Sources

  1. [s1] Nagoya Harbor Transportation Association, NUTS システム障害の経緯報告, published 2023-07-26 (26 July 2023), accessed 2026-09-15. Archived copy. (official)
  2. [s2] The Record, Major Japanese port suspends operation following ransomware attack, published 2023-07-05 (5 July 2023), accessed 2026-09-15. Archived copy. (press)
  3. [s3] The Register, LockBit ransomware infection hits Japan's top cargo port, published 2023-07-06 (6 July 2023), accessed 2026-09-15. Archived copy. (press)

Cite this record

The address of this record is permanent and a correction is always logged on this page, so a citation names the version you read. Add the date you accessed it.

Plain text

World Freight Monitor. "Ransomware stops container handling at the Port of Nagoya." Last updated 2026-09-16 (16 September 2026). https://worldfreightmonitor.com/events/2023/ransomware-attack-nagoya-port-2023/

APA

World Freight Monitor. (2026). Ransomware stops container handling at the Port of Nagoya. World Freight Monitor. https://worldfreightmonitor.com/events/2023/ransomware-attack-nagoya-port-2023/

BibTeX

@misc{wfm_ransomware_attack_nagoya_port_2023,
  author = {{World Freight Monitor}},
  title = {Ransomware stops container handling at the Port of Nagoya},
  year = {2026},
  note = {Last updated 2026-09-16},
  url = {https://worldfreightmonitor.com/events/2023/ransomware-attack-nagoya-port-2023/}
}