Lofotenseafood
bd_d8f55ca43ce0c38b · schema v1 · pii pii-v1
Full breach record for Lofotenseafood →Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group Lynx on its public extortion blog. It has not been validated by the victim or any regulator. Treat attribution and counts as the threat actor's assertion until a regulatory filing or victim disclosure corroborates them.
Source: Ransomware.live
Post text · scraped from the leak site
Lofoten Seafood was established in 1980 by Britt and Roger Mosseng, who started with farming of Atlantic salmon (Salmo salar). Some years later the production of dried and salted fish resumed, which originally had its beginnings in the 1930s. The company has placed emphasis on local control and ownership. Good workers have helped build the company to what it is today. Lofoten Seafood has its own Smolt production - farming of fish - production of fish - processing, as well as its own sales department and export activity. Everything maintained and controlled by the same company. Knowledge and experience are exchanged at every level in the company as we as daily rutines of control of every department. Traceability is very important for the company which helps us trace any matter regarding the fish from its a fish egg to it reach the markets around the world.
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Jan 31, 2025
Claim posted
—
No filing yet · watching
Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.
Claim → filing
—
Compliance clock
Not assessable
Evidence ladder
Attacker assertion only. Establishes: claim date, group, alleged victim.
Unlocks: incident narrative, operational impact. Still no compliance clock.
Unlocks: discovery date, data types, affected count, compliance clock.
Unlocks: materiality, stated response, full audit trail. Ceiling removed.
No regulatory filing corroborates this yet — it is the attacker's own assertion. Watch this entity to be notified the moment a filing corroborates or contradicts it.
Source ceiling
- actor name
- victim claim
- ransom/leak status
- discovery date
- materiality
- notification
- affected count
- confirmed data types
- compliance clock
The ✕ fields stay blank until a regulatory filing or victim disclosure lands.
lynx
According to ransomware.live, Lynx is a ransomware-as-a-service operation that emerged in mid-2024 as a rebrand of INC Ransomware (whose source code was sold for $300,000 on the RAMP forum), claiming ~300 victims across manufacturing, business services, technology, and transportation with an 80/20 profit split for affiliates.