SecOraLens
CriticalBreach

Apify rotates API tokens, prompts 2FA resets after breach

BleepingComputer·Source published ·1 min read

What happened?

Apify has rotated critical internal secrets and revoked some third-party OAuth connections after detecting unauthorized access to its internal systems. [...]

Key details

  • Unauthorized access to Apify internal systems occurred on November 9 and 10, 2026.
  • Customer API tokens and Apify Proxy passwords have been rotated as a precaution.
  • Apify advises affected users to reset two-factor authentication via the Apify Console.
  • Apify states no indication that stored account data was affected by the incident.
  • Apify revoked OAuth connections to external integrations including GitHub out of caution.

What is affected?

  • Apify platform customers using API tokens and Proxy passwords.
  • OAuth connections to external integrations such as GitHub.

How do I fix or mitigate it?

  1. Rotate customer API tokens and Apify Proxy passwords.
  2. Reset two-factor authentication through the Apify Console.
  3. Revoke OAuth connections to external integrations including GitHub.

Summarised by SecOraLens from BleepingComputer. Always read the original source before acting. How SecOraLens verifies advisories.

What to do next

For CISOs and SOC leads

Brief your board. Brief your team.

Executive risk briefs for governance, technical kill-chains for the SOC — delivered as advisories publish. Critical alerts within 1 hour. No spam, unsubscribe anytime.