Apify rotates API tokens and urges 2FA resets after breach
Original title: Apify rotates API tokens, prompts 2FA resets after breach
Access ran November 9–10 and was cut off the next day; Apify says stored account data shows no sign of impact.
Apify said an unauthorized third party accessed parts of its internal systems on November 9 and 10, 2026, and was detected the next day at 12:13 UTC. The Czech web scraping and browser automation company cut off access, invalidated internal credentials, rotated API tokens, reset active sessions, and revoked some third-party OAuth connections, including GitHub. Notices to affected customers say API tokens and Apify Proxy passwords were rotated, and that 2FA codes may have been exposed while passwords remain safe.
Unconfirmed: Apify says it found no indication stored account data was affected; 2FA exposure is described as possible.
- Apify reports about 80,000 customers, including named large enterprises and agencies.
- Impacted users will be emailed when it is safe to reconnect OAuth integrations.
- One notice said Apify found no indication that stored account data was affected.
- A separate letter tells recipients to reset 2FA in the Apify Console.
Impact: Internal systems accessed; some customer 2FA codes may have been exposed
- 1.Reset two-factor authentication through the Apify Console if notified.
- 2.Wait for Apify’s email before reconnecting revoked OAuth integrations such as GitHub.
- Vendors
- Apify
- Products
- Apify Proxy
- Victims
- Apify
- Countries
- Czech Republic
From the original article
1 min read at bleepingcomputer.com
Apify has rotated critical internal secrets and revoked some third-party OAuth connections after detecting unauthorized access to its internal systems. [...]
By Bill Toulas · bleepingcomputer.com
A short excerpt; the article and its images belong to the publisher. Summary, key facts and assessment above are AI-written from the article and can be wrong.