Incidents

Cacoo Data Breach: Nulab Confirms Unauthorized Access Exposed About 792 Support Records

Nulab confirms unauthorized access to Cacoo exposed about 792 support ticket records, including personal data and, in some cases, last four card digits.

Cacoo Data Breach: Nulab Confirms Unauthorized Access Exposed About 792 Support Records

Japanese software company Nulab has confirmed unauthorized access to the Cacoo service environment and the exposure of some customer support ticket records. In a November 16 notice, the company said about 792 records are affected so far, though that number may change as its review continues. The records contained personal data, and some also included the last four digits of payment card numbers. Nulab has found no unauthorized access to customer data in Backlog or any of its other services.

What happened

According to Nulab, the unauthorized access occurred on November 14. The company detected that credentials had been misused in Cacoo’s production environment. It then revoked those credentials and blocked access from the source of the attack. At 6:45 p.m. Japan time that day, Nulab took Cacoo offline and began emergency maintenance. The service was still offline when the notice was published.

The exposed records may have included names, email addresses, phone numbers, postal addresses and, in some cases, the last four digits of card numbers. Nulab is still working to determine the full scope of the incident and has said it will contact affected individuals directly. The company has reported the incident to Japan’s Personal Information Protection Commission.

What to do if you use Cacoo

Anyone who has contacted Nulab’s technical support should watch for messages that impersonate the company. Be especially careful with messages that refer to a support request and ask for a password, authentication code or payment details. Don’t open unexpected attachments or log in through links in such messages. If in doubt, go to the service at its known address and check the company’s announcements yourself.

Administrators should follow Nulab’s updates and confirm whether their users have received individual notifications. Nulab has not confirmed a data breach in any of its other services, so you shouldn’t assume the incident affected Backlog accounts.

SecurHUB’s take

When an incident hits a third-party service, you may need to work out quickly which data and processes depended on it. Incident response helps you set priorities and keep communication with users consistent.

Sources: Nulab – incident notice, TSN Media

AuthorSecurHUB Team

Read more

Related articles

Want to know if this affects your company?

A free consultation with one of our experts — no obligation, in full confidence.

Let's talk