Ransomware Group: INTERLOCK

VICTIM NAME: Anderson & Karrenberg

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

AI Generated Summary of the Ransomware Leak Page

The ransomware leak page centers around the law firm Anderson & Karrenberg, based in Salt Lake City, Utah, in the United States. The group claiming responsibility appears to be associated with the “interlock” ransomware variant. The attack was publicly disclosed on July 18, 2025, with the incident report indicating the attack date as the same day. The leak website contains a screenshot of internal documents or data, suggesting the firm has been compromised and sensitive information may be made available to the public or malicious actors. The attack does not specify the content of the data leak but highlights a significant cybersecurity incident affecting this legal services provider.

The website provides a link to a dark web page where purported data leaks or stolen information are hosted, although specific details about the nature of the leaked data are not included in the summary. Notably, the law firm specializes in legal representation, emphasizing high standards and effective results for clients. The attack’s impact on their operations and data confidentiality remains uncertain publicly, but the incident underscores ongoing cybersecurity threats faced by professional service providers. The page includes a screenshot and indicates that no additional external parties or third-party data sources are involved in this particular breach.