Security Guides

i Cubed Systems CLOMO MDM unauthorized access: part of the data customers registered leaked — what administrators at companies using it should do

i Cubed Systems says unauthorized access leaked part of the data customers registered in CLOMO MDM. Contents and counts are withheld. Admin steps.

Published 2026-11-17 Updated 2026-11-17 Last verified 2026-11-17 11 min read
On this page

For: administrators at companies that use CLOMO MDM (a service for managing smartphones, tablets and other devices), and their employees. This article is based on the company's official notice and does not cover attack techniques.

Developing: this article will be updated as the organisation publishes more

Who is affected

administrators at companies that use CLOMO MDM (a service for managing smartphones, tablets and other devices), and their employees.

Confirmed so farSee the table ↓
  • Unauthorized access
  • Information leak
  • Customers with no individual contact
1 more
  • Service continuity
Not yet confirmed
  • Specific contents of the leaked information
  • Number of affected customers
  • Cause and route of entry
2 more
  • Details of the prevention measures
  • Impact on business results
What to do nowSee the steps ↓
  1. Check whether the company's individual notice reached you
  2. Follow the contents of the notice you received
  3. Beware of emails and calls posing as the company
3 more
  1. Review MDM administrator accounts and permissions (general review)
  2. Tell employees to be careful with messages posing as the IT department
  3. If you had stored personal information, agree next steps with your in-house owner
Last checked
As of November 17, 2026
Follow-up plans and what we checked

The company says it will "promptly announce" any new facts that should be shared. We checked its news list and FAQ on November 17, 2026 and found no update beyond the November 16 notice.

What administrators at companies using it should do today

1

Check whether the company's individual notice reached you

The company says it contacts affected customers individually at the system administrator email address registered with CLOMO. Check first with your in-house system administrator. Also look in spam folders and in the mailboxes of administrators who have left or moved.

For customers who received no contact, the company says it is not asking for any action at this time. Whether a notice arrived is a practical sign of whether you are affected. The number and names of affected customers have not been published.

2

Follow the contents of the notice you received

The company says it tells affected customers individually what leaked and what they need to do. The public notice and FAQ do not give those details.

Check that the notice is genuine through the customer inquiry form on the company's official site or your usual contact point, not through a link in the email.

3

Beware of emails and calls posing as the company

The company asks people to beware of suspicious emails and calls posing as it, and says it never asks for passwords or authentication credentials by email or phone. It also gives the risk of becoming a target of messages posing as the company as a reason for not publishing affected customers' names.

Administrators' contact details are easy material for such messages. Do not open links or attachments, and check through the official site's contact point (how to tell: What is phishing).

4

Review MDM administrator accounts and permissions (general review)

From here on, this is not the company's instruction but a review that suits any company using MDM. List who can use the management console and check that only people who still need it are administrators. Disable administrator accounts that are no longer used.

Use multi-factor authentication for administrator logins (multi-factor authentication guide) and do not reuse administrator passwords on other services. The company's FAQ does not say that it asks customers to change passwords because of this incident.

5

Tell employees to be careful with messages posing as the IT department

MDM generally holds information about devices and users. The company has not said which information leaked here, so pass guidance to employees carefully.

Let staff know that if a message tells them to "fix a device setting" or "reinstall an app", they should not open the link in an email or text but confirm through an official internal channel.

6

If you had stored personal information, agree next steps with your in-house owner

Whether you must notify the people concerned or report to authorities when personal information was among what you registered in MDM depends on what leaked and on your position. Decide with your personal-information owner or legal team, based on the individual notice you receive from the company.

What happened (from i Cubed Systems' notice)

On November 16, 2026, i Cubed Systems, Inc. published a notice regarding unauthorized access to its systems and an information leak, together with an FAQ about the unauthorized access. Everything below is based on those pages.

  1. November 2, 2026

    The company confirmed suspicious access in the systems that run services including CLOMO MDM and began investigating. It immediately blocked the route and started identifying the scope and cause.
  2. After investigation

    It confirmed that unauthorized access by a third party had leaked part of the information customers had registered in CLOMO MDM, and began contacting affected customers individually.
  3. November 16

    Published the notice and the FAQ. It said no new unauthorized access from the same route had been confirmed and that the service continues.
Nov 2
Date suspicious access was confirmed (announced Nov 16)
Withheld
Contents of the leak and number of affected customers
No outage
Service outage caused by this incident (company)
None confirmed
Misuse or secondary harm of the leaked information (at this time)
Overview (from the company's notice)
Service involved
The systems running services including CLOMO MDM. What leaked is part of the information customers had registered in CLOMO MDM
Sequence
Confirmed suspicious access on November 2. Immediately blocked the route and began identifying the scope and investigating the cause
Current situation
Monitoring strengthened. No new unauthorized access from the same route confirmed. The service continues and no outage has resulted
Contents of the leak
Withheld because publishing could give a third party clues to abuse it. Affected customers are told individually
Number and names of affected customers
Withheld because publishing could make them targets of messages posing as the company
Route of entry and system configuration
Withheld because it could give clues to attacks using the same method. The route confirmed has been blocked
Other products
No impact on the company's products and services other than CLOMO MDM has been confirmed at this time
Contact
Customers and partners: the inquiry form on the company's official site (clomo.com/form/order/)

What is known and what is not

Based on the company's notice and FAQ of November 16, as checked on November 17, 2026. We will update the status column as follow-ups appear.

ItemWhat the company saysStatus
Unauthorized accessBy a third party; suspicious access confirmed on November 2Confirmed (company)
Information leakPart of the information customers registered in CLOMO MDM leakedLeak confirmed (company)
Contents of the leaked informationWithheld because it could give clues to abuseWithheld (company)
Affected customersContacted individually at the system administrator email registered with CLOMO; number and names withheldNotices in progress
Customers with no individual contactNo action requested at this timeConfirmed (company's guidance)
Route of entryTechnical details withheld; the route confirmed has been blockedPartly disclosed (company)
Service continuityThe service continues; no outage from this incidentConfirmed (company)
Misuse and secondary harmNone confirmed at this timeNot confirmed (company)
Products other than CLOMO MDMNo impact confirmed at this timeNot confirmed (company)
Detailed cause and scopeInvestigation and verification continueUnder investigation
Impact on business resultsBeing examinedUnder investigation
Report to the Personal Information Protection Commission or othersNot mentioned in the notice or FAQNot stated

Even with no individual notice, watch for follow-ups

The company says it is not asking customers without an individual notice to take any action at this time. That is guidance for "now", and the investigation continues.

In case the scope widens in a follow-up, check that the administrator email address registered with CLOMO is still one you can read.

What can happen when an administration service is targeted

This describes what can generally happen when information registered in an administration service leaks. It does not mean it happened in this case. The company has not said which information leaked.

Administrator contact details and company name

↓

Realistic messages posing as the service provider

→ Do not open links; check via an official contact point

Lists of employees and devices

↓

Messages posing as the in-house IT department

→ Confirm through an official internal channel

What an MDM generally holds, what can follow if it leaks, and the matching action

What the company has not published

  • The specific contents of the leaked information
  • The number and names of affected customers
  • Details of the route of entry and system configuration

What the company says it has not confirmed

  • Misuse or secondary harm of the leaked information (at this time)
  • New unauthorized access from the same route
  • Impact on products and services other than CLOMO MDM
  • A service outage caused by this incident

For people who provide administration SaaS

The cause has not been disclosed, so we cannot say how to prevent a repeat. The points below follow only from the sequence of events the company published.

1

Be able to contact affected customers individually, first

The company says that to prevent misuse it prioritised blocking the route and contacting affected customers individually. Having each customer register an administrator contact so you can reach them any time makes the first response faster.

2

Decide in advance what you will not publish, and why

The company has not published the contents of the leak, the number and names of affected customers, or the route of entry, citing the risk of abuse and targeting. Deciding what to publish in the middle of an incident causes delay. Set the criteria for what is disclosed, by whom and for what reason in calm times.

3

Prepare something customers can do themselves between detection and announcement

The announcement came two weeks after detection. During that time, customers without an individual notice have no way to know what is happening. Preparations such as an FAQ page ready in advance help.

Sources (public record)

The facts in this article are based on the public information below. We have not speculated about the cause or contents, which have not been published.

  • i Cubed Systems, Inc., notice regarding unauthorized access to its systems and an information leak (November 16, 2026, Japanese) — icubedsystems.com
  • i Cubed Systems, Inc., FAQ on the unauthorized access (Japanese) — icubedsystems.com

Update history

2026-11-17: First version, based on the company's notice and FAQ of November 16. We rechecked the company's news list and found no follow-up. We will update this article when new facts are published.

Latest breaking reports

All breaking reports →

FAQ

QWhat was leaked in the CLOMO MDM unauthorized access?
A

According to i Cubed Systems, Inc.'s notice of November 16, 2026, part of the information that customers had registered in CLOMO MDM leaked. The company has not published the specific contents because doing so could give a third party clues to abuse it. It says it tells affected customers individually what leaked and what they need to do.

QHow do I know whether my company is affected?
A

The company says it contacts affected customers individually at the system administrator email address registered with CLOMO, and asks you to check first with your in-house system administrator. It says customers who received no individual contact are not being asked to take any action at this time. It does not publish the number or names of affected customers.

QIs it safe to keep using the service?
A

The company says you can keep using it. It gives as reasons that it has strengthened monitoring of the service environment, that no new unauthorized access from the same route has been confirmed, and that no outage has resulted from this incident.

QAre the cause and route of entry known?
A

The company has not published technical details about the route of entry or the system configuration, saying they could give clues to attacks using the same method. It says the route it confirmed has been blocked, and that it will keep investigating and verifying the details and scope.

QWhat if I get a message claiming to be from the company?
A

The company asks people to beware of suspicious emails and calls posing as it, and says it never asks for passwords or authentication credentials by email or phone. To check whether an individual notice is genuine, use the contact point on the company's official site rather than a link in the email.

QWhy did it take time between detection and the announcement?
A

The company says that, to prevent misuse of the leaked information, it first prioritised blocking the route and contacting affected customers individually with guidance on what to do. It confirmed the suspicious access on November 2 and announced on November 16.