Ransomware Tracker by ExposureDrift
Dashboard / Victims / www.regencytorviscas.com

www.regencytorviscas.com was listed on 11 May 2025 by the stormous ransomware group (the group's claim; Ransomware Tracker by ExposureDrift has not confirmed a breach). stormous listed 16 organizations that month and 187 in total.

  • Listed 557 days ago.
  • 616 organizations were listed by all groups in May 2025, see the month.
  • 27 in Hospitality that month.
  • 21 in ES that month.

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

www.regencytorviscas.com corporate emblem
Listed by stormous Disclosed: 2025-05-11 03:41 UTC

www.regencytorviscas.com

regencytorviscas.com Hospitality ES

Threat Group Post & Evidence

Listed by
Stormous 187 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.

Full customer reservation databases (names, phones, emails, addresses, booking dates) Scanned ID documents (passports, national IDs) Internal emails via OWA Employee and customer email lists RDP credential files (with usernames/passwords)

Kinds of data mentioned

  • Identity documents

    “…(names, phones, emails, addresses, booking dates) Scanned ID documents (passports, national IDs) Internal emails via OWA Employee and customer email lists RDP credential files…”

  • Passwords and credentials

    “…national IDs) Internal emails via OWA Employee and customer email lists RDP credential files (with usernames/passwords)”

  • Email and communications

    “Full customer reservation databases (names, phones, emails, addresses, booking dates) Scanned ID documents (passports, national IDs) Internal emails…”

  • Customer or client data

    “Full customer reservation databases (names, phones, emails, addresses, booking dates) Scanned ID documents…”

  • Employee and HR records

    “…Scanned ID documents (passports, national IDs) Internal emails via OWA Employee and customer email lists RDP credential files (with usernames/passwords)”

  • Databases and backups

    “Full customer reservation databases (names, phones, emails, addresses, booking dates) Scanned ID documents (passports, national…”

Plain-English summary AI-written

The group says it holds customer reservation records, scanned identity documents, internal emails, email lists, and files containing RDP usernames and passwords.

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 www.regencytorviscas.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 www.regencytorviscas.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 www.regencytorviscas.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, email and communications, passwords and credentials, identity documents, 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 www.regencytorviscas.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 www.regencytorviscas.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: passwords and credentials, identity documents, email and communications, customer or client data.

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, identity documents.
  • 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 for mailbox compromise Audit mailbox rules, forwarding and delegated access, rotate mail-admin credentials and move DMARC to p=reject to limit follow-on phishing. Why: The post names: email and communications.
  • 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.
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 regencytorviscas.com
Industry Vertical Hospitality
Country ES
Enrichment Status ENRICHED

Listing severity score (heuristic)

81/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 30/30 pts
Healthcare and life sciences
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
66/100 • HIGH
Last Audited: 2026-11-14 17:50 UTC Passive Recon
Total Network Assets 16
3 hosts • 13 unique IPs
0 cloud-hosted • 2 SaaS
Subdomain Assets 3
Critical Panels 0 (VPN/Admin/SSO)
Non-Prod / UAT 0 Staging/Dev
SaaS Ecosystem 2 Cloud Apps
Primary CSP Public Cloud / E
Email Security Grade B (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 Not Disclosed / Unresolved
DNS Authority Amazon Route 53
Edge CDN / Shield AWS CloudFront / Edge
SPF Record Missing
DMARC Policy Missing
Public DNS records only • no port scanning

More Claims by stormous

All →
higuchi-inc.co.jp
Manufacturing 2026-06-28 21:30 UTC
HIGUCHI USA, INC
Manufacturing 2026-06-28 21:30 UTC
eogb.co.uk
Energy & Utilities 2026-06-28 21:29 UTC
eshacloudqa.com
Technology 2026-06-28 21:29 UTC
monoprix.tn
Retail & E-Commerce 2026-06-28 21:29 UTC