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) · SecurityWeek: Apify Confirms Customer Data Accessed in Cyberattack (Nov 13, 2026) · BleepingComputer: Apify rotates API tokens, prompts 2FA resets after breach