[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f3ga5u8jmhrgok":3},{"success":4,"breach":5},true,{"_id":6,"name":7,"title":8,"slug":9,"domain":10,"breachDate":11,"addedDate":12,"publishedAt":13,"modifiedDate":12,"contentUpdatedAt":14,"source":15,"sourceUrl":16,"sourceUrls":17,"pwnCount":18,"affectedCount":18,"affectedCountStatus":19,"affectedCountLowerBound":13,"affectedCountUnit":20,"hasEnglishDescription":4,"contentLocale":21,"availableLocales":22,"translations":24,"severity":27,"dataClasses":28,"description":45,"seoTitle":46,"seoDescription":47,"logoUrl":48,"isVerified":4,"isSensitive":4,"isSpamList":49,"isMalware":49,"company":50},"6a4cf553e738b3d56ace5f47","ERMI LLC 2025","ERMI LLC 2025 Data Breach","ermi-llc-2025","ermi-motion.com","2025-02-15T00:00:00.000Z","2026-07-07T12:47:15.711Z",null,"2026-07-18T23:21:48.154Z","Manual reviewed breach record","",[],74074,"known","unknown","en",[21,23],"tr",{"en":25,"tr":26},{"slug":9},{"slug":9},"Medium",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44],"Names","Social security numbers","Driver's licenses","Government issued IDs","Passport numbers","Usernames","Passwords","Email addresses","Security questions and answers","Dates of birth","Deceased date","Taxation records","Bank account numbers","Credit cards","Personal health data","Health insurance information","\u003Cp>ERMI LLC 2025 data breach was an incident that occurred due to unauthorized access to employee email accounts at a healthcare company associated with medical movement enhancement devices and patient support services. According to the company's announcement, some files may have been accessed or taken by an unauthorized person between February 15, 2025 and August 14, 2025. After a lengthy investigation, it was determined that the affected files around April 17, 2026 may contain personal and health-related information about some individuals. Notifications were sent to affected individuals with mailing addresses available around May 26, 2026.\u003C\u002Fp>\u003Cp>This incident should not be treated as an ordinary email account incident; because the data types listed include identity, financial, access information and health data together. The fields disclosed include high-sensitivity categories such as social security number, driver's license number, veteran ID, passport number, username and password, password and security question with email address, date of birth, date of death, taxpayer or employer identification number, financial account information, payment card information, medical information and health insurance information. Some trusted notification records show that names are also in scope.\u003C\u002Fp>\u003Ch2>Leaked Data Types and Risks\u003C\u002Fh2>\u003Cp>The data classes used for this record are names, social security numbers, driver's licenses, government-issued IDs, passport numbers, usernames, passwords, email addresses, security questions and answers, birth dates, date of death, tax records, bank account numbers, credit cards, personal health data and health insurance information. Veteran ID is considered under government-issued ID in the canonical classification. Financial account information is represented by bank account numbers, and payment card information is represented by credit cards. Since data fields vary from person to person, it should not be assumed that every individual has all of these fields.\u003C\u002Fp>\u003Cp>When identity fields and financial fields exist together, attackers can attempt to open a new account, apply for a loan, fake a payment order, take over a bank account, and bypass identity verification questions. The combination of username, password, email address, and security question creates additional risk for people who use the same information on other accounts. Health and health insurance information is also susceptible to medical identity theft, fraudulent healthcare claims, inaccurate billing, and personalized scam messages. Fields such as date of death and tax ID can be misused in the context of inheritance, tax or employer registration.\u003C\u002Fp>\u003Ch2>Verified Scope and Limits\u003C\u002Fh2>\u003Cp>The main timeline of the event is supported by public statements. The unauthorized access or file retrieval period is announced as February 15, 2025 and August 14, 2025. The determination that personal information may be contained in the affected files occurred around April 17, 2026, and notifications were announced to be sent around May 26, 2026. The health breach notification shows the number of people affected as 74,074. This number was kept as the main number of affected persons in the register. The appearance of narrower local numbers in some state declarations should be considered as a regional breakdown other than the total number.\u003C\u002Fp>\u003Cp>Field coverage in this record is purposely limited to categories that appear expressly in official and reliable declarations. Because the official text indicates that data types vary from person to person, it should not be taken for granted that every user has a social security number, financial account information, payment card, health information, or access information. However, since the files in e-mail accounts can contain documents from many different systems, the involvement of identity, finance and health areas together in the same event increases the risk level. The record represents the true scope of the event without exaggerating it.\u003C\u002Fp>\u003Ch2>User Groups at Risk\u003C\u002Fh2>\u003Cp>The highest risk group is people who have a connection with ERMI through a patient, service recipient, employee, former employee, provider, payment relationship, insurance relationship or support process and are within the scope of notification. Files maintained in the context of medical device and movement improvement services may include patient information, insurance records, payment relationships, and communication records. Employee email accounts being affected means that different types of documents and correspondence may be at risk, rather than just uniform records from a single database. For this reason, the data fields written in the individual notification letter should be considered priority.\u003C\u002Fp>\u003Cp>People with a social security number, passport number, driver's license or veteran ID are at high risk of identity theft. People who have a username, password or security question may face the risk of account takeover due to password reuse if they use the same information in other accounts. People who have financial account or payment card information should closely monitor their bank movements and payment card transactions. People with health insurance or medical information should regularly check their insurance statements for any service, request, provider or payment record they do not recognize.\u003C\u002Fp>\u003Ch2>Urgent Measures to be Taken\u003C\u002Fh2>\u003Cp>Notified individuals should first check the data types listed for them in the letter and should not miss the registration deadline if there is a free credit monitoring service offered. Individuals whose social security number, driver's license, passport or tax ID may have been affected should consider credit freeze and fraud alert options. If an unrecognized application, new account, address change or collection record appears in the credit reports, a written objection must be made to the relevant institutions. Individuals with financial account or payment card information should contact their bank and card provider to check transactions.\u003C\u002Fp>\u003Cp>Persons whose access information may have been affected should change their passwords on all accounts where they use the same or similar password. Question sets should also be changed in accounts where the security question and answer may have been exposed. Multi-step verification should be enabled, especially email, bank, insurance, health portals and payment accounts should be prioritized. People with health insurance should check disclosure forms, billing records, and claims for health care they do not recognize. Information should not be entered directly in linked messages with the name of a company, bank or healthcare institution; official communication channels should be verified separately.\u003C\u002Fp>\u003Ch2>Long-Term Security Strategies\u003C\u002Fh2>\u003Cp>The risk in this case is long-term; because social security number, date of birth, passport, driver's license, tax ID and health information are fields that cannot be changed easily. Affected individuals should be careful not only in the initial reporting period, but also in subsequent tax periods, loan applications, health insurance transactions and payment transactions. A credit freeze can provide strong long-term protection for people who do not have active credit applications. People with health data should continue to check their insurance statements and medical billing records even after months.\u003C\u002Fp>\u003Cp>Access authorizations, retention periods and sensitive document sharing of files kept in corporate e-mail accounts should be regularly audited. Email accounts should be protected with multi-step verification, unusual session alerts, file download monitoring, password reuse controls, and rapid account closure processes. Leaving attachments containing health and financial data in mailboxes for a long time magnifies the post-event impact. Therefore, document archiving, encrypted file sharing, data inventory and incident response exercises reduce the impact of similar events.\u003C\u002Fp>\u003Ch2>Record Control and User Action\u003C\u002Fh2>\u003Cp>Users who see the ERMI LLC 2025 record on Leakdata should consider the result as a risk of high-sensitive health, identity, financial and account access information. The main number in the register is 74,074 people; however, data types may vary from person to person. Looking at which fields are included in the notification letter provides the most accurate prioritization. Individuals who may have a social security number, passport, driver's license, financial account, payment card, health insurance or password information should not assume lower risk.\u003C\u002Fp>\u003Cp>Users should jointly check credit reports, debit and card transactions, email logins, accounts with password reuse, health insurance disclosures, and medical billing records. If an unrecognized transaction, new account, password reset message, insurance claim or healthcare record is seen, the relevant institutions should be contacted quickly and the applications should be kept in writing. The date distinction in this record is important: the unauthorized access period is between February 15, 2025 and August 14, 2025, the detection of personal information is between April 17, 2026, and the notification period is between May 26, 2026.\u003C\u002Fp>","ERMI LLC 2025 Data Breach (74.1 Thousand Reported Records)","ERMI LLC 2025 Data Breach. 74.1 Thousand reported records are reported. Reported data: Names, Social security numbers, Driver's licenses. Review the scope…","\u002Fuploads\u002Flogo\u002Fermi-llc-2025.png",false,{"name":51,"sector":52,"country":53,"website":10,"websiteArchiveUrl":16,"websiteStatus":16,"websiteCheckedAt":13},"ERMI, LLC","Healthcare \u002F Medical Devices and Patient Support","United States"]