[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f7NPMUxnKnjQwrwcRBk_nbt8cdLGctB4TpufG5p8cFf0":3},{"success":4,"breach":5},true,{"_id":6,"name":7,"title":8,"slug":9,"domain":10,"company":11,"breachDate":15,"addedDate":16,"modifiedDate":17,"pwnCount":18,"totalRecords":19,"dataClasses":20,"description":35,"source":36,"isVerified":4,"isSpamList":37,"isSensitive":4,"severity":38,"processingStatus":39,"logoUrl":40,"contentUpdatedAt":16,"hasEnglishDescription":4},"6a670ef0099ab9c0b4c97275","ResourceCenterDallas2026","Resource Center Dallas 2026 Data Breach","resource-center-dallas-2026","myresourcecenter.org",{"name":12,"sector":13,"country":14,"website":10},"Resource Center of Dallas","Nonprofit","United States","2026-02-04T00:00:00.000Z","2026-07-27T07:55:28.757Z","2026-07-27T09:30:00.000Z",0,null,[21,22,23,24,25,26,27,28,29,30,31,32,33,34],"Personal information","Protected health information","Names","Addresses","Dates of birth","Certain Social Security numbers","Driver's license numbers","Government-issued identification numbers","State identification card numbers","Financial account information","Medical records","Medical information","Health insurance information","Other identification information","\u003Cp>\u003Cstrong>The Resource Center Dallas 2026 data breach\u003C\u002Fstrong> involved unauthorized access to and\u002For acquisition of certain files in the network of a Dallas nonprofit healthcare and community-services organization. According to the organization's official notice, activity occurred from approximately February 4 through February 12, 2026; the network was contained, law enforcement was notified, and outside cybersecurity specialists were engaged.\u003C\u002Fp>\n\u003Cp>After an extensive forensic investigation and document review, Resource Center identified people whose personal or protected health information may have been involved around July 2. State notices report 9,048 Texas and 13 Massachusetts residents, but no deduplicated nationwide total has been published. LeakData does not invent a count: pwnCount and totalRecords are zero, and importedRecordCount is zero.\u003C\u002Fp>\n\u003Ch2>How Was the Resource Center Dallas Breach Confirmed?\u003C\u002Fh2>\n\u003Cp>The primary source is the “Notice Regarding Data Security Incident” published on Resource Center of Dallas's own website. It directly states that an unauthorized party accessed and\u002For may have acquired files from portions of the network, the activity window, the investigation, the main data classes identified, and security measures adopted by the organization afterward.\u003C\u002Fp>\n\u003Cp>A Massachusetts consumer-notification file confirms the July 15, 2026 sample letter, assistance line, and use of person-specific variable fields in individual letters. A Texas regulatory record supplies the state subset, while Claim Depot connects those official sources and summarizes available state counts and detailed fields. The sources align on the organization, dates, and nature of the event.\u003C\u002Fp>\n\u003Ch2>What Happened From February 4 Through February 12, 2026?\u003C\u002Fh2>\n\u003Cp>Resource Center detected that certain network systems had been affected by a data-security incident. Its official notice says an unauthorized party accessed and\u002For acquired certain files from portions of the network from about February 4 through February 12. The public text does not disclose the initial entry method, malware used, or identity of the actor.\u003C\u002Fp>\n\u003Cp>After detecting the event, the organization immediately began an investigation, contained the network, and notified law enforcement. Specialists examined the extent of the unauthorized activity and whether the files held PII or PHI. The forensic and document review took several months; around July 2, Resource Center identified people whose information may have been involved and began preparing notices.\u003C\u002Fp>\n\u003Ch2>What Identity and Financial Information May Have Been Affected?\u003C\u002Fh2>\n\u003Cp>The information varied by person but could include names, addresses, dates of birth, certain Social Security numbers, driver's-license numbers, government-issued identification numbers, state-identification-card numbers, financial-account information, and other identification information. Each recipient's sample letter was designed to identify the variable fields associated with that person's file.\u003C\u002Fp>\n\u003Cp>A combination of name, birth date, SSN, and government identification creates substantial risk of new-account fraud, tax-identity misuse, and targeted phishing. Financial-account information may also support fraudulent payments or account-takeover attempts. Because the public notice does not confirm a bank, access code, payment card, or password, LeakData does not add those subfields.\u003C\u002Fp>\n\u003Ch2>What Medical and Insurance Information Was In Scope?\u003C\u002Fh2>\n\u003Cp>Resource Center explicitly lists medical information and health-insurance information within the possible scope. The state record and source-linked summary also identify medical records among fields that may have been affected. Such data can connect a person to particular care relationships and may be abused for medical-identity misuse or convincing social-engineering attempts.\u003C\u002Fp>\n\u003Cp>The public notice does not separately publish clinical subfields such as diagnosis, treatment, prescription, medical-record number, insurance-policy number, or service date. General examples in the protection guidance should not be treated as confirmed incident fields. LeakData retains medical and insurance categories at the specificity supported by sources without inferring undisclosed sensitive details.\u003C\u002Fp>\n\u003Ch2>How Many People Were Affected and Was the Data Misused?\u003C\u002Fh2>\n\u003Cp>Available state disclosures report at least 9,048 Texas and 13 Massachusetts residents. These are distinct state subsets, not a deduplicated nationwide affected-person count. LeakData does not present 9,061 as the national total or estimate the unknown remainder; pwnCount and totalRecords therefore remain zero, with the state subsets documented in the source note.\u003C\u002Fp>\n\u003Cp>The Massachusetts sample letter says that, as of its date, Resource Center had no evidence that the information was used to commit financial fraud or identity theft. That statement does not guarantee that future misuse will not occur. Because unauthorized file access and\u002For acquisition is confirmed in the official notice, recipients should continue monitoring financial and healthcare accounts.\u003C\u002Fp>\n\u003Ch2>How Did Resource Center Respond and What Should People Do?\u003C\u002Fh2>\n\u003Cp>The organization contained the network, notified law enforcement, conducted a forensic investigation and document review with outside specialists, reviewed security practices, and implemented additional measures. Notices dated July 15 were sent to affected people. A confidential line at 1-888-201-1486 was established for 90 days from the letter, from 9:00 a.m. to 9:00 p.m. Eastern on weekdays.\u003C\u002Fp>\n\u003Cp>Recipients should review credit reports, financial-account statements, and insurance explanation-of-benefits statements for unfamiliar accounts, transactions, or healthcare services. If an SSN or government ID was involved, a credit freeze, fraud alert, and IRS Identity Protection PIN may be appropriate. Personal information or verification codes should not be shared in unexpected messages. LeakData does not host or distribute incident files or make person records searchable.\u003C\u002Fp>","Official Resource Center of Dallas notice confirming unauthorized access to and\u002For acquisition of network files containing PII and PHI",false,"Low","completed","\u002Fuploads\u002Flogo\u002Fmyresourcecenter_org.png"]