Short answer

Apify says an unauthorized third party gained access to parts of its internal systems on 9 and 10 November 2026. It detected the intrusion on 11 November and confirmed on 12 November that some customers' data was accessed. Impacted customers had API tokens and proxy passwords rotated and were told to reset 2FA.

If you think your details were included, start with our checklist on what to do after a data breach.

Key facts

Key facts about the Apify incident
OrganizationApify
Incident typeData breach
StatusConfirmed by the organization
SectorSoftware (web scraping and automation)
CountryCzech Republic
Detected2026-11-11
Disclosed2026-11-12
People or records affectedNot disclosed. Apify has not said how many accounts were affected. Outlets give its customer base as 80,000 (BleepingComputer) or 91,000 (SecurityWeek).

What data was exposed

  • Apify API tokens and Apify Proxy passwords for impacted customers (rotated by Apify)
  • Two-factor authentication codes that may have been exposed
  • Per one customer notice shared online and reported by SecurityWeek: names, email addresses, IP addresses, billing details, account activity, phone numbers, salted password hashes and sign-in tokens for Google and GitHub

What happened

Apify is a Czech platform for web scraping and browser automation. It says an unauthorized third party gained access to parts of its internal systems on 9 and 10 November 2026, according to BleepingComputer. The company detected the incident the next day, cut off the attacker’s access and began an investigation.

On 12 November Apify confirmed on its status page that some customers had personal information or stored data accessed, SecurityWeek reported. SecurityWeek adds that the attacker used a compromised credential to obtain further credentials and access related accounts.

What Apify did

Apify invalidated internal credentials, rotated API tokens, reset all active sessions and changed critical internal secrets, per BleepingComputer. As a precaution it also revoked some OAuth connections to outside services, including GitHub. It says its investigation found no indication that those connections were used as an attack vector. Customers who build Actors from private GitHub repositories were told to reconnect their GitHub integrations, and Apify will email users when reconnecting is safe.

What may have been exposed

The public detail is uneven. BleepingComputer’s sample notice said impacted customers’ Apify API tokens and Apify Proxy passwords were rotated, and advised resetting 2FA because 2FA codes may have been exposed. Apify said it found no indication that account data stored on its platform was affected.

SecurityWeek lists a longer set of fields from a notice a customer shared on Reddit: names, email addresses, billing details, account activity, IP addresses, salted password hashes, 2FA recovery codes, phone numbers and authentication tokens tied to Google and GitHub sign-ins. Card data was reportedly limited to cardholder name, expiry date and last four digits. This is a customer’s copy of a notice, not an official Apify list, and notices appear to differ between customers.

What is still unknown

Apify has not said how many accounts were reached or how the first credential was compromised. The two outlets also give different figures for its customer base, 80,000 and 91,000, so neither tells you the share affected.

What to do now

If you have an Apify account, check your inbox for a notice and act on it. Rotate keys in anything that talked to the old tokens. Because the exposure involves login-related data, expect fake login prompts: our guides on phishing messages and SIM swap and account takeover scams explain how to spot them. The data breach checklist covers password and 2FA steps. For similar developer-platform incidents, see the Railway secrets exposure and the GitBook API token incident.

Scams to watch for after this breach

Criminals use breach news as cover. Expect messages that mention the incident, quote real details, or offer help.

  • Phishing emails that claim to be Apify and ask you to log in, reset 2FA or reconnect GitHub through a link.
  • Attempts to use any exposed tokens against your scripts, cloud accounts or private code repositories.
  • Targeted emails or calls that use your billing or contact details, if those were in your notice.

What to do if you are affected

  1. 01Read the notice Apify sent you, if any. Apify says customers who have not been notified have not been identified as affected so far.
  2. 02Reset two-factor authentication in the Apify Console if your notice or Apify's guidance says to.
  3. 03Update scripts, pipelines and integrations that use the old API tokens or proxy passwords.
  4. 04If you build Actors from private GitHub repositories, reconnect your GitHub integration as Apify advised, and review which apps can access your Google and GitHub accounts.
  5. 05Change any password you reused on other sites, and be careful with emails that ask you to click a login link.

Frequently asked questions

When did the Apify breach happen?

Apify says an unauthorized third party gained access to parts of its internal systems on 9 and 10 November 2026. It detected the incident the day after, at 12:13 UTC on 11 November, according to BleepingComputer.

How did the attacker get in?

SecurityWeek reports the attacker used a compromised credential to obtain additional credentials and reach related accounts. Apify has not said how the first credential was compromised.

Were passwords stolen?

Apify said passwords were safe, according to the notice BleepingComputer saw. A customer notice quoted by SecurityWeek lists salted password hashes, but that list is not an official Apify statement. Notices differ between customers, so rely on the one you received.

How many customers are affected?

Apify has not said. It reports that customers who have not been contacted have not been identified as affected so far, and its investigation continues.

Sources

  1. Apify rotates API tokens, prompts 2FA resets after breach, BleepingComputer, 2026-11-12
  2. Apify Confirms Customer Data Accessed in Cyberattack, SecurityWeek, 2026-11-13

This post summarises public reporting as of 2026-11-19. Details of live incidents change; we update posts when the organization or regulators publish new facts. Spot an error? See our editorial and corrections policy.