Skip to main content
Darkfield

Ransomware victim disclosure

← All victims

Regency Torviscas Apartments & Suites

listed as www.regencytorviscas.com · Claimed by Stormous · listed 1 year ago

14m
Age
since listed · data leaked

Status timeline

  1. ListedMay 11, 2025
  2. Data leakeddate unknown

At a glance

Group
Stormous
Status
Data leaked
Country
Spain
Sector
Hospitality and Tourism
Listed on leak site
May 11, 2025

About the victim

AI dossier — public-source company profile

Regency Torviscas is a spa hotel and apartment resort located in Adeje, Tenerife, Spain. The property offers furnished apartments and suites with spa facilities, pools, and beachfront views, positioning itself as a hybrid between hotel services and private accommodation for leisure travelers.

Industry
Hospitality & Tourism — Apartment Hotels & Spa Resorts
Address
Cataluña, 2, 38660 Adeje, Santa Cruz de Tenerife, España

Attack summary

Severity: critical — Confirmed exfiltration of sensitive PII at scale (passport/ID scans, customer personal data, employee credentials) and operational credentials; high volume of guest and staff personal data from an active hospitality business with documented international clientele.

Stormous claims to have exfiltrated customer reservation databases containing personal identifiers, scanned passport and national ID documents, internal communications, employee and customer email lists, and RDP credential files with plaintext passwords.

critical

Data the group says was taken

AI dossier — extracted from the leak post
  • Full customer reservation database (names, phones, emails, addresses, booking dates)
  • Scanned identification documents (passports, national IDs)
  • Internal emails (OWA)
  • Employee email lists
  • Customer email lists
  • RDP credentials with usernames and passwords

What the group claims

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)

Sources

Source

Indexed 1 year ago

This page surfaces a public ransomware disclosure indexed by Darkfield. Original posts come from the operator's own leak site; we cross-check against ransomware.live, RansomLook and RansomWatch where applicable. Share this URL freely.

Is this your supplier? Your competitor? You?

Pro plans monitor your domain, corporate emails, and crypto wallets across every new ransomware leak-site post, breach dump and Telegram callout — alerts within 5 minutes.

Disclosure context

About Stormous

Stormous is a relatively new ransomware group that emerged in March 2022, operating primarily with financial motivations and has claimed responsibility for attacks against at least 165 victims across multiple countries and sectors. The group's country of origin remains unclear from publicly documented sources, though their operational patterns suggest they may operate as an independent entity rather than a established ransomware-as-a-service model. Limited public documentation from major security firms indicates the group employs common ransomware tactics, though specific details about their initial access vectors, encryption methods, and data exfiltration practices have not been extensively detailed in reports from CISA, FBI, or major threat intelligence providers. Their targeting appears geographically diverse with a focus on Spain, the United States, France, UAE, and Brazil, while showing particular interest in technology, hospitality and tourism, government, and business services sectors, though many of their victims span unspecified industries. As of current reporting, Stormous appears to remain an active threat, though the limited public documentation suggests they operate as a lower-tier ransomware group compared to more prominent families that receive extensive coverage from major security research organizations. The group has been linked to 245 public disclosures across our corpus. First observed on a leak site on March 22, 2022; most recent post July 1, 2026. The operation is currently active.

Timeline of this disclosure

  • May 11, 2025www.regencytorviscas.com listed by Stormouson the group's public leak site

Other recent disclosures by Stormous

Stormous has been linked to 245 public victims on Darkfield. A sample of the most recent:

See the full Stormous dossier →

Sector and geography

This disclosure adds to ransomware activity in the Hospitality and Tourism sector, which has 452 disclosures indexed across all operators we track. Geographically, www.regencytorviscas.com is reported in Spain, a country with 351 ransomware disclosures in our corpus.

If your organisation is affected

A listing by Stormous means www.regencytorviscas.com appeared on a ransomware extortion site and data attributed to it has been published. If this is your organisation, or a supplier you depend on, the priority is to confirm the intrusion and contain it before the window to act closes.

  • Engage your incident-response team and preserve forensic evidence before remediating — do not wipe affected systems first.
  • Force a password reset and revoke active sessions for exposed accounts; rotate any credentials, API keys or certificates that may have been in the stolen data.
  • Assess regulatory notification duties (GDPR, NIS2, sector regulators) — many carry a 72-hour reporting clock from awareness.
  • Report the incident to your national CERT, INCIBE-CERT (Spain), as required for your jurisdiction.
  • Monitor for the data appearing on Stormous's leak site and across paste and breach channels, and brief downstream partners who may be exposed through you.

How we know this. Darkfield monitors public ransomware leak sites continuously, archiving every new disclosure and the data later released against the victim. Each entry on this page is sourced from the operator's own publication and cross-checked against complementary OSINT feeds (RansomLook, ransomware.live, RansomWatch). We do not collect or host stolen data — only the metadata, timestamps and screenshots needed to make the public disclosure searchable and accountable. Records here are corrected when the original post is edited, retracted, or merged with another disclosure.