myerspower.com labriegroup.com mielectric.com aeti.com these four companies were in the same domain! all their networks were encrypted root:gear$N0stra* aeti\admin:_NYt7~St]ye' root:$a53ty! myersamerica\tadmin:$a53ty! myerspower:Xiw6zvbp37gx...
Clustered 2 filings across 2 jurisdictions · filing window Feb 14, 2023 → Mar 16, 2023. View entity profile → Other incidents for this victim →
incident inc_a7df77f36c7f4f90 · 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.
Identity (basic)
CA
Leak Site · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jan 21, 2023
When the intrusion reportedly occurred, per the linked filings
Jan 21, 2023
Reported by CALIFORNIA AG filing
myerspower.com labriegroup.com mielectric.com aeti.com these four companies were in the same domain! all their networks were encrypted root:gear$N0stra* aeti\admin:_NYt7~St]ye' root:$a53ty! myersamerica\tadmin:$a53ty! myerspower:Xiw6zvbp37gx...
Myers Power Products, Inc. discovered unusual network activity on January 21, 2023, which disrupted access to certain systems. An investigation revealed that personal information, including names and other variable data, may have been accessed or acquired without authorization. The company secured its network, engaged independent cybersecurity experts, reported the incident to law enforcement, and implemented additional security measures. Complimentary identity protection services were offered to affected individuals.
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.