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 ↓
- Check whether the company's individual notice reached you
- Follow the contents of the notice you received
- Beware of emails and calls posing as the company
3 more
- Review MDM administrator accounts and permissions (general review)
- Tell employees to be careful with messages posing as the IT department
- If you had stored personal information, agree next steps with your in-house owner
- Where to verify (source)All sources ↓
- i Cubed Systems, Inc., notice regarding unauthorized access to its systems and an information leak (November 16, 2026, Japanese)
- 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
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.
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.
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).
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.
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.
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.
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.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.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.
- 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.
| Item | What the company says | Status |
|---|---|---|
| Unauthorized access | By a third party; suspicious access confirmed on November 2 | Confirmed (company) |
| Information leak | Part of the information customers registered in CLOMO MDM leaked | Leak confirmed (company) |
| Contents of the leaked information | Withheld because it could give clues to abuse | Withheld (company) |
| Affected customers | Contacted individually at the system administrator email registered with CLOMO; number and names withheld | Notices in progress |
| Customers with no individual contact | No action requested at this time | Confirmed (company's guidance) |
| Route of entry | Technical details withheld; the route confirmed has been blocked | Partly disclosed (company) |
| Service continuity | The service continues; no outage from this incident | Confirmed (company) |
| Misuse and secondary harm | None confirmed at this time | Not confirmed (company) |
| Products other than CLOMO MDM | No impact confirmed at this time | Not confirmed (company) |
| Detailed cause and scope | Investigation and verification continue | Under investigation |
| Impact on business results | Being examined | Under investigation |
| Report to the Personal Information Protection Commission or others | Not mentioned in the notice or FAQ | Not 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 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.
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.
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.
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.
Read next
- A case involving management software: suspected exploitation of an N-able N-central vulnerability
- How breaches in Japan tend to begin: how 2026 breaches in Japan began
- Guarding against follow-on scams: What is phishing / Smartphone security basics
- Protecting administrator accounts: Multi-factor authentication guide
- Other 2026 incidents: Data breaches and cyberattacks in 2026