Ransomware Tracker by ExposureDrift
Dashboard / Victims / FinSoft

FinSoft was listed on 22 September 2026 by the N0n ransomware group (the group's claim; Ransomware Tracker by ExposureDrift has not confirmed a breach). N0n listed 18 organizations that month and 368 in total.

  • Listed 57 days ago.
  • 874 organizations were listed by all groups in September 2026, see the month.
  • 65 in Retail & E-Commerce that month.
  • 1 in UZ that month.

Updated 2026-11-18 07:36 UTC. Data: public leak-site listings. How we work.

FinSoft corporate emblem
Listed by N0n Disclosed: 2026-09-22 01:51 UTC

FinSoft

Retail & E-Commerce UZ

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)
Full Resolution
Capture of the page on N0n's leak site that lists FinSoft
© Ransomware Tracker by ExposureDrift • Watermarked copy of the group's own page. The unmodified capture is available on request.
Window Viewport (1280x962) | Capture of the group's own page | Zero Local Tooling Execution • Pure Text-Stream Ingestion

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.

Retail software vendor / IT services · Uzbekistan | Client databases of 10+ retail chains (keddo, marc, lancaster, comf_rus, ek, cr, bas_at, bas_juk, bas_nov, bas_zar): sales, stock, pricing, financial records; Back-office platform and API service data | One client database publishes per day after the deadline, starting with keddo. Their clients will know exactly whose software failed them. | [ACTIVE: deadline 2026-09-25 01:06 UTC]

Kinds of data mentioned

  • Customer or client data

    “One client database publishes per day after the deadline, starting with keddo. Their clients will know…”

  • Databases and backups

    “One client database publishes per day after the deadline, starting with keddo. Their clients will know exactly…”

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 FinSoft (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 FinSoft 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 FinSoft 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.
  • 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 FinSoft 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 FinSoft

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: customer or client data.

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 No country is recorded for this listing. Identify the data-protection and contractual duties that apply where the affected people live, and ask counsel. General guidance, not legal advice. Why: The listing records no country.

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 56 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

Resolved Domain Not stated
Industry Vertical Retail & E-Commerce
Country UZ
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.

More Claims by N0n

All →
SOGELEC Iskan for Electrical Contracting W.L.L.
Construction & Real Estate 2026-11-18 17:25 UTC
Ardi Youth Academy
Education 2026-11-18 17:03 UTC
Jazz Pharmaceuticals plc
Healthcare 2026-11-17 22:51 UTC
CarNow LLC
Technology 2026-11-17 21:26 UTC
Vir Biotechnology, Inc.
Healthcare 2026-11-16 11:01 UTC
Verastem Oncology (Verastem, Inc.)
Unknown 2026-11-16 11:01 UTC