Ransomware Tracker by ExposureDrift
Dashboard / Victims / Liztex Guatemala

Liztex Guatemala was listed on 03 June 2026 by the thegentlemen ransomware group (the group's claim; Ransomware Tracker by ExposureDrift has not confirmed a breach). thegentlemen listed 76 organizations that month and 1119 in total.

  • Listed 168 days ago.
  • 708 organizations were listed by all groups in June 2026, see the month.
  • 118 in Manufacturing that month.
  • 2 in GT that month.

Updated 2026-11-14 15:56 UTC. Data: public leak-site listings. How we work.

Liztex Guatemala corporate emblem
Listed by thegentlemen Disclosed: 2026-06-04 09:09 UTC

Liztex Guatemala

liztex.com Manufacturing GT

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.

***.com Liztex is a leading Guatemalan textile manufacturer with over 50 years of experience in producing fabrics. We want to inform you that our group managed to breach and encrypt Liztex network. 398GB leaked from there as a result of this breach. What kind of data leaked: - SAP data - contacts - contracts - planning - logistics - projects data - personal data - employee data - medical data - partners data - customers data - financial data - correspondence - production data - quality control data - offers and proposals - subsidiary data - other sensitive business data

Amounts as written

  • 398GB

Kinds of data mentioned

  • Medical or patient records

    “…planning - logistics - projects data - personal data - employee data - medical data - partners data - customers data - financial data - correspondence - production data…”

  • Customer or client data

    “…data - personal data - employee data - medical data - partners data - customers data - financial data - correspondence - production data - quality control data - offers and…”

  • Employee and HR records

    “…contacts - contracts - planning - logistics - projects data - personal data - employee data - medical data - partners data - customers data - financial data - correspondence - production…”

  • Contracts and legal files

    “…result of this breach. What kind of data leaked: - SAP data - contacts - contracts - planning - logistics - projects data - personal data - employee data - medical data - partners…”

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 Liztex Guatemala (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 Liztex Guatemala 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 Liztex Guatemala 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, employee and hr records.
  • If you share health data with them You may be the data controller, with notification duties of your own. Ask counsel which health-privacy rules apply to you. Why: The post names medical or health data.

Within 30 days

  • Keep watching Liztex Guatemala 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 Liztex Guatemala

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

  • Handle health-data exposure Work out which patient or health records are in scope, apply the health-privacy notification rules that cover them, and prepare patient communications. Why: The post names: medical or patient records.
  • 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.
  • 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: 398GB. Treat group figures as unverified.
  • Lock down exposed admin, VPN and SSO panels Restrict by IP allow-list or a zero-trust proxy and require MFA. Why: A passive scan found 1 critical panel(s) reachable from the internet.
  • Check regulatory and stakeholder notification duties Health data adds sector rules. This is general guidance, not legal advice: confirm current rules with counsel. Why: The listing or sector points to health data.

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 Manufacturing organizations and ask them whether they were affected. Why: thegentlemen listed 73 other Manufacturing 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 liztex.com
Industry Vertical Manufacturing
Country GT
Enrichment Status ENRICHED

Listing severity score (heuristic)

88/100 • CRITICAL

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
Industrial manufacturing
2. Group tier 25/25 pts
Tier 1: among the groups with the most listings in our data
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
75/100 • CRITICAL
Last Audited: 2026-11-14 16:34 UTC Passive Recon
Total Network Assets 17
5 hosts • 12 unique IPs
0 cloud-hosted • 2 SaaS
Subdomain Assets 5
Critical Panels 1 (VPN/Admin/SSO)
Non-Prod / UAT 0 Staging/Dev
SaaS Ecosystem 2 Cloud Apps
Primary CSP Public Cloud / E
Email Security Grade A (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 Microsoft 365 / Exchange Online
DNS Authority Authoritative DNS (biz)
Edge CDN / Shield None
SPF Record Configured
DMARC Policy Enforced
Public DNS records only • no port scanning

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