Ransomware Group: LYNX

VICTIM NAME: lofotenseafood[.]com

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 LYNX Onion Dark Web Tor Blog page.

AI Generated Summary of the Ransomware Leak Page

The ransomware leak page concerning Lofoten Seafood describes the company’s extensive background in the agriculture and food production sector, notably its activities in farming and processing fish since its inception in 1980. Established by Britt and Roger Mosseng, the company initially focused on Atlantic salmon farming and later resumed the production of dried and salted fish. The commitment to local control and ownership is emphasized, highlighting the importance of skilled employees in the company’s growth. The leak mentions how the organization maintains rigorous control over various departments, which includes a dedicated smolt production, processing operations, and a sales team that manages export activities.

In terms of cybersecurity implications, the leak was published on March 7, 2025, and appears to contain information about internal operations, though no specific sensitive details or Personally Identifiable Information (PII) are disclosed within the extracted data. The page features a screenshot that likely provides visual context, though the specific content of this image is not detailed. Currently, there are no indicators of employee or third-party data being exposed in association with the breach. The presence of potential download links or additional resources has been suggested, but specific URLs have not been included in this summary, adhering to protocols regarding data sensitivity and privacy.