Live Blog: Cyber Reflections on the Iran-Israel-U.S. War Read the Analysis
Alleged

CULines Data Breach

Ransomware claim involving CULines

Published: Oct 12, 2026 N0n

Threat Level

High

Confidence: High

Quick Summary

Company
CULines
Industry
Manufacturing
Threat Actor
N0n
Date of Incident
Oct 12, 2026

Executive Summary

CULines, a container shipping operator based in China, was listed as a victim by the N0n ransomware group on October 12, 2026. The group’s claim highlighted the exposure of twenty-five employee credentials, which was the highest count among the batch of maritime victims listed concurrently. This incident, involving a significant player in global logistics, underscores the growing threat to the transportation sector. The identified credentials suggest a broad compromise across various corporate identity systems and operational platforms, indicating a potential for extensive disruption to CULines’ services, including cargo booking, documentation, and customer-facing interfaces. N0n has claimed responsibility for 72 victims in the 60 days preceding this listing, demonstrating significant operational tempo. The group’s primary focus has been on the Transportation, Technology, and Healthcare sectors, with a notable concentration of victims in the US, South Korea, and Brazil. Within the same batch as CULines, other maritime sector victims included Ocean Network Express (Singapore), T.S. Lines (Taiwan), and ZPMC (China). CULines’ targeting aligns with N0n’s established industry preferences, suggesting the group may have identified vulnerabilities within the broader maritime and logistics infrastructure.

Technical Analysis

The stealer-log analysis associated with N0n’s claim against CULines revealed the exposure of 25 credentials. These credentials span across multiple corporate identity systems and operational platforms, suggesting that the compromise affected more than a single endpoint. This broad scope of exposed credentials indicates that the threat actor may have achieved persistent access to CULines’ network over an extended period, rather than a brief, single-session intrusion. The potential impact of this credential exposure could significantly affect CULines’ critical operations, including cargo booking, documentation processes, and customer interaction systems. The scale and nature of the credential exposure observed are consistent with the methods employed by ransomware groups to gain a foothold and establish persistent access within targeted organizations. The identified credentials could potentially grant attackers access to sensitive systems, facilitating further lateral movement and the deployment of ransomware. Given the nature of CULines’ business as a container carrier, the compromised credentials may provide access to a wide range of operational technologies and customer data, posing a substantial risk to the company’s integrity and its clients. The exposure of 25 credentials across various identity and operational systems warrants immediate and comprehensive action. This includes full credential rotation for all accounts associated with the culines[.]com domain. Organizations should prioritize the isolation and investigation of potentially compromised endpoints. Furthermore, implementing phishing-resistant multi-factor authentication (MFA) on all remote access solutions and single sign-on (SSO) systems is crucial. It should be assumed that persistent network access may have been established during the period when these credentials were collected.

Disclaimer

This report is intended for threat intelligence and security awareness purposes. SOCRadar does not host, redistribute or buy stolen data. All breach information reported here is collected from publicly accessible threat actor and ransomware portals. This content is intended to equip CTI teams with context around recent attacks. While we strive for accuracy, listings on ransomware leak and extortion sites cannot always be independently verified and may not reflect confirmed breaches. If you believe any data in this report is incorrect, please contact us.