Evolution Spine / All Labs was listed on 16 October 2026 by the N0n ransomware group (the group's claim; Ransomware Tracker by ExposureDrift has not confirmed a breach). N0n listed 150 organizations that month and 394 in total.
- Listed 34 days ago.
- 1147 organizations were listed by all groups in October 2026, see the month.
- 157 in Healthcare that month.
Updated 2026-11-19 05:32 UTC. Data: public leak-site listings. How we work.
Evolution Spine / All Labs
Threat Group Post & Evidence
- Listed by
- N0n 394 listings in total
The listing states no data size and no ransom demand.
Dark Web Leak Proof Screenshot
Original Source (Safe Tor Stream)The group's leak-site address is on paid plans
Free accounts see who listed this organization, when, and what the post claims. The address of the group's own page is shown to license-key holders. If you have a key, see what a license key adds.
What the group says it holds
Taken from the group's own post. Ransomware Tracker by ExposureDrift has not seen the data and cannot confirm any of this.
Medical device manufacturing (US) · Texas, USA | FDA quality system records of a Texas spinal implant manufacturer: CAPAs, device history records for implant lots, management reviews, design drawings and audit files; The complete inventory database of the business, 317 tables, with hospital and surgical-center customers, purchase orders and implant lot shipping records; Finance records: purchase orders, tax forms and payroll timesheets; Hospital product packets for spinal fusion systems and staff mailbox exports | [NOT PAID — EXPOSED]
Kinds of data mentioned
-
Tax records
“…orders and implant lot shipping records; Finance records: purchase orders, tax forms and payroll timesheets; Hospital product packets for spinal fusion systems and staff…”
-
Accounting and ledgers
“…history records for implant lots, management reviews, design drawings and audit files; The complete inventory database of the business, 317 tables, with hospital and surgical-center…”
-
Payroll and salaries
“…lot shipping records; Finance records: purchase orders, tax forms and payroll timesheets; Hospital product packets for spinal fusion systems and staff mailbox exports |…”
-
Medical or patient records
“Medical device manufacturing (US) · Texas, USA | FDA quality system records of a Texas spinal implant…”
-
Customer or client data
“…database of the business, 317 tables, with hospital and surgical-center customers, purchase orders and implant lot shipping records; Finance records: purchase orders, tax forms…”
-
Employee and HR records
“…payroll timesheets; Hospital product packets for spinal fusion systems and staff mailbox exports | [NOT PAID — EXPOSED]”
-
Databases and backups
“…management reviews, design drawings and audit files; The complete inventory database of the business, 317 tables, with hospital and surgical-center customers, purchase orders…”
Plain-English summary AI-written
The group says it holds quality and manufacturing records, an inventory database, financial records, hospital product packets and staff mailbox exports from a spinal implant manufacturer.
Written by an AI model (openai/gpt-6-luna) from the post above. It can contain mistakes: rely on the quote, not the summary.
What to do about this listing
Choose who you are. Each step shows why it appears and, where we have one, its source. General guidance, not legal or incident-response advice.
If you work with Evolution Spine / All Labs (customer, supplier or partner)
Within 3 days
- Do not open the group's page or download the data Do not visit the leak site or download files from a listing. Holding stolen data can be unlawful, and the files can carry malware. Wait for the company's own notice. Why: A safety rule for any leak listing.
- Ask Evolution Spine / All Labs directly Write to your contact and ask whether your data, or your access to their systems, is in scope, and ask for a written statement. Your contract or data-protection law may oblige them to tell you if your data is affected: check the notification clause. Why: A listing is only the group's claim; the company is the one who can confirm what was taken.
- Review what Evolution Spine / All Labs can reach of yours List the accounts, API keys, VPN or SSO connections and shared mailboxes this company has with you. Rotate the keys you gave them and remove access they do not need. Why: Access a supplier holds is how a listing about them can become a problem for you.
- Expect convincing phishing Messages that quote real orders, invoices or names are more likely after a leak. Tell finance and the help desk to treat any request from, or about, this company with extra care. Why: The post names: customer or client data, employee and hr records.
- Verify payment-detail changes by phone Confirm any change to bank details or any urgent invoice with a number you already hold, not one in the message. Why: The post names: payroll and salaries, accounting and ledgers, tax records.
- Check software and integrations you take from them If you run their software or call their API, check that updates come through the usual channel and rotate the keys and tokens you hold for it. Why: The post names: databases and backups.
- If you share health data with them You may be the data controller, with notification duties of your own. Ask counsel which health-privacy rules apply to you. Why: The post names medical or health data.
Within 30 days
- Keep watching Evolution Spine / All Labs A supplier's listing can change after the first sighting: the group can add data, change the status or publish. Add the company to your supplier list to be told, and check your own domain too. Why: A listing is a moving claim, not a single event. Add to your supplier list Check your own domain
If you are Evolution Spine / All Labs
First 24 hours
- Reset credentials and sessions Force password, API-key and session-token resets for the accounts the post suggests were exposed, enforce phishing-resistant MFA, and revoke OAuth/SSO grants issued before the listing date. Why: The post names: customer or client data, payroll and salaries.
- Protect payments Tell your bank, verify any change to supplier or payroll bank details by calling a known number, and watch for invoice-fraud emails that use real names and amounts. Why: The post names: payroll and salaries, accounting and ledgers.
Within 3 days
- Handle health-data exposure Work out which patient or health records are in scope, apply the health-privacy notification rules that cover them, and prepare patient communications. Why: The post names: medical or patient records.
- Support affected individuals Identify the employees or customers whose identity data may be in scope and offer identity-protection or credit monitoring; brief the help desk on likely phishing. Why: The post names: employee and hr records.
- Rotate database and cloud access Rotate database and cloud-storage keys, review public bucket and snapshot sharing, turn on object-level audit logging and keep backup encryption keys separate. Why: The post names: databases and backups.
- Check regulatory and stakeholder notification duties Health data adds sector rules. This is general guidance, not legal advice: confirm current rules with counsel. Why: The listing or sector points to health data.
Within 30 days
- Watch for tax-filing fraud Tell your tax advisers and, where available, tax authorities so fraudulent filings made with exposed identifiers can be caught early. Why: The post names: tax records.
- Check shared suppliers and software List the suppliers and software you share with other Healthcare organizations and ask them whether they were affected. Why: N0n listed 73 other Healthcare organization(s) in the last 90 days.
General readiness for any ransomware claim (not about this listing)
- Offline, immutable backups and a restore drill Keep backups outside domain-admin reach and practise a restore; a leak does not remove the risk of re-encryption. Why: General practice for any ransomware claim; not specific to this listing.
- Look for mass file access and unusual outbound transfers Review EDR, proxy and identity logs for bulk reads, archive creation and large uploads to file-sharing services. Why: General practice for any ransomware claim; not specific to this listing.
- Phishing-resistant MFA on remote access Enforce MFA on VPN, SSO and admin panels, and retire password-only or SMS-based remote access. Why: General practice for any ransomware claim; not specific to this listing.
Listing details
Listing severity score (heuristic)
81/100 • CRITICALA heuristic built from sector, group, data volume and claim details. It is not evidence that a breach occurred or a measure of harm.
External Attack Surface Profile
ASM IntelligenceNo scan has been run for this domain yet, so there are no figures to show. Running one is passive: it reads public DNS and certificate records only.
Launch Attack Surface Recon →Run a free passive scan on your own domain to see what an attacker can see from the outside.