← Breach analysis by the Dual Vulnerabilities framework

Soken Chemical ransomware (Unattributed, 2024)

2024 · Japan · C - Manufacturing · Ransomware attack with initially undetected data exfiltration

Analysed 2026-11-06 by Hermes

Open this case in the tool →

What happened

Ransomware attack with initially undetected data exfiltration

Dual vulnerability type

Expertise to Execution

Evidence coverage: 1/6 stages, weight 6/60

Decisive stage: egress (clearest evidence) · Alternative: Strategy to Execution

Why this classification

(1) Soken Chemical & Engineering is a TSE-listed chemical manufacturer recorded as critical infrastructure (critical manufacturing) in the source dataset, transacting with thousands of business partners; the standing expectation for such a company is that bulk outbound data transfer is monitored and that the scope of an intrusion can be reconstructed from its own instrumentation. (2) Operationally, the encryption was found on 09-01-2024 and contained by the company's own shutdowns, and the disclosure and notification conduct was prompt; but the data leaving the network was not: the company's own investigation confirmed only five data items by 05-03-2024, and it learned of a far larger leak only on 10-05-2024 when an external investigation firm informed it - the June announcement put the loss at potentially about 7,460 companies' transaction data and about 19,408 personal records, still phrased as possible because the company could not positively establish what had been taken. (3) The classification rests on the egress stage: egress monitoring and forensic scoping are remedies that exist and are known to technical specialists (material origin), yet they were never realised in operations - neither the exfiltration nor its scope could be detected or reconstructed in-house (execution break) - which is an Expertise to Execution gap, not mere weak security; the entry vector was investigated but never disclosed and is not load-bearing, and the same-day headquarters, next-day disclosure and individual notifications show no Strategy to Leadership pattern at the response stage. RM35 (Expertise to Execution lens): the firm's inability to detect or interrupt the outbound transfer that an external specialist firm later identified shows the known egress-monitoring control was not implemented or tuned in this environment, amplifying the incident from a contained encryption event into a mass data loss (causal role: Amplifying). RM33 (Expertise to Execution lens): the company could not scope or reconstruct the exfiltration from its own records - from 'no leakage confirmed' in January to 'possible leakage' of 19,408 records in June - leaving the true impact obscured even at final disclosure (causal role: Obscuring).

Evidence by stage

Risk markers

Sources

Notes

EuRepoC row; description matches the stated victim. The dataset's NetSecurity source URL (https://scan.netsecurity.ne.jp/article/2024-01-16/50451.html) returned 404 when opened on 06-11-26 and was replaced by the company's own disclosure PDFs and Security NEXT reporting. Actor: EuRepoC records the incident as not attributed; ransomware leak-site trackers index a LockBit 3.0 claim of listing soken-ce.co.jp, but that is attacker-side material outside the research boundaries and no established press attribution was found, so the actor stays Unattributed. The company's June 2024 disclosure PDF could not be located on its site (guessed URLs 404, IR page timed out on repeat access); the June figures rest on Security NEXT (secondary). The row's 'no data deemed stolen' reflects the position at the January follow-up; leakage was confirmed on 05-03-2024 and massively revised on 19-06-2024. Legal response per EuRepoC: Tokyo Metropolitan Police Department investigation from 09-01-2024.