Low Keng Huat (Singapore) Limited
Clustered 2 records across 1 jurisdiction: 1 enforcement record and 1 leak-site claim · decided Mar 22, 2024. View entity profile → Other incidents for this victim →
incident inc_0c794f51b91a427a · merged by deterministic · confidence 100%
Litigation Timing
Not recorded for this incident
Discovery variance · Leak precedence · Materiality delta · SEC filing delay · Filing span — no SEC 8-K in this cluster; needs two dated filings.
Member cascade — every enforcement record and leak-site claim in this incident
- OCT 5Leak sitebianlian postfirst record · attacker claim · unverifiedday 0
- MAR 22Singapore PDPCSingapore PDPC noticemost recent · states nationwide total 1,400operator-confirmed+169d
- Watching for additional filings — new sources merge into this incident automatically.
Roll-up facts — reconciled across members
- Breach window
- —
- Discovered
- —
Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.
Evidence ladder — rungs this incident occupies
Attacker assertion only. Establishes: claim date, group, alleged victim.
No press coverage linked yet.
Unlocks: discovery date, data types, affected count, compliance clock.
No SEC filing or victim statement yet.
Merge provenance
- Method
- deterministic
- Confidence
- 1.00 · above the 0.85 auto-merge floor
- Reviewed
- operator-reviewed Sep 6, 2026 · at least one link edge was human-adjudicated
- Audit
- Every link edge records its method, confidence and model + prompt versions (100% is the strongest edge).
Merges are reversible — a wrong link can be detached with its audit trail intact. How merging works.
About this clustering
DisclosureLens links filings into incidents through layered matchers: deterministic rules (same source document, multistate filings of one breach, tight-window same-victim pairs), a weighted-similarity scorer for cross-source candidates, and an operator review queue for everything uncertain. Each link records its own method and confidence — shown per filing in the timeline below. The system defaults to NOT merging when uncertain, because a false merge (collapsing two unrelated breaches) is more harmful than a false split (showing related filings separately); uncertain pairs route to human review instead of auto-merging. This page states only what the linked filings agree on; each filing's own account stays on its own record, linked from the timeline below.
The weekly clock on records like this one
The Disclosure Clock is a weekly briefing on what landed in the disclosure record, and the gap between the criminals' post and the regulator's filing — measured on the whole record, with the method shown.
Weekly. Double opt-in, one-click unsubscribe, and the address goes nowhere else.