Ransomware Group: FOG

VICTIM NAME: Kooijman Vianen (kooijmanvianen[.]nl)

NOTE: No files or stolen information are [exfiltrated/downloaded/taken/hosted/seen/reposted/disclosed] by RedPacket Security. Any legal issues relating to the content of the files should be directed at the attackers directly, not RedPacket Security. This blog is simply posting an editorial news post informing that a company has fallen victim to a ransomware attack. RedPacket Security is in no way affiliated or aligned with any ransomware threat actors or groups and will not host infringing content. The information on this page is fully automated and redacted whilst being scraped directly from the FOG Onion Dark Web Tor Blog page.

AI Generated Summary of the Ransomware Leak Page

The ransomware leak page concerning Kooijman Vianen, located in the Netherlands, has disclosed a substantial data leak amounting to approximately 25.7 GB. The incident was discovered on January 23, 2025, and the relevant information was published shortly thereafter. Kooijman Vianen’s website, accessible at kooijmanvianen.nl, is associated with a group known as Fog, which is infamously linked to various cyber ransom activities. However, no workers, users, or third parties have been reported affected in association with this leak, emphasizing the potential limited scope of sensitive data involved, but the exact nature of the information compromised remains unspecified.

The leak page features a screenshot that likely depicts elements of the data breach, reflecting typical content shared during such cyber incidents. There is a notable absence of concrete details regarding individuals or additional data points that could pertain to the company, emphasizing a level of sanitization aimed at protecting PII. As with many ransomware cases, the implications for Kooijman Vianen may be severe, potentially affecting their operations or reputation in the industry. The exact activities of the organization, which is not clearly defined in this report, could influence how they address and mitigate the fallout from this leak.