Elemetal is one of the largest precious metals refiner. They are laundering money for drug cartel and can't find a small amount to prevent data leak. Cost of their privacy is $160.000. 600GB of...
Clustered 2 filings across 2 jurisdictions · filing window Sep 18, 2023 → Mar 1, 2024. View entity profile → Other incidents for this victim →
incident inc_f471f93fd72a4b57 · merge_method human · confidence 100%
Discovered → first regulatory filing
Gap between first leak claim and first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Materiality delta · SEC filing delay — no SEC 8-K in this cluster; needs two dated filings.
Financial account · Financial credentials
ME
Leak Site · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Aug 22, 2023
When the intrusion reportedly occurred, per the linked filings
Elemetal is one of the largest precious metals refiner. They are laundering money for drug cartel and can't find a small amount to prevent data leak. Cost of their privacy is $160.000. 600GB of...
Feb 9, 2024
Reported by MAINE AG filing
Elemetal, LLC reported a data breach affecting 13 Maine residents. The breach, which occurred on August 22, 2023, and was discovered on February 9, 2024, was the result of an external system breach (hacking). The compromised information includes names in combination with financial account numbers or credit/debit card numbers and their security codes. Elemetal began notifying affected individuals on March 1, 2024, and offered 24 months of credit monitoring and identity restoration services through IDX.
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. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.
Affected (this filing): 13