Van der Spek Vianen B.V. was listed on 17 November 2026 by the rhysida ransomware group (the group's claim; Ransomware Tracker by ExposureDrift has not confirmed a breach). rhysida listed 14 organizations that month and 327 in total.
- Listed 2 days ago.
- 969 organizations were listed by all groups in November 2026, see the month.
- 141 in Manufacturing that month.
- 5 in NL that month.
Updated 2026-11-19 05:29 UTC. Data: public leak-site listings. How we work.
Van der Spek Vianen B.V.
Threat Group Post & Evidence
- Listed by
- Rhysida 327 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.
Van der Spek Vianen B.V. Van der Spek Vianen B.V. (vanderspek.nl) - top Komatsu & tower-cranedealer in the Netherlands.2,773,480 files, ~1.18 TiB.Complete bookkeeping 2015�2026: G/L 8.0M + 15.1M rows, 5,583customers, 5,044 vendors, 4,672 vendor IBANs, receivables incl.VolkerWessels, BAM, Dura Vermeer; 12,202 dunning letters.35 mailboxes fully parsed: >=239,038 messages with bodies(directors, HR, finance, sales), 2011�2026.HR dossiers of ~46 employees: 2026 payslips with IBAN/DOB/address,signed employment contracts, disciplinary warnings, sick-leave mail(medical data), Belgian employee sheets with rijksregisternummer(national ID numbers).SEPA pain.001 payment files, corporate account NL97 ABNA0575393696, NAV license (5964249), live website DB passwords(vanderspek.nl, used-komatsu.nl, hyundai-used.com, emv-cat). More
Amounts as written
- 2,773,480 files
- 5,583customers
- 46 employees
Kinds of data mentioned
-
Banking and wire details
“…finance, sales), 2011�2026.HR dossiers of ~46 employees: 2026 payslips with IBAN/DOB/address,signed employment contracts, disciplinary warnings, sick-leave mail(medical data),…”
-
Identity documents
“…sick-leave mail(medical data), Belgian employee sheets with rijksregisternummer(national ID numbers).SEPA pain.001 payment files, corporate account NL97 ABNA0575393696, NAV license (5964249),…”
-
Passwords and credentials
“…corporate account NL97 ABNA0575393696, NAV license (5964249), live website DB passwords(vanderspek.nl, used-komatsu.nl, hyundai-used.com, emv-cat). More”
-
Medical or patient records
“…IBAN/DOB/address,signed employment contracts, disciplinary warnings, sick-leave mail(medical data), Belgian employee sheets with rijksregisternummer(national ID numbers).SEPA pain.001…”
-
Employee and HR records
“…with bodies(directors, HR, finance, sales), 2011�2026.HR dossiers of ~46 employees: 2026 payslips with IBAN/DOB/address,signed employment contracts, disciplinary warnings, sick-leave…”
-
Contracts and legal files
“…of ~46 employees: 2026 payslips with IBAN/DOB/address,signed employment contracts, disciplinary warnings, sick-leave mail(medical data), Belgian employee sheets with rijksregisternummer(national…”
Plain-English summary AI-written
The group says it holds 2,773,480 files, including company financial records, emails, employee HR and medical information, and payment files.
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 Van der Spek Vianen B.V. (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 Van der Spek Vianen B.V. 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 Van der Spek Vianen B.V. 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: passwords and credentials, identity documents, 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: banking and wire details.
- 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 Van der Spek Vianen B.V. 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 Van der Spek Vianen B.V.
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: passwords and credentials, identity documents.
- 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: banking and wire details.
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, identity documents.
- 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: 2,773,480 files, 5,583customers, 46 employees. 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. Health data adds sector rules. This is general guidance, not legal advice: confirm current rules with counsel. Why: Listing country: Netherlands.
-
Check the ways rhysida is reported to get in
Check these first; they are how the group is reported to work in general.
- Actors typically log in to VPN access points with stolen valid credentials, which the advisory ties to organizations without multi-factor authentication. (update of Apr 2025)
Within 30 days
- Review privileged and contract material Ask counsel which contracts and privileged files are named, and whether client or partner confidentiality terms oblige you to tell them. Why: The post names: contracts and legal files.
- Check shared suppliers and software List the suppliers and software you share with other Manufacturing organizations and ask them whether they were affected. Why: rhysida listed 5 other Manufacturing 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)
79/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 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.