Apify says an attacker used a compromised credential to obtain account credentials and access related customer accounts on November 9 and 10. The web automation platform says it closed that access path and has detected no further attacker activity since November 11. Its incident notice says the investigation is ongoing and affected users are being contacted individually.

Bill Toulas reports for BleepingComputer that Apify rotated affected customers’ API tokens and proxy passwords. A separate notification seen by the publication asked some customers to reset two-factor authentication because their codes may have been exposed. Those notifications do not establish that every account was affected.

Update · November 16, 2026, 10:52 a.m. EST

Apify’s November 13 update, posted at 17:36 CET, adds a storage-access recommendation for all users. In Console, open Settings → General resource access and select Restricted. Apify says an open setting lets anyone who knows a storage ID read that storage. Review any intended sharing or integrations when changing access.

This is a newly explicit defensive step, not evidence that every open storage was accessed during the incident. Apify also says it now stores API tokens only as hashes. It reports adding network restrictions between internal services and stronger internal authentication while continuing log analysis and a broader security review.

Those changes reduce future exposure; they do not revoke credentials already copied or reverse earlier data access. Continue following the account-specific rotation and integration notices described below. The latest reviewed update still describes an ongoing investigation and promises a later postmortem.

Update · November 12, 2026, 5:44 p.m. EST

Apify’s latest notice, posted at 17:16 CET, says it has notified customers whose personal information or stored data was accessed. If a customer has not received an email, Apify says it has not identified that account as affected so far. The investigation continues, and it will contact additional customers if that changes.

Check the account and its integrations

Follow any account-specific notice through the Apify console reached independently. Check automations that rely on rotated tokens or proxy passwords, and replace invalid credentials where needed. Treat unexpected authentication prompts or incident-themed messages cautiously.

Apify also revoked some external OAuth connections as a precaution. The company says its investigation has not found that those connections were an attack path. Users building Actors from private GitHub repositories can reconnect GitHub using the steps in its incident notice; users of other integrations should follow their separate notification.

Caveat: Apify has not yet published a complete account of the exposure or a postmortem. The company’s statements and the reported customer notices describe an active investigation, not a final scope.