Ransomware Tracker by ExposureDrift
Dashboard / Victims / **********.com

**********.com was listed on 04 April 2026 by the thegentlemen ransomware group (the group's claim; Ransomware Tracker by ExposureDrift has not confirmed a breach). thegentlemen listed 86 organizations that month and 1119 in total.

  • Listed 229 days ago.
  • 847 organizations were listed by all groups in April 2026, see the month.
  • 103 in Technology that month.
  • 1 other listing for the same organization.

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

**********.com corporate emblem
Listed by thegentlemen Disclosed Date: Not Applicable (Identity Undisclosed)

**********.com

Technology

Named in 2 separate listings

Another listing name this organization: a different group, or the same group months apart. Each is a claim the group published, not a confirmed breach. The same group listing it again within a few months is not counted: that is the same listing sent twice or moved from countdown to published.

This listing: thegentlemen, 04 Apr 2026 kawa4096, 27 Jul 2025

Threat Group Post & Evidence

Listed by
Thegentlemen 1,119 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.

A major IT company developing enterprise software for team collaboration and project management for enterprise clients. 1900 NDA files. Source code. All top 50 fortune clients in 1 place.

Kinds of data mentioned

  • Customer or client data

    “1900 NDA files. Source code. All top 50 fortune clients in 1 place.”

  • Contracts and legal files

    “1900 NDA files. Source code. All top 50 fortune clients in 1 place.”

  • Source code and designs

    “1900 NDA files. Source code. All top 50 fortune clients in 1 place.”

Plain-English summary AI-written

The group says it holds 1,900 NDA files, source code, and information about all top 50 Fortune clients in one place.

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 **********.com (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 **********.com 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 **********.com 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: source code and designs.

Within 30 days

  • Keep watching **********.com 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 **********.com

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 secrets and signing keys Assume secrets in repositories are exposed: rotate API keys, tokens and code-signing keys, and review build and release systems for unexpected changes. Why: The post names: source code and designs.
  • 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

  • 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 Technology organizations and ask them whether they were affected. Why: thegentlemen listed 59 other Technology 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 Technology
Country Not stated
Enrichment Status ENRICHED

Listing severity score (heuristic)

79/100 • ELEVATED

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 20/30 pts
Technology and communications
2. Group tier 25/25 pts
Tier 1: among the groups with the most listings in our data
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 thegentlemen

All →
AARP
Healthcare 2026-11-18 09:22 UTC
NVIDIA
Technology 2026-11-18 09:22 UTC
BAE Exchange
Financial Services 2026-11-17 16:56 UTC
Rosenberger Legal
Professional Services 2026-11-17 16:56 UTC
Bio architecture Formosana
Agriculture and Food Production 2026-11-17 16:56 UTC
Ebema
Manufacturing 2026-11-17 16:55 UTC

Other listings for this name

2 listings
thegentlemen Viewing Now
2026-04-04 22:42 UTC Severity: 79/100
2025-07-27 09:44 UTC Open listing →