← Blog

Apify Data Breach: Hashes, Tokens, Billing (Nov 2026)

Share on X

9-10 November 2026: Apify says an unauthorised party used a compromised credential, obtained further account credentials and accessed related customer accounts. Detected 11 November at 12:13 UTC. Census unpublished. See the Apify breach record.

The status page remains the primary source. SecurityWeek reported a Reddit copy of a customer letter with a longer field list. Treat that list as one customer copy, not a published inventory. 91,000 customers is a marketing figure, not this census.

What happened at Apify?

Stolen login, 9-10 November, cut off 11 November 12:13 UTC. Authorities notified. API tokens and Proxy passwords rotated, sessions invalidated, some OAuth including GitHub revoked, 2FA reset prompted. Letters went to customers Apify had identified. No email yet means not identified so far, not a lifetime all-clear.

Different customer letters have not matched word for word. BleepingComputer saw a note that 2FA codes may have been exposed while passwords remained safe. The Reddit copy lists hashes and recovery codes. Catalog both as letter variants, not as a contradiction you have to pick in secret.

What data was exposed?

SecurityWeek's Reddit-letter list: names, emails, billing, activity, IPs, salted password hashes, 2FA recovery codes and phones, Google/GitHub sign-in tokens, cardholder name, expiry and last four. No full PAN or CVV on that copy. recordsAffected stays 0.

Recovery codes are the sharp item. One of them bypasses 2FA. Reset 2FA in Console, keep only the new codes, change the password anyway, rotate tokens wherever you pasted them.

The Fireworks post is the other mid-November developer-platform incident. Keep the two vendors separate.

Who is affected?

Customers whose personal information or stored data Apify says was accessed. If you got the email, follow it. If you did not, Apify has not identified your account yet. Actor data, datasets and secret inputs were described as not accessed in some letters. Do not assume that for every account.

More on the company is on the Apify company page.

What should customers do?

  1. Reset 2FA in Settings, Login and Privacy. Discard old recovery codes.
  2. Change the password, even if a letter said hashes were salted.
  3. Replace rotated API tokens and Proxy passwords in scripts, n8n, Make, Zapier, MCP, agents.
  4. Review Google and GitHub app access if you used those sign-ins.
  5. Treat billing-failure invoices as hostile for a while.

Apify will not collect a card CVV through a new domain to restore an Actor.

Is 91,000 the census?

No. That is a marketing customer count. recordsAffected stays 0 until Apify or a regulator publishes a people number.

Do not treat GitHub OAuth revocation as proof those connections were abused. It was a precaution on the status page.

Frequently asked questions

How many people were affected?

Unpublished. 91,000 customers is not this census.

Were full card numbers taken?

The Reddit letter copy says no full PAN or CVV. Cardholder name, expiry and last four only.

Should I reset 2FA?

Yes. Recovery codes and 2FA settings are on the longer letter list, and other letters already asked for a reset.

When was it found?

11 November 2026 at 12:13 UTC, after access on 9 and 10 November.

Were Actor datasets copied?

Some letters said Apify found no indication stored account data on the platform was accessed. Other letters listed personal and billing fields. Follow the email you received.

Sourcing note: Apify status page, SecurityWeek customer-letter copy, BleepingComputer.

Do not download alleged Apify dumps. This catalog does not link them. A later leak-site post is still an unverified brand until Apify names it.

Compare later mail with apify.com. Apify will not ask for a card CVV or a one-time code through a new website to finish this investigation.

Do not merge this row with the Fireworks October incident. They are separate catalog files even when they share a season or a vendor class.

If you did not receive a letter, you may still be in an unpublished state filing. Ask Apify in writing whether your identifier sits in the reached file.

US residents can place a free credit freeze at Equifax, Experian and TransUnion. Use the local freeze or watch process named in the notice if you live elsewhere.

Keep the paper letter if one arrives. A later amendment can add fields or a higher census. This catalog will move recordsAffected only when a named official source publishes a new figure. Do not treat a class-action advertisement as a census.