KuroCMS Dev Log Vol.6: Enhancing Security Amid the Wave of Mass Data Leaks
product Business Software Technology

KuroCMS Dev Log Vol.6: Enhancing Security Amid the Wave of Mass Data Leaks

Recent AI cyberattacks drive massive leaks. Like Russia or Israel taking land and dignity, you must defend yourself in this world. KuroCMS remains OSS while heavily boosting security.


The scale of cyberattacks and hacking damages that began around September 2026 continues to expand unabated. While urgent countermeasures are universally recognized as necessary, the scope of damage keeps growing daily. For reference, we have compiled a comprehensive table of recent incidents below.

List of Major Data Breaches Occurred from September 2026 to Present#

Enterprises and organizations that announced personal data leaks or potential exposures due to unauthorized access and related incidents (dates indicate publication date). Total of 64 cases. *Listed in reverse chronological order

DateEnterprise / OrganizationDetailsScaleCause
Oct 17
(Sat)
Skyticket (Travel Booking)Credit card data breachedApprox. 6,000 peopleUnauthorized access
Oct 16
(Fri)
Yamato TransportPersonal data breachedApprox. 5.31M recordsUnauthorized access
NikkeiPersonal data leak1.83M recordsUnauthorized access
Mitsubishi Gas ChemicalPersonal data of former staff leaked2,000 peopleContractor / Vendor
Studio (Web Design Tool)Suspected customer data leak—Unauthorized access
FANCL Group affiliatePersonal data leak830,000 recordsUnauthorized access
Comic CmoaMember data leaked (emails, DOB)—Unauthorized access
Japan PostCustomer records left exposed600 recordsUnauthorized access
Hitachi AstemoBusiness partner data leaked350 peopleUnauthorized access
Times Car (Park24)Response policy announced on Oct 23—Follow-up report
IwaiCosmo SecuritiesCustomer data leak4,600 peopleContractor / Vendor
Hamamatsu CityFire dept data leak suspected (via Arcadia)—Contractor / Vendor
BASE subsidiaryPersonal data leak (incl. 2.09M credit cards)23.35M peopleUnspecified
Keio CorporationRansomware claim confirmed by cyber gang 'Qilin'—Ransomware
Oct 15
(Thu)
M3, Inc.Pharma services personal data leaked—Unauthorized access
SOURCENEXTSuspected customer data leak22.52M recordsUnauthorized access
Burger King JapanMobile app member data leaked11.18M recordsUnauthorized access
Medley, Inc.Medical system breach suspectedUp to 787 facilitiesUnauthorized access
Oct 14
(Wed)
transcosmos inc.Contract job applicant data leakedApprox. 4,600 peopleUnspecified
Mazda Motor CorporationCommunity portal breach suspected4,103 peopleContractor / Vendor
Aena (Cosmetics Retailer)Member data breach suspected810,000 peopleUnauthorized access
Izumi Co., Ltd.Risk of data breachUp to 400,000 recordsSoftBank affiliate
JR Kyushu Restaurant Sub.Personal data breach suspected26,900 peopleUnspecified
Oct 13
(Tue)
Japan PostRisk of customer data breachUp to 4,807 recordsSystem glitch
Municipal Disaster Info ServiceEmail addresses potentially leaked3.13M recordsUnauthorized access
Gin no Sara (Sushi Delivery)Customer data leaked via external serverUp to 6.5M recordsUnauthorized access
JR CentralEmail leak suspected on proprietary EC site—SoftBank affiliate
Omaezaki City, ShizuokaData leak risk via disaster mail vendor—Contractor / Vendor
SKY Perfect JSATEmail addresses potentially leaked—SoftBank affiliate
Yamaha / Yamaha MotorSNS member data breach suspectedTotal 3,200 peopleUnspecified
Oct 10
(Sat)
DIP Corporation (Baitoru)Email addresses leakedUp to 3.88M recordsUnspecified
Temairazu (Channel Manager)Data breach suspected4.45M peopleUnauthorized access
Oct 9
(Fri)
JR KyushuEmail addresses potentially leakedUp to 1.3M recordsSoftBank affiliate
LY CorporationPersonal data leak via search tool—Contractor / Vendor
Bandai Namco Group affiliateArcade game member records leaked—Unauthorized access
Mizkan GroupEmail addresses and other data leaked—Contractor / Vendor
Resorttrust, Inc.Member records leaked via website26,000 recordsUnauthorized access
Sansan, Inc.Data leak suspected from external cloud10,000 peopleUnauthorized access
Suzuki Motor CorporationEmail addresses and other data potentially leaked—Contractor / Vendor
JR EastEmail addresses potentially leaked—SoftBank affiliate
BOOKOFF subsidiarySuspected customer data leakUp to 6.43M recordsUnauthorized access
Oct 8
(Thu)
NewsPicksPotential personal data leak—Unauthorized access
Lawson, Inc.Personal data leak (names, addresses, etc.)Approx. 2.15M recordsUnauthorized access
Daiichikosho Co., Ltd.Risk of personal data leak8.72M recordsContractor / Vendor
The Bank of IwateCustomer data leak suspected (via partner Daiwa's vendor)—Contractor / Vendor
Oct 7
(Wed)
HIS subsidiaryPassport records potentially leakedUp to 627 peopleUnauthorized access
Sompo Japan InsurancePotential customer data leak60,000 recordsUnauthorized access
Oct 6
(Tue)
Asahi Kasei Group affiliateHealthcare professional portal breach suspectedUp to approx. 560,000 peopleUnspecified
Citizen Watch Co., Ltd.Customer data leak suspected100,000 peopleContractor / Vendor
Nimoca (Nishitetsu Group)Customer records breachedApprox. 500 recordsUnauthorized access
GMO Internet Group affiliatePersonal data leaked and loyalty points abused950,000 peopleUnauthorized access
MrMax HoldingsCustomer records breachedUp to 1.73M peopleUnauthorized access
Oct 5
(Mon)
Daiki Suisan (Sushi/Seafood)Data breach suspected170,000 peopleUnauthorized access
Osaka Metropolitan UniversityRisk of personal data leak130,000 peopleRansomware
Yakiniku KingCustomer data leakOver 10 million recordsUnauthorized access
Daiwa SecuritiesBank account numbers and customer data leak suspected220,000 recordsContractor / Vendor
Oct 4
(Sun)
NikkeiData breach, 9,000 phishing emails dispatched—Unauthorized access
NikkeiCredential stuffing led to personal data leak1,646 peopleUnauthorized access
Oct 3
(Sat)
ABAHOUSE HOLDINGSAll customer data potentially leaked (flagged via suspicious emails)All customersUnspecified
Oct 2
(Fri)
Dai-ichi Life GroupEmployee records leaked (including retirees)120,000 peopleUnspecified
Sagawa ExpressPersonal data leak suspected (names, addresses, etc.)—Unauthorized access
Sep 30
(Wed)
2 Osaka Gas affiliatesPotential customer data leakApprox. 8,260 recordsUnauthorized access
Sep 29
(Tue)
Secoma (Seicomart)Data leak suspected from application server570,000 recordsUnauthorized access
Sep 28
(Mon)
Times CarPersonal data leaked (incl. driver's license scans)Up to 6.6M recordsUnauthorized access
Total (44 cases with stated scale; combined records and individuals, including duplicates)Approx. 124 million

A truly staggering toll: approximately 124 million records. Even accounting for uncertain figures and overlap, the total volume of compromised records essentially equals the entire population of Japan.

Key Characteristics of Recent Damages and Intrusion Vectors#

While recent incidents exhibit damage on an unprecedented scale, the most alarming aspect is the sheer frequency—breaches occurring practically every single day. Attackers are unmistakably leveraging advanced AI capabilities. Although many victims have not disclosed their breach pathways, among those that have, the overwhelming majority stem from vulnerabilities in "web applications, sites, and APIs."

The second most prevalent vector involves "email lures and site redirection (phishing)." With generative AI producing flawlessly natural prose, users are easily tricked into clicking deceptive links that lead to replica sites identical to authentic portals, entering credentials that are promptly harvested.

While vulnerabilities in VPN gateway hardware often dominate headlines, only a single incident (Digital Agency) explicitly cited VPN flaws during this period. The overwhelming majority entered via the two vectors above, exacerbated by weak post-intrusion administrator access controls—system architectures where an intruder gains virtually unchecked lateral privileges.

How Does KuroCMS Address These Security Threats?#

To begin with, account takeovers via phishing emails or spoofed websites simply cannot occur in KuroCMS because it relies exclusively on passkeys. Beyond our personal aversion to memorizing passwords, people inevitably choose simple, reusable passwords when forced to remember them, creating a profound structural vulnerability that passkeys fundamentally eliminate.

Here is an overview of the core security measures that were already in place in KuroCMS v1:

VersionCountermeasureDetails
v1Passkey-Only AuthenticationWith no passwords stored anywhere, there are no credentials to leak or reuse. Users authenticate via biometric fingerprint or facial recognition, with cryptographic keys never leaving the local device enclave. Session states are stored in isolated formats inaccessible to third-party sites or external scripts.
v1Full Revision Rollback for AI EditsPrior to overwriting or deleting any article text, a complete snapshot is recorded as an immutable version. Authorship (human, AI, or API) is cryptographically stamped via the authentication layer and cannot be forged. Even if an intruder alters content, the entire article can be reverted instantly.
v1Hashed Storage of API KeysPersonal Access Tokens (PATs) utilized for AI orchestration are stored solely as one-way cryptographic hashes. Original token strings never persist on servers, rendering stolen database records useless as API credentials.
v1Zero Storage of Cloudflare Master KeysWhen deploying to personal Cloudflare environments, API tokens entered during setup are consumed in memory for deployment only and never saved anywhere. Subsequent automated updates are handled by a least-privilege token restricted exclusively to Worker script deployments.
v1Pre-built Static HTML DeliveryVisitors are served strictly pre-compiled static HTML pages without querying live databases on each request, drastically shrinking the external attack surface. Features fetching external URLs strictly validate targets prior to retrieval (SSRF mitigation), which concurrently enables edge CDN caching for blistering load speeds.

And here is an overview of the significant security enhancements introduced in the latest v2 update:

VersionEnhancementDetails
v2Strict Script Sanitization in ContentArticle content and site copy undergo rigorous dual-pass sanitization—both upon persistence and upon client rendering—eliminating script tags, DOM event attributes, javascript: pseudo-protocols, and unauthorized embeds. Scripts will never execute in visitor or administrator browsers, regardless of whether content was authored by humans, AI, APIs, or data imports.
v2Signature-Verified UpdatesNew releases are fetched from KuroCMS's official distribution infrastructure and verified against digital signatures and content hashes before installation. If a newly deployed build fails health checks, WorkerOps automatically rolls back to the prior stable release.
v2Strict Tenant Data IsolationArticles and media assets reside exclusively inside the client's own Cloudflare account. Under managed hosting, infrastructure and CMS instances are account-isolated with dedicated per-tenant databases. Telemetry bug reports transmit solely numerical error codes, never article content.
v2Admin Access Restricted to Registered NetworksThe administrative console is strictly accessible only from the specific IP network used during passkey authentication. IP registration is fully automated and dynamically renewed during active use. Any session activity from an unrecognized IP triggers an immediate session lock and verification alert to the owner.
v2Network and Device Cryptographic BindingBrowser sessions are strictly bound to the origination IP network. Session refresh tokens are cryptographically bound to the specific hardware security key of the issuing device (device binding). Even if a session token is intercepted, it cannot be replayed from another network or machine.

What Changed? Future Roadmap and Strategic Evolution#

The most significant architectural enhancement is IP restriction. In the modern IPv6 era, where every individual device can possess a unique global IP address, accessing the KuroCMS admin panel requires matching the registered IP. Spoofing an IPv6 address is extraordinarily difficult even for tier-1 ISP network engineers. Combined with passkeys bound directly to the browser and hardware enclave, conventional penetration becomes virtually impossible.

In conjunction with this, we migrated KuroCMS's authentication foundation to an enterprise-grade corporate ID platform. This aligns with our introduction of the Managed Hosting model for users who find creating Cloudflare accounts and generating PATs challenging. As a result, the enterprise ID platform monitors anomalous access, instantly alerting users via dashboard notifications and emails while enabling our security operations center to mitigate threats immediately.

This was a decision over which we deliberated extensively. We committed to keeping KuroCMS's core source code fully open-source, while housing only the authentication backbone within a closed, highly hardened enterprise infrastructure. To ensure existing self-hosted users experience no disadvantage, direct deployment to personal Cloudflare accounts (the sole method in v1) remains fully supported. We sincerely apologize for the slight inconvenience of requiring email registration.

Compared to v1, KuroCMS v2 represents a massive leap forward in defensive security. We deeply appreciate your continued trust and support.

*KuroCMS v2 is expected to be released around this weekend.





How was this article?