Polstermöbel Oelsa GmbH was listed on 10 February 2025 by the sarcoma ransomware group (the group's claim; Ransomware Tracker by ExposureDrift has not confirmed a breach). sarcoma listed 7 organizations that month and 144 in total.
- Listed 647 days ago.
- 1011 organizations were listed by all groups in February 2025, see the month.
- 158 in Manufacturing that month.
- 37 in DE that month.
Updated 2026-11-19 06:16 UTC. Data: public leak-site listings. How we work.
Polstermöbel Oelsa GmbH
Threat Group Post & Evidence
- Listed by
- Sarcoma 144 listings in total
The listing states no data size and no ransom demand.
No capture of the original post
We only show a screenshot when we captured the group's own page ourselves. For this listing we have not, so none is shown.
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.
Polstermöbel Oelsa GmbH Since our company was founded in 1869 and thus has a company tradition spanning over 150 years, we have been able to establish ourselves in the market as a specialist for functional upholstered furniture. Our company has functional solutions that are unique in the industry and can be integrated into both classic and modern living room dreams. With our in-house field and customer service and almost 250 employees, our trading partners and customers have a highly motivated team at their disposal to meet the highest quality standards. We would be delighted to help you realize your dream living room!Geo: Germany - Leak size: 987 GB Archive - Contains: Files, SQL, Exchange
Amounts as written
- 250 employees
- 987 GB
Kinds of data mentioned
-
Email and communications
“…room!Geo: Germany - Leak size: 987 GB Archive - Contains: Files, SQL, Exchange”
-
Customer or client data
“…both classic and modern living room dreams. With our in-house field and customer service and almost 250 employees, our trading partners and customers have a highly motivated…”
-
Employee and HR records
“…room dreams. With our in-house field and customer service and almost 250 employees, our trading partners and customers have a highly motivated team at their disposal to meet…”
-
Databases and backups
“…living room!Geo: Germany - Leak size: 987 GB Archive - Contains: Files, SQL, Exchange”
Plain-English summary AI-written
The group says it holds a 987 GB archive containing files, SQL data, and Exchange data.
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 Polstermöbel Oelsa (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 Polstermöbel Oelsa 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 Polstermöbel Oelsa 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, email and communications, employee and hr 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.
Within 30 days
- Keep watching Polstermöbel Oelsa 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 Polstermöbel Oelsa
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: email and communications, customer or client data.
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.
- 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 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: 250 employees, 987 GB. Treat group figures as unverified.
- Check regulatory and stakeholder notification duties EU/EEA: GDPR Art. 33 and 34 require notifying the supervisory authority within 72 hours of becoming aware of a personal data breach, and affected people where risk is high. This is general guidance, not legal advice: confirm current rules with counsel. Why: Listing country: Germany.
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)
60/100 • ELEVATEDA 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 IntelligenceRun a free passive scan on your own domain to see what an attacker can see from the outside.