---
title: Apify confirms intruder used a compromised credential to reach internal systems and customer accounts on Nov 9-10; some customers' personal data or stored data accessed | ctxsec
url: https://ctxsec.com/items/apify-breach-compromised-credential-customer-accounts-2fa-recovery-codes-oauth-revoked-nov-9-10
description: "The web scraping and automation platform says an unauthorized third party got into parts of its internal systems on Nov 9 and 10, used a compromised credential to obtain more account credentials and accessed related Apify accounts. It detected the activity on Nov 11 at 12:13 UTC, cut off access, rotated critical internal secrets, revoked some OAuth connections (including GitHub) as a precaution, notified authorities, and has emailed customers whose personal information or stored data was accessed; customers who got no email have not been identified as affected so far. A notification seen by SecurityWeek lists names, emails, billing details, IP addresses, salted password hashes, 2FA recovery codes and phone numbers, and Google/GitHub sign-in tokens; BleepingComputer says affected customers' API tokens and Apify Proxy passwords were rotated."
status: "official (Apify status page incident updates, Nov 11-12, 2026); exposed data types per a customer notification reported by SecurityWeek and BleepingComputer"
published: 2026-11-13
---

> The web scraping and automation platform says an unauthorized third party got into parts of its internal systems on Nov 9 and 10, used a compromised credential to obtain more account credentials and accessed related Apify accounts. It detected the activity on Nov 11 at 12:13 UTC, cut off access, rotated critical internal secrets, revoked some OAuth connections (including GitHub) as a precaution, notified authorities, and has emailed customers whose personal information or stored data was accessed; customers who got no email have not been identified as affected so far. A notification seen by SecurityWeek lists names, emails, billing details, IP addresses, salted password hashes, 2FA recovery codes and phone numbers, and Google/GitHub sign-in tokens; BleepingComputer says affected customers' API tokens and Apify Proxy passwords were rotated.

[← Cybersecurity News](/news) · [markdown](/items/apify-breach-compromised-credential-customer-accounts-2fa-recovery-codes-oauth-revoked-nov-9-10.md)

official (Apify status page incident updates, Nov 11-12, 2026); exposed data types per a customer notification reported by SecurityWeek and BleepingComputer

2026-11-13 11:45 AM ET

### Apify confirms intruder used a compromised credential to reach internal systems and customer accounts on Nov 9-10; some customers' personal data or stored data accessed

- **If you use Apify:** follow the instructions in any notification email; reset 2FA in the Apify Console if told to; reconnect GitHub for Actors built from private repos (Actor, Change provider, GitHub, authorize per account and organization) and reconnect other integrations when prompted.
- **Downstream:** update any pipelines that used rotated Apify API tokens or Proxy passwords, and review the third-party accounts your scrapers and Actors log into, since stored data may have been accessed.
- **Still open:** Apify hasn't said how many accounts were affected or how the first credential was obtained; it promises a post-mortem.

Sources: [Apify Status: Security incident (updates Nov 11-12, 2026)](https://status.apify.com/) · [SecurityWeek: Apify Confirms Customer Data Accessed in Cyberattack (Nov 13, 2026)](https://www.securityweek.com/apify-confirms-customer-data-accessed-in-cyberattack/) · [BleepingComputer: Apify rotates API tokens, prompts 2FA resets after breach](https://www.bleepingcomputer.com/news/security/apify-rotates-api-tokens-prompts-2fa-resets-after-breach/)
