[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f1tyx0r0ikkcm9":3},{"success":4,"breach":5},true,{"_id":6,"name":7,"title":8,"slug":9,"domain":10,"breachDate":11,"addedDate":12,"modifiedDate":12,"contentUpdatedAt":12,"source":13,"sourceUrl":14,"sourceUrls":15,"pwnCount":18,"affectedCount":18,"affectedCountStatus":19,"affectedCountLowerBound":20,"affectedCountUnit":21,"hasEnglishDescription":4,"severity":22,"dataClasses":23,"description":26,"seoTitle":27,"seoTitleEn":28,"seoDescription":27,"seoDescriptionEn":29,"logoUrl":30,"isVerified":4,"isSensitive":31,"isSpamList":31,"isMalware":31,"company":32},"6a70855bbe8abb4e6396dd6d","Nursa2026","Nursa 2026 Data Breach","nursa-2026","nursa.com","2026-02-27T00:00:00.000Z","2026-08-03T12:11:07.578Z","Washington Attorney General filing, Nursa notice, independent filing report, and official company website","https:\u002F\u002Fagportal-s3bucket.s3.amazonaws.com\u002Fdatabreach\u002FBreachM24095.pdf",[14,16,17],"https:\u002F\u002Fwww.atg.wa.gov\u002Fdata-breach-notifications","https:\u002F\u002Fnursa.com\u002F",13168,"known",null,"people","Medium",[24,25],"Names","Dates of birth","\u003Cp>\u003Cstrong>The 2026 Nursa data breach\u003C\u002Fstrong> involved an unauthorized person viewing and exporting a limited number of user profiles from the healthcare staffing and shift-management platform. A filing with the Washington Attorney General confirms that at least 13,168 Washington residents were affected.\u003C\u002Fp>\u003Cp>Nursa connects healthcare professionals and facilities for flexible, short-term shifts. The disclosed 13,168 people represent Washington residents only; because no nationwide total has been published, the figure must be treated as a verified lower bound.\u003C\u002Fp>\u003Ch2>How did the Nursa data breach happen?\u003C\u002Fh2>\u003Cp>According to the official filing, an unauthorized person accessed Nursa's web application and exported a limited number of user profiles on February 27 and March 18, 2026. These are two confirmed access dates; the sources do not say that access continued throughout the period between them.\u003C\u002Fp>\u003Cp>Nursa became aware of the unauthorized activity on March 20, 2026. The company said it resecured the platform, engaged cybersecurity specialists, and investigated the scope of the event. The initial access method and the identity of the attacker have not been publicly disclosed.\u003C\u002Fp>\u003Ch2>What information was involved?\u003C\u002Fh2>\u003Cp>The Washington filing identifies first and last names and dates of birth as the affected information. Nursa's sample letter says the affected profiles contained names with an additional person-specific field, while the regulator cover letter confirms that field as date of birth.\u003C\u002Fp>\u003Cp>Public sources do not support Social Security numbers, passwords, financial accounts, payment cards, medical records, or insurance information as part of this incident. The catalog therefore limits the data scope to names and dates of birth; operating in healthcare does not by itself establish that medical information was affected.\u003C\u002Fp>\u003Ch2>Why do names and dates of birth matter?\u003C\u002Fh2>\u003Cp>A name combined with a full date of birth can help an attacker guess identity-verification answers, craft personalized phishing messages, or enrich a profile with information obtained elsewhere. Those fields may not be sufficient to open a financial account on their own, but they can make targeted fraud more convincing.\u003C\u002Fp>\u003Cp>Nursa users should be cautious with unexpected messages about shifts, recruitment, document updates, or healthcare facilities. The absence of a known identity-fraud report as of the notice date does not guarantee that misuse will not occur later.\u003C\u002Fp>\u003Ch2>How did Nursa respond?\u003C\u002Fh2>\u003Cp>After detecting the activity, the company resecured its platform, worked with specialists on forensic investigation and remediation, and reviewed its existing security policies and protections. Written notices to affected people were sent on May 13, 2026.\u003C\u002Fp>\u003Cp>Nursa also provided a professional assistance line for questions and fraud-prevention resources. Its notice says the company was not aware of identity fraud or fraudulent activity connected to the event at the time of notification.\u003C\u002Fp>\u003Ch2>What should affected people do?\u003C\u002Fh2>\u003Cp>Notice recipients should verify Nursa account activity only through the official app or nursa.com and should not disclose a password, one-time code, identity document, or financial detail in response to an unexpected message. A request claiming to come from a facility or recruiter should be checked through a known contact channel rather than a link in the message.\u003C\u002Fp>\u003Cp>Credit reports and financial accounts can be reviewed regularly for unfamiliar activity. If a fraudulent transaction, account, or use of identity information appears, it should be reported to the relevant organization and authorities; a fraud alert or credit freeze may also be appropriate.\u003C\u002Fp>","","Nursa 2026 Data Breach (13.2 Thousand People Affected)","The Nursa data breach affected at least 13,168 people after names and dates of birth were exposed through unauthorized profile exports.","\u002Fuploads\u002Flogo\u002Fnursa-official.svg",false,{"name":33,"sector":34,"country":35,"website":17,"websiteArchiveUrl":27,"websiteStatus":27,"websiteCheckedAt":20},"Nursa","Healthcare","United States"]