Ransomware Tracker by ExposureDrift
Dashboard / Victims / enTouch

enTouch was listed on 09 October 2026 by the Black X ransomware group (the group's claim; Ransomware Tracker by ExposureDrift has not confirmed a breach). Black X listed 3 organizations that month and 17 in total.

  • Listed 41 days ago.
  • 1147 organizations were listed by all groups in October 2026, see the month.
  • 187 in Technology that month.
  • 12 in JP that month.

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

enTouch corporate emblem
Listed by Black X Disclosed: 2026-10-09 19:13 UTC

enTouch

entouch.jp Technology JP

Threat Group Post & Evidence

Listed by
Black X 17 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.

enTouch is a Japanese IT company specializing in the medical and pharmaceutical sectors, providing services for online consultations, sales activities, and customer data management between pharmaceutical companies and medical institutions. We possess the entire database from data.entouch.jp, the data analysis system used by enTouch. The database contains sensitive customer information, including names, contact details, consultation schedules and records, and sales activity data categorized by pharmaceutical company.

Plain-English summary AI-written

The group says it holds enTouch’s entire database, including customer names, contact details, consultation schedules and records, and pharmaceutical-company sales activity data.

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 enTouch (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 enTouch 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 enTouch 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.

Within 30 days

  • Keep watching enTouch 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 enTouch

Within 3 days

  • Find out what was actually taken The post names no specific kind of data, so no data-specific steps are shown. Check the group's own post and your logs to learn what is claimed and what is real. Why: The listing text names no data types.
  • Retire staging and dev exposure Take non-production hosts off the internet or behind authentication, and rotate any secrets they held. Why: A passive scan found 2 non-production host(s) that are public.
  • Check regulatory and stakeholder notification duties Japan: the APPI requires reporting certain leaks to the Personal Information Protection Commission and notifying affected people. This is general guidance, not legal advice: confirm current rules with counsel. Why: Listing country: Japan.

Within 30 days

  • Check shared suppliers and software List the suppliers and software you share with other Technology organizations and ask them whether they were affected. Why: Black X listed 2 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 entouch.jp
Industry Vertical Technology
Country JP
Enrichment Status ENRICHED

Listing severity score (heuristic)

69/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 10/25 pts
Tier 3: all other groups
3. Data Volume & PII Scope 25/25 pts
Largest claim: a terabyte or more, or regulated data named in the post
Formula: sector • group tier • data claimed (scaled to 100) Rule-based score

External Attack Surface Profile

ASM Intelligence
95/100 • CRITICAL
Last Audited: 2026-11-14 16:04 UTC Passive Recon
Total Network Assets 9
5 hosts • 4 unique IPs
0 cloud-hosted • 1 SaaS
Subdomain Assets 5
Critical Panels 0 (VPN/Admin/SSO)
Non-Prod / UAT 2 Staging/Dev
SaaS Ecosystem 1 Cloud Apps
Primary CSP Public Cloud / E
Email Security Grade D (SPF/DMARC)
Open the full attack surface scan →
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 Google Workspace
DNS Authority Authoritative DNS (jp)
Edge CDN / Shield None
SPF Record Missing
DMARC Policy Missing
Public DNS records only • no port scanning

More Claims by Black X

All →
Court Square Group
Financial Services 2026-11-10 04:58 UTC
Forus Deporte y Ocio S.L
Hospitality 2026-11-10 04:57 UTC
DomusVi
Healthcare 2026-11-10 04:56 UTC
bayer
Healthcare 2026-10-09 19:14 UTC
lopay
Financial Services 2026-10-09 19:12 UTC