NTT Docomo announced a separate privacy incident that affected customers who signed new contracts using mobile number portability, or MNP, at Docomo retail stores between Sept. 17 and Sept. 25.<\/p>\n\n\n\n
Docomo data breach, what went wrong at stores<\/h2>\n\n\n\n
Docomo said a store system error prevented an important consent screen and related information from appearing during new signups, which meant customers did not have the opportunity to opt in to rich communication services, known as RCS.<\/p>\n\n\n\n
As a result, about 16,000<\/strong> customer records were set to an RCS available status without consent. Docomo said RCS lets users send photos and video over a phone number, and that for 225 of those cases messages were actually exchanged and phone numbers and other data were transmitted to Google Asia Pacific.<\/p>\n\n\n\n Docomo emphasized that message contents were encrypted and that Google cannot read the encrypted content, but the company acknowledged that metadata, such as who contacted whom and when, was transmitted to Google as part of RCS handling.<\/p>\n\n\n\n Docomo said this is not the first time consent procedures failed. The company previously transferred about 340,000 user phone numbers to Amazon without user consent, a separate incident that Docomo attributed to a consent flow error.<\/p>\n\n\n\n Nikkei said the affected Google Workspace accounts are used for staff work email, cloud storage, and other corporate tools. The publisher said it discovered the unauthorized logins only after Google informed it, indicating the attacker remained in the accounts for more than a week.<\/p>\n\n\n\n In its notification, Nikkei said it does not yet know whether the exposed names and email addresses were used for follow-up scams or other misuse. The company said it has informed affected individuals and is reviewing logs and security settings.<\/p>\n\n\n\n Both incidents, disclosed on Oct. 4, highlight different risks of centralized services. In the Nikkei case, Google acted as the notifier, while in the Docomo case a carrier system error caused user consent screens not to appear and metadata to be shared.<\/p>\n\n\n\n For users and IT teams the incidents are a reminder to check account security settings. Companies that use Google Workspace should review login alerts, investigate any unusual sign-in activity, and ensure two factor authentication is enabled for staff accounts.<\/p>\n\n\n\n Customers who signed up at Docomo stores between Sept. 17 and Sept. 25 should watch for individual notices from Docomo beginning Oct. 4, the carrier said. Customers concerned about shared metadata can contact Docomo support for details about what was transmitted to Google.<\/p>\n\n\n\n Readers in Hong Kong and elsewhere who use Google Workspace or RCS should confirm that multi factor authentication is active and that administrators have enabled alerting for suspicious logins, because even large organizations can depend on outside notification to learn they were breached.<\/p>\n\n\n\n For its part, Docomo said it will investigate the store system error and take steps to prevent a recurrence. Nikkei said it is cooperating with Google and reviewing its internal security procedures.<\/p>\n","protected":false},"excerpt":{"rendered":" Docomo data breach and a Nikkei Google Workspace intrusion disclosed Oct. 4 exposed thousands of users’ contact metadata, prompting security checks and company notices.<\/p>\n","protected":false},"author":2,"featured_media":981057,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"inline_featured_image":false,"footnotes":""},"categories":[5012],"tags":[1740,47934,35048,47798,4591,47932,47797,25253,35265,1234,47933,37143],"class_list":["post-981178","post","type-post","status-publish","format-standard","has-post-thumbnail","category-gadgets-en-2","tag-japan","tag-account-security","tag-cybersecurity","tag-docomo","tag-google","tag-mobile-carriers","tag-nikkei","tag-privacy","tag-rcs","tag-tech","tag-user-consent","tag-workspace"],"raw_content":"\n Docomo data breach and a separate Nikkei Google Workspace account intrusion were disclosed Oct. 4 by the companies, exposing contact metadata and prompting privacy checks.<\/p>\n\n\n\n Japan's largest business newspaper, Nikkei, said some staff Google Workspace accounts were accessed illegally from late July into early August, and the company only learned about the intrusion after Google notified it in early August.<\/p>\n\n\n\n Nikkei said the intrusion may have exposed the email addresses and names of 1,646<\/strong> people, and the company has not confirmed whether anyone suffered follow-on harm. Nikkei did not disclose how the accounts were broken into.<\/p>\n\n\n\n NTT Docomo announced a separate privacy incident that affected customers who signed new contracts using mobile number portability, or MNP, at Docomo retail stores between Sept. 17 and Sept. 25.<\/p>\n\n\n\n Docomo said a store system error prevented an important consent screen and related information from appearing during new signups, which meant customers did not have the opportunity to opt in to rich communication services, known as RCS.<\/p>\n\n\n\n As a result, about 16,000<\/strong> customer records were set to an RCS available status without consent. Docomo said RCS lets users send photos and video over a phone number, and that for 225 of those cases messages were actually exchanged and phone numbers and other data were transmitted to Google Asia Pacific.<\/p>\n\n\n\n Docomo emphasized that message contents were encrypted and that Google cannot read the encrypted content, but the company acknowledged that metadata, such as who contacted whom and when, was transmitted to Google as part of RCS handling.<\/p>\n\n\n\n Docomo said this is not the first time consent procedures failed. The company previously transferred about 340,000 user phone numbers to Amazon without user consent, a separate incident that Docomo attributed to a consent flow error.<\/p>\n\n\n\n Nikkei said the affected Google Workspace accounts are used for staff work email, cloud storage, and other corporate tools. The publisher said it discovered the unauthorized logins only after Google informed it, indicating the attacker remained in the accounts for more than a week.<\/p>\n\n\n\n In its notification, Nikkei said it does not yet know whether the exposed names and email addresses were used for follow-up scams or other misuse. The company said it has informed affected individuals and is reviewing logs and security settings.<\/p>\n\n\n\n Both incidents, disclosed on Oct. 4, highlight different risks of centralized services. In the Nikkei case, Google acted as the notifier, while in the Docomo case a carrier system error caused user consent screens not to appear and metadata to be shared.<\/p>\n\n\n\n For users and IT teams the incidents are a reminder to check account security settings. Companies that use Google Workspace should review login alerts, investigate any unusual sign-in activity, and ensure two factor authentication is enabled for staff accounts.<\/p>\n\n\n\n Customers who signed up at Docomo stores between Sept. 17 and Sept. 25 should watch for individual notices from Docomo beginning Oct. 4, the carrier said. Customers concerned about shared metadata can contact Docomo support for details about what was transmitted to Google.<\/p>\n\n\n\n Readers in Hong Kong and elsewhere who use Google Workspace or RCS should confirm that multi factor authentication is active and that administrators have enabled alerting for suspicious logins, because even large organizations can depend on outside notification to learn they were breached.<\/p>\n\n\n\n For its part, Docomo said it will investigate the store system error and take steps to prevent a recurrence. Nikkei said it is cooperating with Google and reviewing its internal security procedures.<\/p>\n","_links":{"self":[{"href":"https:\/\/ztylezman.com\/en\/wp-json\/wp\/v2\/posts\/981178","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/ztylezman.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/ztylezman.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/ztylezman.com\/en\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/ztylezman.com\/en\/wp-json\/wp\/v2\/comments?post=981178"}],"version-history":[{"count":1,"href":"https:\/\/ztylezman.com\/en\/wp-json\/wp\/v2\/posts\/981178\/revisions"}],"predecessor-version":[{"id":981179,"href":"https:\/\/ztylezman.com\/en\/wp-json\/wp\/v2\/posts\/981178\/revisions\/981179"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/ztylezman.com\/en\/wp-json\/wp\/v2\/media\/981057"}],"wp:attachment":[{"href":"https:\/\/ztylezman.com\/en\/wp-json\/wp\/v2\/media?parent=981178"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/ztylezman.com\/en\/wp-json\/wp\/v2\/categories?post=981178"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/ztylezman.com\/en\/wp-json\/wp\/v2\/tags?post=981178"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}![\"Exterior](\"https:\/\/ztylezman.com\/wp-content\/uploads\/2026\/10\/ztylezman.com_docomo-shop-860w.jpg\")
Nikkei Google Workspace intrusion, what Nikkei reported<\/h2>\n\n\n\n
![\"Infographic](\"https:\/\/ztylezman.com\/wp-content\/uploads\/2026\/10\/ztylezman.com_nikkei-docomo-privacy-numbers-860w.jpg\")
What users should do after the Docomo data breach<\/h2>\n\n\n\n
Docomo data breach, what went wrong at stores<\/h2>\n\n\n\n
Nikkei Google Workspace intrusion, what Nikkei reported<\/h2>\n\n\n\n
What users should do after the Docomo data breach<\/h2>\n\n\n\n