[INTERLOCK] – Ransomware Victim: Maki Building Centers

image

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.

Ransomware group:
INTERLOCK
Victim name:
MAKI BUILDING CENTERS

AI Generated Summary of the Ransomware Leak Page

On 2025-10-27 15:47:48.518761, a leak post attributed to the Interlock ransomware group identifies Maki Building Centers, a Construction industry firm, as a victim. The leak page presents a description of a Web-based File Manager in PHP and references Tiny File Manager as the tool to manage files. The page includes a claim URL indicator, suggesting there is an external link for claims or additional data, though no specific URL is provided in the data. No screenshots or images are embedded on the page, and there are no downloadable files listed. A body excerpt shows a listing-like UI with phrases such as “Item Type,” “Item Name,” and a feature to search files within a folder and subfolders, implying the page exposes a structured file index or access portal rather than a standard ransom note.

The post does not specify an impact, such as encryption or a data leak, within the provided metadata; there is no visible ransom amount or negotiation terms. The absence of images or downloads, combined with the file-manager interface excerpt, suggests limited detail about the data stolen and the breach’s scope in the released content. The victim is identified as Maki Building Centers within the Construction sector, while the Interlock group is listed as the actor; the timestamp attached to the leak is treated as the post date, with no separate compromise date available. Given the lack of explicit indicators of data type or extortion demands, the risk cannot be fully assessed from this page alone without corroborating information from other sources.

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.

AI APIs OSINT driven New features