Apify Breach: One Compromised Credential Led to Customer Data, With 2FA Recovery Codes and GitHub and Google Sign-In Tokens Reportedly Exposed

High · 2026-11-14 · By H.A

Apify Breach: One Compromised Credential Led to Customer Data, With 2FA Recovery Codes and GitHub and Google Sign-In Tokens Reportedly Exposed

The Czech web-scraping platform, which says it has about 91,000 customers, confirmed an attacker accessed internal systems and customer data on 9–10 November 2026 and has rotated secrets and revoked some OAuth connections.

Overview

Apify, a Czech web-scraping and automation platform that says it has about 91,000 customers, has confirmed that an attacker accessed customer data and internal systems. The intrusion took place on 9–10 November 2026 and was found on 11 November. It started with one compromised credential that the attacker used to collect more credentials and reach connected accounts.

Apify has not said how many accounts were affected. A customer notice shared publicly, which has not been independently verified, lists data that includes 2FA recovery codes and authentication tokens for Google and GitHub sign-ins. That would make this more than a typical contact-data leak.

The Incident

According to Apify's status page and statements:

The customer notice that circulated says exposed data may include:

Timeline

All dates are Mauritius time (UTC+4). Apify has not published exact hours.

Tradecraft

The publicly known pattern is credential chaining: one valid secret is used to find others (in config, CI variables, vaults or internal tools) until the attacker reaches systems holding customer data. How the first credential was obtained has not been disclosed. Infostealer logs, phishing and leaked secrets in code are the usual sources for this kind of entry.

The data reportedly taken makes follow-on abuse possible:

Vendor Response

Apify says it has:

Apify says it has found no evidence that the OAuth connections were the attack vector.

Detection

For Apify customers and security teams:

# GitHub CLI: list recent org audit-log events tied to OAuth/integration access (requires org admin)
gh api "/orgs/YOUR_ORG/audit-log?phrase=action:oauth_access+created:>=2026-11-09" --paginate | jq '.[] | {action, actor, created_at}'

Recommended Actions

Analyst Assessment

Developer and automation platforms are attractive targets because they hold other people's secrets. A scraping platform's customers routinely store credentials for the sites and APIs they automate. That makes the downstream impact potentially larger than the 91,000 headline number suggests, and it depends heavily on what each customer kept in their Actors. The reported exposure of 2FA recovery codes is the detail to act on fastest. Apify's quick detection, within roughly a day, limited the attacker's time inside. Customers should still assume any secret stored on the platform before 11 November is burned and rotate it.

REEF SENTINEL