[INTERLOCK] – Ransomware Victim: Pritchard Brown & Chillicothe Metal
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 INTERLOCK Onion Dark Web Tor Blog page.
AI Generated Summary of the Ransomware Leak Page
On October 29, 2025, the leak post attributed to the interlock group identifies Pritchard Brown & Chillicothe Metal as a US-based manufacturing victim. The entry frames the incident as a data-leak rather than an encryption event and references a local data share labeled PRITCHARDBROWN[.]local containing about 1.3 TB of data. The body excerpt indicates the attackers have presented the exfiltrated material through a web-based file manager interface described as Tiny File Manager (a PHP-based tool), with a listing structure that includes item type and item name and a search function across folders. A claim URL is provided on the leak page, signaling public engagement or negotiation, though the available data does not include a ransom amount or specific demand.
Metadata indicates there are no screenshots or images on the post, and there are no downloadable items listed. The victim is categorized as Manufacturing, with the country identified as the United States. The provided timestamp, 2025-10-29 06:23:56.814899, aligns with the published post date; there is no separate compromise date present in the data. The page describes a data-leak scenario with alleged data exposure from a local host rather than explicit encryption, and no ransom figure is provided in the supplied information. The summary keeps the victim name as provided and notes the presence of a claim URL for public engagement, but without a stated payment amount in the dataset.
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.
