[SAFEPAY] – Ransomware Victim: mino-in[.]co[.]jp

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

Ransomware group:
SAFEPAY
Victim name:
MINO-IN[.]CO[.]JP

AI Generated Summary of the Ransomware Leak Page

On 2025-10-24 21:23:19.966774, a ransomware leak post associated with the Safepay group references the victim mino-in.co.jp, a long-established Japanese technology manufacturer. The leak page presents a corporate profile of a company that designs and builds screen-printing machines, stencil makers, dryers, printing accessories, and specialty inks. It positions the business as one of Japan’s few “total” screen-printing suppliers, covering equipment manufacture, consumables, and technical service, and notes a domestic and export footprint. The profile highlights product lines that serve apparel decoration, industrial printing, signage, and specialty printed electronics, and mentions an export-oriented operation with roughly 100 employees and plausible annual sales in the low billions of yen. The page emphasizes background information about the company rather than a detailed breach summary, and it contains no images or downloadable content; there is a claim URL indicated for readers seeking additional information.

The post date is 2025-10-24 21:23:19.966774, and there is no explicit compromise date provided in the accessible excerpt, so the post date functions as the publication date of the claim. The excerpt does not clearly state whether the attack encrypted systems or leaked data, and it does not specify any ransom amount. Overall, the leak page appears to present background corporate information about the victim rather than a concrete breach narrative, with a claim URL suggesting there may be another page containing the claim details, but the visible content remains focused on the company’s profile rather than attack particulars. No screenshots or media are shown on the page, consistent with the data indicating zero images and zero downloads.

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