Staples, Inc. / SBD Inc. was listed on 04 November 2026 by the N0n ransomware group (the group's claim; Ransomware Tracker by ExposureDrift has not confirmed a breach). N0n listed 227 organizations that month and 395 in total.
- Listed 15 days ago.
- 981 organizations were listed by all groups in November 2026, see the month.
- 113 in Retail & E-Commerce that month.
- 431 in US that month.
Updated 2026-11-19 05:30 UTC. Data: public leak-site listings. How we work.
Staples, Inc. / SBD Inc.
Threat Group Post & Evidence
- Listed by
- N0n 395 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.
office supply retail · United States | Per product profit margin records for the retail storefront of a major North American office supply company: 381,964 records from a single daily file; Unit sales and revenue for 64,041 products; Shopper activity logs with IP addresses, search terms and devices; Shopper chat transcripts including a callback phone number; A staff directory with names and email addresses for close to 200 employees; A pasted table of 30 social security numbers with dates of birth in a service chat | [NOT PAID — EXPOSED] Initially listed anonymously by N0n as "Company #129" on 2026-11-04.
Amounts as written
- 381,964 records
- 200 employees
Kinds of data mentioned
-
Identity documents
“…names and email addresses for close to 200 employees; A pasted table of 30 social security numbers with dates of birth in a service chat | [NOT PAID — EXPOSED] Initially listed anonymously…”
-
Email and communications
“…transcripts including a callback phone number; A staff directory with names and email addresses for close to 200 employees; A pasted table of 30 social security numbers with dates…”
-
Employee and HR records
“…devices; Shopper chat transcripts including a callback phone number; A staff directory with names and email addresses for close to 200 employees; A pasted table of 30…”
Plain-English summary AI-written
The group says it holds retail records covering product margins, sales and revenue, shopper activity and chats, a staff directory, and a table of social security numbers with birth dates.
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 Staples, Inc. / SBD (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 Staples, Inc. / SBD 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 Staples, Inc. / SBD 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: email and communications, identity documents, employee and hr records.
Within 30 days
- Keep watching Staples, Inc. / SBD 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 Staples, Inc. / SBD
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: identity documents, email and communications.
Within 3 days
- 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, identity documents.
- Check for mailbox compromise Audit mailbox rules, forwarding and delegated access, rotate mail-admin credentials and move DMARC to p=reject to limit follow-on phishing. Why: The post names: email and communications.
- Size the exposure against your own systems Inventory which systems hold data of the kind and volume claimed, so notification and legal decisions rest on your records rather than the group's figures. Why: The post claims: 381,964 records, 200 employees. Treat group figures as unverified.
- Check regulatory and stakeholder notification duties United States: state breach-notification laws apply; listed companies may also have SEC Form 8-K Item 1.05 duties for material incidents, and HIPAA applies to health data. This is general guidance, not legal advice: confirm current rules with counsel. Why: Listing country: United States.
Within 30 days
- Check shared suppliers and software List the suppliers and software you share with other Retail & E-Commerce organizations and ask them whether they were affected. Why: N0n listed 64 other Retail & E-Commerce 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)
56/100 • GUARDEDA 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.