Skip to content

Apify breach exposed customer data and GitHub OAuth tokens

A compromised credential let an attacker reach other Apify accounts on 9 and 10 November, exposing personal data and sign-in tokens before Apify cut off access.

Source: Apify Status

Apify disclosed a security incident in which an attacker used a compromised credential to obtain further account credentials and reach other Apify accounts on 9 and 10 November. Apify’s monitoring caught the activity and cut off the attacker at 12:13 UTC on 11 November, and it says it has seen no further activity since.

Apify confirmed personal information or stored data was accessed for some customers, and is notifying them individually by email with details specific to their account. Independent reporting on those notifications lists names, email addresses, billing details, salted password hashes, 2FA recovery codes and authentication tokens tied to Google and GitHub sign-ins among the exposed data, though Apify says full card numbers were not exposed. In response it revoked OAuth connections to third-party integrations, rotated its internal secrets, switched to storing API tokens only as hashes, and tightened network and authentication controls.

Why it matters: if you run Apify actors or integrate Apify with GitHub or Google, treat those connections as compromised until you reconnect them, restrict storage access under Settings > General resource access in the Apify console, and rotate any Apify API tokens stored in other services.

The caveat: Apify hasn’t said how many accounts were affected, and a full post-mortem hasn’t been published yet, so anyone not directly emailed is relying on the status page for now.

Share

Related reading

More from The Wire

All briefs