Apify breach exposes account credentials and customer data, prompting token rotations
Breach & Incident Intelligence · 8 sources · Updated 9h ago · First seen Nov 12, 2026

Apify disclosed that an unauthorized third party used a compromised credential to obtain account credentials and access related customer accounts on November 9–10, 2026. The company detected the intrusion on November 11 at 12:13 UTC, cut off access, and said it had detected no further attacker activity since that day. Apify has notified customers whose personal information or stored data was accessed; its investigation remains ongoing. Customer notifications described differing impacts: one reported no indication of stored-data exposure, while another warned that two-factor authentication codes might have been exposed but said passwords remained safe.
Apify invalidated internal credentials, rotated critical internal secrets, reset all active sessions, and notified affected customers that their Apify API tokens and Apify Proxy passwords had been rotated. It also revoked some external OAuth connections as a precaution, although investigators have not found those connections to be an attack vector, and notified relevant authorities. Affected customers should follow their individual notification instructions, including resetting 2FA where advised, and update integrations using rotated credentials. Customers building Actors from private GitHub repositories must reconnect GitHub, and other integrations may require reauthorization. Apify said customers without a notification had not been identified as affected so far and promised further updates and a postmortem.


