NTT Docomo Breach: Up to 300,000 Customers' Names, Addresses and Birth Dates Possibly Exposed — Online Shop and My docomo Shut Down, and the Same-Day 5G Outage Was Not the Attack

Cyber · 2026-11-06 · By H.A

NTT Docomo Breach: Up to 300,000 Customers' Names, Addresses and Birth Dates Possibly Exposed — Online Shop and My docomo Shut Down, and the Same-Day 5G Outage Was Not the Attack

Docomo detected a likely intrusion on 4 November and took its Online Shop and My docomo offline; up to about 300,000 records with names, addresses, birth dates and phone numbers may be exposed, its third security incident in weeks.

What Happened

NTT Docomo, Japan's largest mobile operator with about 91 million mobile subscriptions, says outsiders very probably got into its servers. Up to about 300,000 customer records may have been exposed. The company detected the intrusion on Wednesday 4 November and, at about 1:05 a.m. on Thursday 5 November, took its Docomo Online Shop and My docomo account portal offline for emergency maintenance.

The records that may have been accessed contain names, postal addresses, dates of birth, mobile phone numbers and contact phone numbers. Docomo has not yet said whether payment details, including credit card data, were involved. That question is still under investigation, as are the cause and the full scope of the intrusion.

Services Still Restricted

The online shop and contract procedures in My docomo stayed suspended through 5 and 6 November, with no reopening date announced. At times customers could still check data usage and bills, but not buy phones or change contracts online. Docomo is directing urgent requests to its shops and retail partners and to its phone support lines.

Docomo says it has found no further leaks since the first discovery. It will contact affected customers individually once it knows who they are, but it has not said how or when.

A Separate Outage, Not the Attack

Hours after the shutdown, at about 11:18 a.m. on 5 November, Docomo customers on 5G standalone (5G SA) began having trouble with calls, data and SMS nationwide. Many people assumed it was part of the attack. Docomo says it was not: the outage was caused by congestion in the switching equipment that handles 5G SA subscribers, and its investigation found no sign of unauthorized access or a cyberattack before or after the outage.

Service came back at about 1:20 a.m. on 6 November, roughly 14 hours later. 4G users, people on non-standalone 5G, operators that rent Docomo's network, and emergency calls were not affected. Customers who switched their phones to 4G as a workaround have been told to switch back. Docomo's terms only pay compensation when service is completely unusable for 24 hours or more, so this outage falls short of that rule.

The Third Incident in Weeks

The breach caps a bad autumn for Docomo and its parent, NTT:

It is not yet known whether the new intrusion is connected to the October contractor breach.

Why It Matters

Names, addresses, dates of birth and phone numbers are exactly what scammers need to make convincing fake messages. Expect a wave of SMS, emails and phone calls pretending to be Docomo, offering "compensation" or a "refund", or asking for "identity verification". These usually lead to card-harvesting pages or ask for one-time codes. Phone numbers tied to a real name and address also make SIM-swap attempts and account-recovery fraud more likely.

What Docomo Customers Should Do

Reef Sentinel Take

Two things stand out. First, this is the third security event at Docomo in about three weeks, coming after a contractor breach of almost 450,000 records. That points to wider problems across the group and its suppliers, not one unlucky intrusion. Second, the timing of the outage shows how quickly confusion spreads: a network failure that had nothing to do with the attack was widely read as part of it. Until Docomo publishes the cause and confirms whether payment data was reached, treat this as an exposure of identity data and prepare for phishing that targets customers.

COMPUTE NODE · · --:--:--

Fresh cybersecurity news,
daily threat intelligence.

Daily cyber news, live threat intel and exploited CVEs.

Everything in one place

Self-hosted, hardened, and yours.

RUN IT

Local AI console

Chat with a model on your own hardware via Ollama or any OpenAI-compatible server. No cloud, no key.

DEFEND

Cyber threat feed

Automatic daily intel from CISA KEV, NVD & GitHub advisories, a live cyber threat map, and your own notes.

NEWS

News & videos

Articles and updates on pentesting, AI, and cyber — with embedded video, including YouTube. Post your own.

DIRECTORY

Registry

Runtimes, models, MCP servers, agents, and a full security & pentest tooling section.

PUBLISH

Posts

Write, edit, publish, and share articles backed by a real database and your account.

COMMUNITY

Forum

Threads and replies across categories from Models to Hardware to Security.

CODE

Repos

Curated AI and security GitHub repos, plus a shelf for pinning your own.

DOWNLOAD

Skill packs

Agent starters, RAG scaffolds, and defensive security & VAPT report templates.

Registry

Runtimes, models, MCP servers, agent frameworks, and a security & pentest tooling section — all links out to the real projects.

Local AI console

Talk to a model running on your own machine through Ollama or an OpenAI-compatible server — your prompts and the model's replies always go straight from your browser to your local model, never through a Reef server. Attach files for context, and pick up saved chats where you left off.

Type /image a prompt in the box below to generate
Not connected

Local AI hardware benchmark

A spec-based compatibility advisor — tells you which local models your hardware can run well, which will be slow, and which to skip. Connect to Ollama below for a real, measured speed test instead of an estimate.

1. Your hardware

2. Live check against your local model server (optional)

If a local model server is running, this cross-references the table above with what you've actually got loaded — and runs a real, measured speed test instead of an estimate.

AI Database

A browsable catalog of AI models across providers — context windows, pricing, and capabilities.

Loading…

Cyber threat feed

Latest threats pulled automatically every day from CISA's Known-Exploited-Vulnerabilities catalog and NVD — plus threat intel you post yourself.

⇩ Export STIX
Loading threat feed…

Cyber threat map

Attacks happening right now, all over the world.

Connecting…
LIVE · MAURITIUS TIME--:--:--
attack route, country to country attack route into Mauritius attacker reported worldwide
Loading live data…
attackers reported per minute · click to rewindnow

Top attack routesweb

Attackers based inlast hour

Networkslast hour

Click any dot, feed row or table row to see that IP's profile.

Mauritius

Who attacks Mauritius

Loading…

Web attacks malicious requests to Mauritian websites that were blocked
Network DDoS floods meant to knock Mauritian servers offline

    Mauritius · last 24 h

    How Mauritius is attacked

    Network-level attacks (DDoS) aimed at Mauritius, by method. They try to knock servers and networks offline by sheer volume.

    • Loading…

    The ports or services these floods aimed at aren't published.

    Mauritius · last hour

    Attackers located in Mauritius

    0attackers located in Mauritius were reported in the last hour

    This counts attacks coming from Mauritius, not attacks on it: IPs in Mauritius that servers elsewhere reported for attacking them. Usually zero or one; when it rises, it's often a hacked local server or router.

    Worldwide today

    What attackers are knocking on

    Ports most targeted across a worldwide network of sensors .

    Worldwide today

    Most active attackers

    Ranked by how many separate sensors they hit. Click a row for its profile.

    IPCountryNetworkSensors hitReports
    What you're looking at
    Blue routes

    Share of attack traffic from one country to another. Thicker, faster streams carry more. Particles show volume, not one per attack.

    Every 15 min · published 1–2 h behind
    Amber flashes

    An attacking IP that servers around the world reported in the last minute, placed where the IP is. Its targets aren't published, so there's no line.

    Every minute · shown about 1 min behind
    Locations

    IP locations are approximate (city level at best) and show where the machine is hosted, not who controls it.

    Approximate · city level at best

    News

    Articles, guides and updates on pentesting, AI, and cybersecurity — with embedded video. Add your own, including YouTube.

    Loading…

    Posts

    Loading…

    Loading posts…

    Forum

    Questions, answers, and talk about running AI locally.

    Loading forum…

    GitHub repositories

    Curated AI and security repos, plus your own pinned shelf.

    Command board

    One-liners, configs, and advice worth keeping — shared by everyone here.

    ⚠ Commands are shared with all users. Never include credentials, tokens, or internal hostnames. Review anything before you run it.
    Loading commands…

    Skill packs

    Starter files served from the API — AI agent scaffolds plus defensive security & VAPT reporting templates. Click to download.

    Loading skills…

    Threat Library

    Threat actors, malware and tools — their attack techniques, Reef Sentinel coverage and indicators of compromise.

    Loading…

    Threat Intelligence

    Curated threat write-ups, advisories and analysis — with cover media.

    Loading…

    Tutorials

    Step-by-step guides for running local AI, using the console, and tracking threats. Admins can add their own.

    Loading…

    Downloads

    Direct links to the official homepage/download page for well-known cybersecurity, penetration-testing, and local-AI software. Always verify checksums/signatures from the vendor before running anything.

    Loading…

    Terms & Conditions

    Loading…

    Help & FAQ

    Answers to common questions about Reef Sentinel, plus a formatting guide for posts, articles, and comments.


    Formatting guide

    Commands you can type into the body of a post, comment, or reply — no HTML needed. Comments and short replies only support bold, italic, and inline code.

    Contact us

    Questions, feedback, or a security disclosure? Reach us directly, or send a message and we'll get back to you by email.

    Loading…

    Send a message

    VAPT Report Generator

    Build an engagement, add findings with a live CVSS calculator, and generate a branded, print-ready report.

    Recon Toolkit

    Passive OSINT lookups for the recon phase of an engagement, plus offline hash identification and a payload cheatsheet.

    Website Checker

    Reads a website's HTTP response headers to identify its framework and server, shows any known CVEs for the exposed versions with details, and recommends what to do.

    Control panel

    Manage everything shown on the site — news & videos, posts, homepage headlines, and subscribers. Admin only.

    Overview
    Content
    Site
    Account & Security

    Email settings

    SMTP on ports 25/465/587 is blocked outbound by some hosts (e.g. DigitalOcean droplets by default) — Resend and Brevo send over their HTTPS API instead, so they work even then. Only the selected provider is used to send; the others stay saved but idle, so you can switch back any time without losing settings.

    Get a key from resend.com/api-keys. Uses the "From address" below as the sender — it must be on a domain you've verified with Resend.

    Get an API key (not an SMTP key) from app.brevo.com/settings/keys/api. Uses the "From address" below as the sender — it must be a verified sender in your Brevo account.

    "From address" and "Site name/URL" are shared by SMTP, Resend, and Brevo — they control what recipients see, regardless of which provider is active.

    Send a test email

    Sends through whichever provider is currently active above. Save your settings first if you just changed them.