[QILIN] – Ransomware Victim: Rex-Hide
![[QILIN] - Ransomware Victim: Rex-Hide 1 image](https://www.redpacketsecurity.com/wp-content/uploads/2024/09/image.png)
NOTE: No files or stolen information are exfiltrated, downloaded, taken, hosted, seen, reposted, or disclosed by RedPacket Security. Any legal issues relating to the content should be directed at the attackers, not RedPacket Security. This blog is an editorial notice informing that a company has fallen victim to a ransomware attack. RedPacket Security is not affiliated with any ransomware threat actors or groups and will not host infringing content. The information on this page is automated and redacted whilst being scraped directly from the QILIN Onion Dark Web Tor Blog page.
AI Generated Summary of the Ransomware Leak Page
On November 7, 2025, a ransomware leak post publicly identifies Rex-Hide as the victim in a post attributed to the threat group qilin. The entry frames the incident as a data-leak event, consistent with double-extortion campaigns that disclose stolen material online. The metadata lists a post date of 2025-11-07 and notes that a claim URL is present on the page, suggesting the attackers provide a link to additional information or a data-claim resource. Ten image attachments are listed on the page, described as screenshots or internal-document visuals; no direct data downloads are indicated in the available data. The industry field is not provided, and there is no explicit ransom amount disclosed in the record. Content is hosted via a Tor onion service, and direct URLs have been defanged in this summary.
The leak page includes ten visual assets, interpreted as screenshots or thumbnails of internal documents or materials related to the breach. While the images are present, the exact contents are not described in detail here. A short body excerpt reiterates the victim name and includes a hashed identifier, which is typical of leak postings that reference exfiltrated material. There is no industry data provided beyond the generic entry, and no ransom figure is shown in the available data. Taken together, the post signals a data-leak scenario rather than a simple encryption event, with attackers offering a claim URL and presenting visuals to substantiate the breach, all hosted on a defanged Tor onion service.
Support Our Work
A considerable amount of time and effort goes into maintaining this website, creating backend automation and creating new features and content for you to make actionable intelligence decisions. Everyone that supports the site helps enable new functionality.
If you like the site, please support us on Patreon or Buy Me A Coffee using the buttons below.
