Port of Tanjung Pelepas
bd_e14e35d7c17df4a1 · schema v1 · pii pii-v2
Press / market disclosure — not a breach-notification filing
A media or market posting that confirms an incident but carries no breach-notification fields, so compliance clocks aren't assessable. The summary below is extracted from the coverage — verify against the source.
Cyber attack disrupts operations at Malaysia’s Port of Tanjung Pelepas. Port of Tanjung Pelepas: Le Port de Tanjung Pelepas has confirmed that it suffered a cybersecurity incident that affected its operational systems and temporarily interrupted container terminal operations. A gradual restart began on September 10. Linked ransomware group: direwolf.
P pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Sep 9, 2026
Press report
—
No filing yet · watching
Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.
Attack → press
—
Compliance clock
Not assessable
Evidence ladder
Attacker assertion only. Establishes: claim date, group, alleged victim.
Unlocks: incident narrative, operational impact. Still no compliance clock.
Unlocks: discovery date, data types, affected count, compliance clock.
Unlocks: materiality, stated response, full audit trail. Ceiling removed.
If an SEC 8-K, state-AG notice or victim statement lands, DisclosureLens merges it into an incident and links it here.
Source ceiling
- incident type + narrative only (may be machine-translated)
- discovery date
- materiality
- affected count
- data types
- compliance clock
The ✕ fields stay blank until a regulatory filing or victim disclosure lands.
direwolf
According to ransomware.live, Dire Wolf is a sophisticated human-operated ransomware group first documented in May 2025, written in Golang using Curve25519/ChaCha20 encryption, targeting manufacturing and technology sectors across 13+ countries with ransoms up to $500,000, operated by a tight core team rather than a broad affiliate program.