
On 12 October 2026 an extortion group calling itself n0n listed 38 maritime organisations from 18 countries on its leak site, in a single batch: container lines, terminal operators, port IT providers, ship managers, agents and logistics companies, each with its own deadline and its own ransom demand. Nobody on the list had confirmed a breach when the trade press reported it two days later. A week after that, a maritime cybersecurity firm published an interim assessment with a different reading: the files published as samples probably come from one place, a support and project archive linked to a software provider that serves the sector, split by customer and presented as 38 separate victims.
We are not going to comment on the companies named, nor on the provider: the data has not been authenticated and every statement in the analyses is marked as alleged. What is worth your time is the shape of the case, because it will come back: one leak at a supplier, resold as a breach at each of its customers.
What is actually known
Sources: The Loadstar (14 October 2026), Cyprus Shipping News, analysis by Cydome (20 October 2026). Everything above should be read as alleged until an organisation confirms it.
What
Who was listed
The group
The assessment
Impact
Why « it is not you, it is your supplier » is the pattern that matters
Every port runs software it did not write, supported by people it does not employ, through accounts it does not manage. The provider's support archive holds, by nature, what its customers sent it over the years: configuration exports, screenshots with real data, test accounts, the occasional password in an e-mail. That archive is a single target, and it is outside your perimeter.
What makes October 2026 a new case is the business model, not the technique. The group did not need to breach a port. It needed one set of stolen credentials at one provider, then a spreadsheet to split the archive by customer name and send 38 invoices. For the port that finds its name on the list, the questions are the same as after a real intrusion, except that the answers are at the supplier, which is handling 37 other customers at the same time. « Old in part, authenticity not established » is not reassurance. It is the exact description of a supplier archive: everything you ever sent, kept for longer than you assumed.
What a port team can do this week
None of this requires a budget line: an afternoon, your supplier list, and « unknown » written where it applies.
List what your suppliers hold
Rotate what a support archive could contain
Ask for the provider's own incident clause
Watch for infostealer traces on your side
If you have the same cases
Most ports do, and that is fine: everyone runs software written by someone else. If you want a quick, private way to see where you stand, we built two self-assessments that take about two minutes and stay in your browser until you decide otherwise: one for engineers, one for the people who lead the team. If something in your result worries you, talk to us in confidence. And when one port sees a threat, every member of the Alliance is told: that is the whole point.
Keep reading
Supply chain: when the attack comes through
Credential theft and MFA bypass
Every public port cyber incident, on one
Port engineer cyber self-assessment: 2-minute test
Team cyber assessment for port and terminal
DMS Group: the logistics chain, from the
Want a second pair of eyes on your site?
Every member gets cyber advice and two site visits a year. Start with a two-minute self-assessment.



