Apify, a Czech-based web scraping and automation platform serving approximately 91,000 customers, has confirmed that its internal systems were breached in a cyberattack earlier this month. The company identified unauthorized access to its infrastructure on November 11, 2026, and subsequently determined that the intrusion occurred over the preceding two days, November 9 and 10. Upon discovery, Apify blocked the attacker’s access and initiated a formal investigation into the scope of the incident.
According to the company, the breach originated from a single compromised credential. The intruder utilized this initial access to escalate privileges, obtaining additional credentials that allowed them to move laterally and compromise various customer accounts. While Apify has not disclosed the total number of accounts affected, it has confirmed that it is actively notifying those whose personal information or stored data was accessed. Customers who have not received a direct communication from the company are currently not considered to be among the impacted group, though the investigation remains ongoing.
Reports from affected users indicate that the exposed data is extensive. The compromised information includes names, email addresses, billing details, account activity logs, and IP addresses. Furthermore, the breach involved sensitive security credentials, including salted password hashes, two-factor authentication (2FA) recovery codes, and phone numbers. The attackers also gained access to authentication tokens linked to third-party services, specifically those used for Google and GitHub account integrations.
Regarding financial data, Apify has clarified that the exposure was limited. While the attackers accessed billing information, this was restricted to cardholder names, expiration dates, and the last four digits of payment cards. The company emphasized that full credit card numbers and security codes were not compromised during the incident.
In response to the breach, Apify has implemented several security measures to prevent further unauthorized activity. These include enhanced monitoring of its systems, the rotation of critical internal secrets, and the revocation of certain OAuth connections. Specifically, the company has instructed users who build Apify Actors from private GitHub repositories to manually reconnect their GitHub integrations to ensure security.
While the attackers gained access to OAuth tokens, Apify stated that its investigation has not uncovered evidence suggesting that these connections were utilized as an attack vector to compromise external services. The company continues to work through the aftermath of the event, focusing on system remediation and communication with its user base to mitigate the risks associated with the exposed credentials and authentication tokens.





