Skip to content
attrip.Make things to explore your curiosity
MenuClose

What Did Facebook’s 30 Million Account Check Mean? Reading a 2018 Notice

Published · Updated · 6 MIN READ · Notes and discoveries

RECORD / 2026

This post originally introduced a page for checking Facebook’s “30 million accounts” security incident in October 2018. The incident concerned access tokens stolen in September of that year.

An old screenshot saying an account was not affected cannot establish its security today. The useful questions are which incident the notice covered, when it was issued, and what its answer actually established.

The 30 million figure was an update about the September 2018 incident

Facebook’s October 12, 2018 update described suspicious activity beginning September 14, recognition of the attack on September 25, and closure of the vulnerability within two days. Its estimate changed from 50 million potentially affected people to about 30 million whose tokens were stolen.

The company distinguished three groups:

| Group at the time | Reported access to information |
| — | — |
| About 15 million | Names and contact information |
| About 14 million | Those details plus additional profile information |
| About 1 million | Tokens stolen, but no information accessed |

ITmedia’s October 15 explanation also covered those groups and the checking page. These figures describe this particular incident, not a different leak or Facebook’s entire user population.

The screenshot answered a question about that particular incident

A screenshot of the 2018 Facebook incident notice saying this account was not affected according to the investigation so far
The checking screen preserved in the 2018 post, not a current account-status check.

The image asks whether the account was affected by “this issue” and says the investigation so far found no unauthorized access to that account. My original caption described this as the message shown when the account was okay.

That answer had a specific scope. Reading the image as “not affected by this 2018 incident” is different from treating it as “not compromised today.” Matching the date, incident, and scope of the answer avoids turning an old notice into a present-day security certificate.

The original Help Center link remains. I have not verified that it still offers the same checking function or inspected any reader’s account.

A password and a token that keeps you logged in are different

An access token acts as a key for an existing login. Facebook’s September 28, 2018 explanation said it reset affected tokens, required users to log in again, and did not require everyone to change their passwords because of this incident.

My original post briefly recommended changing a password if affected. Invalidating an access token and changing a password are different operations; the revised explanation follows what the company said at the time.

For a hypothetical comparison of old reports, separate what was stolen, what the service invalidated, and what users were asked to do. A request to log in again does not by itself prove that a password was stolen. This is a history of the 2018 response, not a current interface walkthrough or a diagnosis of an individual account.

Leave a thought

Leave your name blank to post as Anonymous.