Clustered 3 filings across 3 jurisdictions · filing window Jul 11, 2025 → Mar 3, 2026. View entity profile → Other incidents for this victim →
incident inc_d978b7b2c43240e3 · merge_method human · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
Gap between first leak claim and first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Materiality delta · SEC filing delay — no SEC 8-K in this cluster.
TX WA
Leak Site · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jun 6, 2025
Reported by WASHINGTON AG filing
New American Funding, LLC, a finance sector entity reported a ransomware incident to the Washington Attorney General. The organization became aware of the incident on 2025-06-06 and filed notice on 2025-07-11. 1,991 Washington residents were affected. 35 days elapsed between awareness and notification.
Affected (this filing): 1,991
New American Funding is a family-owned mortgage lender with a nationwide presence. Since its founding in 2003, the firm has been dedicated to helping Americans finance their homes. They offer a variety of loans including FHA, VA, HARP, and Conventional loans. The company is known for its efficient processes, exceptional service, innovative use of technology, and strong commitment to providing equal housing opportunities.
Jan 28, 2026
Reported by TEXAS AG filing
New American Funding, LLC based in Tustin, California, a financial services entity reported a data breach to the Texas Attorney General. The breach was discovered on 2026-01-28 and reported on 2026-03-03. 1,942 Texas residents were affected. 0 individuals affected in total. Types of information involved: Name of individual;Address;Social Security Number Information;Date of Birth. Consumers were notified via U.S. Mail.
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): 1,942