Solid Trading B.V. was listed on 15 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 368 in total.
- Listed 34 days ago.
- 1147 organizations were listed by all groups in October 2026, see the month.
- 62 in Financial Services that month.
- 9 in NL that month.
Updated 2026-11-18 12:03 UTC. Data: public leak-site listings. How we work.
Solid Trading B.V.
Threat Group Post & Evidence
- Listed by
- N0n 368 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.
FX liquidity and trading technology · Netherlands | Live client trading records: order and execution data for the banks and institutions trading through this firm, with amounts and account identifiers; The client database: companies, platform users with password hashes, credit limits, clearing paths and fee schedules; FIX venue session configurations, including login credentials for liquidity providers; Trade history and bank matching audit records | [NOT PAID — EXPOSED] Initially listed anonymously by N0n as "Company #67" on 2026-10-15.
Kinds of data mentioned
-
Accounting and ledgers
“…login credentials for liquidity providers; Trade history and bank matching audit records | [NOT PAID — EXPOSED] Initially listed anonymously by N0n as "Company #67" on 2026-10-15.”
-
Passwords and credentials
“…account identifiers; The client database: companies, platform users with password hashes, credit limits, clearing paths and fee schedules; FIX venue session configurations,…”
-
Customer or client data
“FX liquidity and trading technology · Netherlands | Live client trading records: order and execution data for the banks and institutions trading through this…”
-
Databases and backups
“…trading through this firm, with amounts and account identifiers; The client database: companies, platform users with password hashes, credit limits, clearing paths and fee schedules;…”
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 Solid Trading 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 Solid Trading 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 Solid Trading 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: customer or client data, passwords and credentials.
- 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: accounting and ledgers.
- 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 Solid Trading 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 Solid Trading 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, customer or client data.
- 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: accounting and ledgers.
Within 3 days
- 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 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: Netherlands.
Within 30 days
- Check shared suppliers and software List the suppliers and software you share with other Financial Services organizations and ask them whether they were affected. Why: N0n listed 40 other Financial Services 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.