Ransomware Tracker by ExposureDrift
Dashboard / Victims / FINSA

FINSA was listed on 14 November 2026 by the Barracuda ransomware group (the group's claim; Ransomware Tracker by ExposureDrift has not confirmed a breach). Barracuda listed 4 organizations that month and 18 in total.

  • Listed 5 days ago.
  • 969 organizations were listed by all groups in November 2026, see the month.
  • 96 in Financial Services that month.
  • 12 in ES that month.

Updated 2026-11-19 05:29 UTC. Data: public leak-site listings. How we work.

FINSA corporate emblem
Listed by Barracuda Disclosed: 2026-11-14 17:50 UTC

FINSA

Financial Services ES

Threat Group Post & Evidence

Listed by
Barracuda 18 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.

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.

During an audit of FINSA—a multi-billion-dollar wood processing company—numerous violations in data storage and infrastructure security were identified. We extracted all confidential and production files from their servers, totaling 800 GB. Following this, we completely halted operations by attacking the company’s virtualization. Among the extracted data is now available: Internal production information across FINSA’s facilities Financial documents, databases, and reports Full employee information Wood processing materials and technologies Contracts with partners and their terms And much more. We welcome anyone interested in purchasing all of this company’s data. Additionally, we are prepared to leak the files to the media, competitors, and legal firms for investigations and public lawsuits if you have any intentions toward this company. | $100,000

Amounts as written

  • 800 GB

Kinds of data mentioned

  • Employee and HR records

    “…across FINSA’s facilities Financial documents, databases, and reports Full employee information Wood processing materials and technologies Contracts with partners and their terms…”

  • Contracts and legal files

    “…reports Full employee information Wood processing materials and technologies Contracts with partners and their terms And much more. We welcome anyone interested in purchasing all…”

  • Databases and backups

    “…production information across FINSA’s facilities Financial documents, databases, and reports Full employee information Wood processing materials and technologies Contracts…”

Plain-English summary AI-written

The group says it holds 800 GB of confidential and production files, including internal production information, financial documents, databases, reports, employee information, wood-processing materials and technologies, and partner contracts.

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 FINSA (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 FINSA 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 FINSA 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: 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 FINSA 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 FINSA

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.
  • 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: 800 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: Spain.

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 Financial Services organizations and ask them whether they were affected. Why: Barracuda listed 1 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

Resolved Domain Not stated
Industry Vertical Financial Services
Country ES
Enrichment Status ENRICHED

Listing severity score (heuristic)

48/100 • GUARDED

A heuristic built from sector, group, data volume and claim details. It is not evidence that a breach occurred or a measure of harm.

1. Sector Criticality 10/30 pts
Commercial and general business
2. Group tier 10/25 pts
Tier 3: all other groups
3. Data Volume & PII Scope 18/25 pts
Larger claim: gigabytes, or business or financial records named in the post
Formula: sector • group tier • data claimed (scaled to 100) Rule-based score

External Attack Surface Profile

ASM Intelligence

No 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 →
Is Your Organization Exposed?

Run a free passive scan on your own domain to see what an attacker can see from the outside.

Defense Telemetry

Passive DNS
Mail Gateway Proofpoint Enterprise Protection
DNS Authority Akamai Intelligent Edge
Edge CDN / Shield Akamai CDN
SPF Record Configured
DMARC Policy Enforced
Public DNS records only • no port scanning

More Claims by Barracuda

All →
ProLiant
Technology 2026-11-12 07:22 UTC
ADG Blatt
Professional Services 2026-11-08 22:50 UTC
EVINOKS
Technology 2026-11-01 01:50 UTC
Femern Link Contractors
Transportation 2026-10-28 12:50 UTC
Ministarstvo poljoprivrede, šumarstva i ribarstva
Agriculture and Food Production 2026-10-09 04:20 UTC
Automovil Club del Ecuador ANETA
Transportation 2026-10-02 04:50 UTC