Urgent.News

What's breaking now, across thousands of outlets.

Tech

Daiwa Securities says info on 110,000 clients may have been leaked

The brokerage said the leak resulted from the servers of an external vendor being hacked.

Daiwa Securities says info on 110,000 clients may have been leaked

Daiwa Securities Group announced that the personal information of up to 110,000 clients may have been compromised after an external vendor's servers were targeted by hackers. The brokerage received a notification from vendor Scala Communications on Saturday revealing evidence of unauthorized access to client data, according to a statement released by Daiwa on Monday.

The leaked information consisted of names and account numbers, but it cannot be used to access securities accounts or perform online trading. Neither the brokerage's systems nor any inappropriate transactions linked to the breach have been identified. Daiwa Securities emphasized that its own systems remained uncompromised. The intrusion follows a series of similar incidents in Japan, where companies ranging from logistics firm Yamato Holdings to Sakura Internet also experienced unauthorized access to customer data.

In South Korea, banks have also been affected by client data breaches in recent days, prompting authorities to mandate security assessments. Daiwa Securities expressed regret for causing concern among customers and stakeholders, assuring that the matter is being taken seriously. The company's shares experienced a slight decline in value following the announcement.

Written by urgent.news from Japan Times's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at japantimes.co.jp →

More in Tech

What It Actually Takes to Run a Polymarket Trading Bot 24/7

Getting a Polymarket trading bot to place orders is one problem. Keeping it running correctly for days or weeks is a different problem.

  • Polymarket trading bot requires robust infrastructure beyond functional code
  • Separate process health from trading system health for comprehensive monitoring

Should you require the new iOS? A five-question checklist before you touch the deployment target

Every September someone on the team asks the same thing: now that the new iOS is out, can we just require it? It sounds like housekeeping. It isn't.

  • Not all users can update to the new iOS version; older devices will be excluded from updates
  • Distinguish between using a new API and requiring a new OS; building with new SDK is straightforward
  • Gather your own OS version statistics before deciding to raise the deployment target

CAP Theorem: The Trade-Off Behind Distributed Systems

What if your database has multiple servers, and they suddenly can’t communicate with each other? Should the system keep accepting requests, even if some servers might have outdated data?

  • Consistency guarantees most recent write without stale information
  • Availability ensures responses even with failing system parts
  • Partition Tolerance maintains operation during server communication failures

Java Development Services: Is Java Still Relevant for Android Apps?

A mature Android application can contain hundreds of thousands of lines of Java, serve paying customers, and pass through years of production releases.

  • Java remains relevant for Android apps alongside Kotlin.
  • Legacy code and technical debt factors influence language choice.
  • Kotlin's advantages don't mandate Java's immediate replacement.

More from Monday 5 October →