Incident
Published 2026-11-12
Updated 2026-11-14
Verified 2026-11-15

Apify says an unauthorised third party accessed parts of its internal systems on 9 and 10 November 2026; it revoked some OAuth connections, including GitHub, and rotated critical internal secrets

Apify, a web scraping and browser automation platform, said on its status page on 11 November 2026 (20:46 CET = 03:46 AWST 12 Nov) that on 9 and 10 November 2026 an unauthorized third party gained access to parts of Apify's internal systems, and that it detected the activity on 11 November at 12:13 UTC (20:13 AWST), cut off access and started an investigation.

Apify said that as a precaution it revoked some OAuth connections to external integrations, including GitHub. In an update on 12 November 2026 (12:08 CET = 19:08 AWST), Apify said the third party used a compromised credential to obtain a number of account credentials and accessed related Apify accounts; that this access path is closed and it has detected no further activity from the attacker since 11 November; that it rotated various critical internal secrets and notified the relevant authorities; and that it is notifying affected users individually.

According to BleepingComputer, a customer notice it saw says affected customers' Apify API tokens and Apify Proxy passwords were rotated, and another letter to affected customers advises resetting two-factor authentication because their 2FA codes may have been exposed.

UPDATE (14 Nov 2026): In a status update on 12 November 2026 (17:16 CET = 00:16 AWST 13 Nov), Apify said it has notified customers whose personal information or stored data was accessed, and that users who have not received an email have not been identified as affected so far.

In an update on 13 November (17:36 CET = 00:36 AWST 14 Nov), Apify said API tokens are now stored only as hashes, that it added network restrictions between internal services and stronger authentication on internal systems, and that it will publish a post-mortem with the root cause within a week; it recommends all users set General resource access to Restricted in Console settings. (source: Apify status page)

Product
Apify platform (web scraping and browser automation)
Versions
n/a — incident
Exploited in Australia?
unknown
Patch to
Apify users: follow the instructions in any email from Apify; if you build Actors from private GitHub repos, reconnect GitHub; reconnect other integrations if prompted (Apify status page). According to BleepingComputer, Apify's letter to affected customers advises resetting 2FA through the Apify Console.

breaches cloud identity