TrendAI found three attacker servers aimed at Japan, one running CyberStrikeAI with 44 agents. Microsoft ties ARTEX to Storm-0940. What is proved, what is not, and how to detect it.
Where to find how breaches are really done, a dated timeline to 25 October 2026, and a reproducible risk model on 264 Japanese notices: a heavy tail and supplier cascades.
Names, plus phone numbers, addresses and possibly dates of birth, for 2,155,345 Lawson ID accounts; Lawson corrected on 24 October that email addresses did not leak. What to check.
The 38 largest disclosures of the past 12 months and all 153 notices of the last 60 days, sorted by how the data got out: apps and APIs, analytics tools, suppliers, accounts, ransomware.
Sender and recipient details for about 100 days of parcels may have leaked through a tracking lookup. What that means for your own public lookup services, and for companies that ship with a carrier.
At 21:55 on 21 October, Sanae Takaichi asked website owners to patch PHP that night, or switch their sites off. What PHP2Shell is, how much of Japan it reaches, and what to do now.
IT OperationsSIEMEDRThird-party RiskLegal / Privacy
At least ten Japanese companies said data left through their apps, APIs or lookup pages this autumn. How to find every API you run, test it, fix it and watch it, with queries and templates.
BK Japan says its app's member system was accessed from 2 to 7 October. What leaked, what the dates show, and an outside-in risk card for its internet-facing systems, scored without the details.
The company behind the ZERO antivirus range, Fudegurume and Pocketalk says a member API was misused for four days. What leaked, who its customers are, and what they should check.
IT OperationsSIEMEmail SecurityLegal / PrivacyThird-party Risk
New daily public-IPv4 scans bring port histories, banners and fingerprints to VirusTotal. See what changed, where to find it and how to pivot to related infrastructure.
Ransomware hit IDCF Cloud on 7 October 2026. The 14 October report: backups for 194 customers, no sign data left their servers, 48 portal records viewed; new notices from Mouse, Izumi, JR Central.
IT OperationsEDRSIEMThird-party RiskEmail SecurityLegal / Privacy
The travel site disclosed three intrusions on 9 October. Four days later NICT warned of “A2B” attacks that start by analysing a company's app. What leaked, how the routes differ, and what to check.
IT OperationsSIEMEmail SecurityLegal / PrivacyThird-party Risk
On 8 and 9 October a minister and the ruling party called Japan's wave of breaches critical, even an emergency. What was said, what it does and does not mean, and what our numbers showed first.
IT OperationsSIEMThird-party RiskLegal / PrivacyEmail Security
Asahi Kasei Therapeutics’ HCP site was breached at its operator. Why specialty-tagged HCP data and MR photos fuel targeted phishing, and what pharma teams should check now.
Passport details and allergy notes for up to 627 travellers may have been taken from an overseas file server. Why scoping took 300 days, and what to check in your own subsidiaries.
IT OperationsEDRSIEMLegal / PrivacyThird-party Risk
Files linked to 15,382 accounts were accessed or obtained. Separate profile and password-data exposures show why cloud incidents need both privilege and data-impact reviews.
IT OperationsSIEMThird-party RiskLegal / PrivacyEmail SecurityEDR
A night-time system failure led to traces of an intrusion that began at a web-system vulnerability. What the two notices say, what changed between them, and what online retailers should check.
About 6.6 million accounts and identity documents for 1.6 million. Updated with Japanese licence images for sale on a dark-web site and 40,000 lawsuit sign-ups.
A software vulnerability exposed all 948,498 records of the GMO survey site infoQ, and 611 accounts had points exchanged without consent. What points operators, SOCs and members should check.
IT OperationsSIEMEmail SecurityLegal / PrivacyThird-party Risk
Verified scope of the Yakiniku King app breach, impersonation and recovery risks, team actions, decision branches and scoped KQL/Splunk hunting templates.
G Point’s incident explained: identifier scope, outage and point protection, partner reconciliation, team responsibilities and KQL/Splunk review templates.
All five campuses lost their systems on 2 October. Data on at least 130,000 students and graduates may have leaked. What a shared virtualisation platform and reachable backups mean for recovery.
IT OperationsSIEMEDRLegal / PrivacyEmail SecurityThird-party Risk
A research brief on the 'Big Four' state actors in 2025–26: their mandates, who they hit (Japan is 20% of China-linked targeting in Microsoft's data), and the hunts that follow.
Mail from a real Nikkei account led recipients to a malicious site on 30 September. What recipients should check, and why the stated fix, a password change, is not the whole recovery.
CertiK counts 248 incidents and a 54% rise in Q3 2026, but only 10% after returned funds. Bitget's $387.5M theft began with a zero-day in a security product. What security teams should learn.
1,360,563 member records may have been viewed, and the sales system also stored unhashed server and VPS passwords. What hosting customers should rotate, check and hunt for.
IT OperationsThird-party RiskSIEMLegal / PrivacyEmail SecurityEDR
A China-aligned actor that targets think tanks in the US and Japan relays Microsoft's real sign-in through a fake browser window. What stops it, who acts, and how to hunt for it.