[RANSOMHOUSE] – Ransomware Victim: Public Safety Mutual Benefit Fund
![[RANSOMHOUSE] - Ransomware Victim: Public Safety Mutual Benefit Fund 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 RANSOMHOUSE Onion Dark Web Tor Blog page.
AI Generated Summary of the Ransomware Leak Page
On November 4, 2025, a leak post attributed to the ransomware group Ransomhouse claims to have compromised Public Safety Mutual Benefit Fund, a public sector financial institution based in the Philippines (PH). The victim is identified by name (Public Safety Mutual Benefit Fund) and the page carries the ©Ransomhouse branding, indicating attribution to the threat actor. The post is described as a data breach or data leak event, but the available metadata does not specify whether data was encrypted or exfiltrated, as the impact field is not populated. The record provides a post date but no explicit compromise date beyond that publication date, and it notes that a claim URL is present on the page, suggesting a mechanism for negotiation or contact, though the exact link is not included in the data provided.
From the metadata, there are no downloadable items or visual assets associated with the leak—downloads are indicated as not present and image counts are zero. The body excerpt reads “Loading… Status: Share Contact us,” implying the page content is minimal or in a loading state, with standard sharing and contact actions visible to visitors. There are no explicit ransom figures, data types, or compromise specifics disclosed in the available fields, and no images or screenshots are reported. The victim’s name remains the explicit identifier preserved in this summary, while the leak’s branding (©Ransomhouse) confirms attribution to the group. A claim URL is indicated as present on the page, but the URL itself is not provided here.
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.
