← Back to BLACKWIRE EMBER BUREAU CYBERSECURITY ALERT Screenshot of Apify status page showing security incident updates

Apify’s public status page listed the breach and ongoing remediation steps on 13 November 2026.

APIFY DATA BREACH EXPOSES USER CREDENTIALS, COMPANY RESPONDS

*Apify confirmed a breach on Nov 9‑10 2026 that exposed account credentials and stored data. The company shut down the attack vector, notified affected users, and is overhauling its security stack.*

By EMBER Bureau - BLACKWIRE  |  November 13, 2026, 19:01 CET  |  Apify breach, data security, API tokens, OAuth, cyber attack

Apify, a cloud automation platform, confirmed a security incident on 9‑10 November 2026 where an unauthorized third party accessed account credentials using a compromised credential. The breach was detected on 11 November at 12:13 UTC, prompting immediate shutdown of the attack path. The incident affected API, Actors, and General services, exposing stored user data and personal information.

Since detection, Apify has notified affected customers via email, revoked certain OAuth connections, rotated internal secrets, and launched a full security review. The company promises a post‑mortem within a week and further updates within 72 hours. Users are urged to restrict storage access and stay vigilant against phishing attempts.

How did the attackers breach Apify’s systems?

On 9 and 10 November 2026 an unauthorized third party used a compromised credential to obtain a number of account credentials and accessed related Apify accounts. The intrusion was detected on 11 November at 12:13 UTC, at which point Apify cut off the access path and halted further activity. Internal logs show no attacker activity after 11 November. The compromised credential allowed the intruder to move laterally within Apify’s internal services, reaching API, Actors, and General endpoints. Apify closed the access route and began a forensic investigation while notifying relevant authorities.

What data was potentially exposed?

The breach gave the attacker access to API tokens, account credentials, and any storage that was left open. Apify warned that while a storage ID is public, anyone who knows it can read the storage, meaning personal information could be exposed. The company has emailed customers whose personal information or stored data was accessed, confirming that the compromised data includes user‑provided content and authentication details. Users who have not received an email are, so far, not identified as affected.

Apify will never ask for your password, 2FA codes, or payment details.

What remediation steps has Apify taken?

Apify now stores API tokens only as hashes, limiting the impact of any future token leak. It added network restrictions between internal services and strengthened authentication on internal systems. As a precaution, the firm revoked some OAuth connections, rotated various critical internal secrets, and revoked OAuth links to external integrations, including GitHub. Dozens of additional security activities are underway, including a comprehensive review of the entire stack, continuous log analysis, and heightened monitoring for suspicious activity. A post‑mortem will be published within a week.

What should users do now?

Apify advises all users to restrict access to their storages: in Console go to Settings → General resource access and set it to Restricted. Users should also be cautious of phishing; Apify will never ask for passwords, 2FA codes, or payment details. Those building Actors from private GitHub repos must reconnect GitHub via the “Change provider” flow. Any prompted reconnections for other integrations should follow the separate email notifications. Users with questions should contact Support or reply to the breach notification email.

Frequently asked questions

When did the Apify breach occur?

The unauthorized access happened on 9 and 10 November 2026 and was detected on 11 November at 12:13 UTC.

What data did the attackers access?

Attackers accessed API tokens, account credentials, and any storage left open, potentially exposing personal information.

How is Apify protecting users after the breach?

Apify now stores API tokens as hashes, added network restrictions, strengthened authentication, revoked OAuth connections, rotated internal secrets, and is conducting a comprehensive security review.

The Apify breach highlights the fragility of credential‑based access in cloud platforms and the cascading risk to downstream services. While the company’s rapid containment and transparent communication are commendable, the episode underscores the need for continuous credential hygiene and zero‑trust networking. As Apify tightens its defenses, users must adopt the recommended safeguards to prevent future exposure. The coming post‑mortem will reveal whether deeper systemic flaws remain.

Sources: https://status.apify.com/incidents/sxd1dj5j6749

More coverageCybersecurity breaches and exploits