Skip to main content

Ransomware victim disclosure

All victims

DAISEN

Claimed by AiLock · listed 5 days ago

4d
Age
since listed · data leaked

Status timeline

  1. ListedAug 13, 2026
  2. Data leakeddate unknown

At a glance

Group
AiLock
Status
Data leaked
Country
Japan
Listed on leak site
Aug 13, 2026

About the victim

AI dossier — public-source company profile

Daisen Co., Ltd. is a Japanese manufacturer specializing in greenhouse design and construction, vinyl houses, and daylighting architecture with over 130 years of history. The company operates multiple business divisions including agricultural facilities, daylighting/toplight systems for commercial buildings, exterior products, and picture frames.

Industry
Greenhouses, Agricultural Facilities & Daylighting Architecture
Address
〒440-8521 愛知県豊橋市下地町字柳目8, Japan

Attack summary

Severity: medium — Confirmed operational disruption (system outage) and unauthorized access acknowledged by the victim company itself, but no proof files are advertised and no specific data exfiltration is confirmed in the leak post.

AiLock claims to have conducted an unauthorized access attack on Daisen's systems, resulting in system downtime as acknowledged in the company's own notice dated 2026.08.03. The leak post does not specify what data was exfiltrated or the scope of the breach.

medium

What the group claims

DAISEN is a leading manufacturer specializing in greenhouses, vinyl houses, and daylight architecture.

Sources

Source

Indexed 5 days ago

This page surfaces a public ransomware disclosure indexed by Darkfield. Original posts come from the operator's own leak site; we cross-check against ransomware.live, RansomLook and RansomWatch where applicable. Share this URL freely.

Is this your supplier? Your competitor? You?

Pro plans monitor your domain, corporate emails, and crypto wallets across every new ransomware leak-site post, breach dump and Telegram callout — alerts within 5 minutes.

Disclosure context

About AiLock

AiLock is an emerging ransomware group first observed in March 2026 with a primarily financial motivation, having targeted at least 24 known victims across multiple sectors. The group's origin and affiliations remain largely undocumented by major threat intelligence organizations, though their targeting patterns suggest a broad operational scope spanning the United States, Canada, Great Britain, China, and Germany. Based on publicly available information from security researchers, AiLock appears to focus on technology companies, consumer services, manufacturing, and public sector entities, though specific attack methodologies, initial access vectors, and encryption techniques have not been extensively documented by CISA, FBI, or major security firms. The group's relatively recent emergence and limited public documentation suggest they may be a smaller operation or newly formed entity, with no notable major campaigns or high-profile ransoms publicly reported by established threat intelligence sources. Given the March 2026 first observation date and lack of subsequent major public reporting, AiLock's current operational status and capabilities remain largely undetermined by mainstream cybersecurity organizations. The group has been linked to 49 public disclosures across our corpus. First observed on a leak site on March 3, 2026; most recent post August 13, 2026. The operation is currently active.

Timeline of this disclosure

  • August 13, 2026DAISEN listed by AiLockon the group's public leak site

Sector and geography

This disclosure adds to ransomware activity in the Technology sector, which has 3,572 disclosures indexed across all operators we track. Geographically, DAISEN is reported in Japan, a country with 89 ransomware disclosures in our corpus.

If your organisation is affected

A listing by AiLock means DAISEN appeared on a ransomware extortion site and data attributed to it has been published. If this is your organisation, or a supplier you depend on, the priority is to confirm the intrusion and contain it before the window to act closes.

  • Engage your incident-response team and preserve forensic evidence before remediating — do not wipe affected systems first.
  • Force a password reset and revoke active sessions for exposed accounts; rotate any credentials, API keys or certificates that may have been in the stolen data.
  • Assess regulatory notification duties (GDPR, NIS2, sector regulators) — many carry a 72-hour reporting clock from awareness.
  • Report the incident to your national CERT, JPCERT/CC (Japan), as required for your jurisdiction.
  • Monitor for the data appearing on AiLock's leak site and across paste and breach channels, and brief downstream partners who may be exposed through you.

How we know this. Darkfield monitors public ransomware leak sites continuously, archiving every new disclosure and the data later released against the victim. Each entry on this page is sourced from the operator's own publication and cross-checked against complementary OSINT feeds (RansomLook, ransomware.live, RansomWatch). We do not collect or host stolen data — only the metadata, timestamps and screenshots needed to make the public disclosure searchable and accountable. Records here are corrected when the original post is edited, retracted, or merged with another disclosure.