•6 min read

Apify Confirms Security Breach: Developers Urged to Rotate API Tokens and Reset 2FA

Apify, a popular web scraping and automation platform, has disclosed a security breach, prompting users to rotate API tokens and reset 2FA for enhanced security. Learn the details and best practices.

Apify Confirms Security Breach: Developers Urged to Rotate API Tokens and Reset 2FA

In a critical update for the developer community, Apify, a widely-used web scraping and browser automation platform, has confirmed a security incident involving unauthorized access to its internal systems. The breach, detected on November 10, 2026, has led to immediate and decisive actions from Apify, including the rotation of API tokens and a strong recommendation for users to reset their two-factor authentication (2FA) settings. This news underscores the persistent and evolving cybersecurity challenges faced by platforms handling sensitive developer credentials and data, highlighting the importance of robust security practices for both service providers and their users.

Apify, which serves a substantial user base of 80,000 customers, including major corporations, is a vital tool for many developers and businesses. The incident, which occurred between November 9 and 10, 2026, prompted a rapid response to mitigate potential risks. While the company has stated there's no indication that stored account data was compromised, the rotation of API tokens and proxy passwords, alongside the advisory for 2FA resets, points to the potential exposure of critical access credentials. This blog post delves into the specifics of the Apify security breach, its implications for developers, and essential steps to safeguard your accounts and projects.

1. The Incident: Unauthorized Access and Rapid Response

Apify identified unauthorized access to parts of its internal systems on November 10, 2026, following an intrusion that occurred between November 9 and 10. Upon discovery, the company initiated an immediate and comprehensive incident response plan. This swift action involved invalidating critical internal credentials, rotating all customer API tokens and Apify Proxy passwords, and resetting all active user sessions to sever the attacker's access.

Furthermore, out of an abundance of caution, Apify revoked OAuth connections to external integrations, including popular developer platforms like GitHub. This measure aims to prevent any potential misuse of compromised OAuth tokens that could grant access to linked third-party services. The company has been actively notifying affected users via email, providing specific instructions on the necessary security actions. The transparency and speed of Apify's response are crucial in managing such security incidents, allowing developers to take timely preventative measures. While investigations are ongoing, Apify has communicated that there is currently no indication that account data stored on its platform was affected by the incident.

2. Key Actions for Developers: Secure Your Apify Accounts

For developers utilizing Apify's web scraping and browser automation services, immediate action is paramount to ensure the security of their projects and data. The primary directives from Apify are clear: rotate your API tokens and reset your two-factor authentication (2FA) settings. Although Apify automatically rotated API tokens and proxy passwords, manually verifying and generating new ones adds an extra layer of security.

Here’s a breakdown of recommended steps:

  • API Token Rotation: Even though Apify performed an automatic rotation, it is best practice to log into your Apify Console and generate new API tokens. Update all your applications, scripts, and CI/CD pipelines that use these tokens with the newly generated ones.
  • 2FA Reset: Apify has advised users to reset their two-factor authentication through the Apify Console. This is a critical step because 2FA codes may have been exposed during the intrusion. Resetting ensures that even if old 2FA codes were compromised, they are no longer valid.
  • Review OAuth Connections: As Apify revoked OAuth connections to external services like GitHub, users will need to re-authenticate these integrations. When reconnecting, ensure you understand and approve the permissions requested by Apify.
  • Monitor for Suspicious Activity: Keep a close eye on your Apify account activity logs, as well as any linked external accounts (e.g., GitHub, cloud providers) for any unusual or unauthorized actions.
  • Update Dependencies: While not directly related to this breach, regularly updating all project dependencies is a general security best practice that can prevent vulnerabilities from being exploited.

Adhering to these steps will significantly reduce the risk associated with the breach and help maintain the integrity of your development workflow.

3. Broader Implications for API Security and Developer Trust

The Apify security incident serves as a stark reminder of the inherent risks in the interconnected world of software development, particularly concerning API platforms. Developers often integrate third-party APIs into their applications, granting these services varying levels of access to their systems and data. When a platform like Apify, which handles sensitive automation tasks and potentially access to other web services, experiences a breach, the ripple effect can be significant across its extensive customer base.

This incident highlights several critical aspects of API security:

  • Supply Chain Security: The security posture of any third-party tool or API integrated into a development workflow becomes a part of the overall software supply chain security. A compromise in one link can expose the entire chain.
  • Importance of Least Privilege: Developers should always strive to grant third-party services and APIs only the minimum necessary permissions to perform their intended functions.
  • Robust Authentication Mechanisms: The emphasis on 2FA and its potential exposure underscores the need for strong, multi-factor authentication methods that are regularly reviewed and updated.
  • Incident Response and Transparency: Apify's rapid response and transparent communication are crucial for maintaining developer trust during a security event. Clear guidance on remedial actions empowers users to protect themselves effectively.
  • Continuous Monitoring: Both service providers and developers must implement continuous monitoring for suspicious activities and potential vulnerabilities.

As the digital landscape evolves, so do the methods of cyber attackers. This event reinforces the need for developers to remain vigilant, adopt proactive security measures, and critically evaluate the security practices of the services they rely on.

Comparison Overview

Security AspectApify's Response (Post-Breach)General Best Practices for Developers
API TokensAutomatically rotated; users advised to generate new ones.Regularly rotate API keys; use environment variables, not hardcoded values; implement least privilege.
2FA (Two-Factor Authentication)Users advised to reset 2FA codes via console.Always enable 2FA; use strong authentication apps (e.g., TOTP) over SMS where possible; reset if suspicious activity occurs.
OAuth ConnectionsRevoked to external services (e.g., GitHub); users need to re-authenticate.Review and revoke unused OAuth grants; understand requested permissions before granting access; monitor linked accounts.
Account Data CompromiseNo indication of stored account data being affected.Implement strong, unique passwords; monitor account activity logs; enable alerts for unusual logins.
Incident CommunicationPrompt email notifications and public updates.Stay informed through official channels; follow security advisories; report suspicious activity immediately.

Frequently Asked Questions (FAQ)

Q: What exactly happened with Apify?

Apify experienced unauthorized access to parts of its internal systems between November 9 and 10, 2026. The company detected the breach on November 10 and immediately took steps to mitigate the impact, including invalidating internal credentials and rotating API tokens.

Q: Are my Apify API tokens and proxy passwords safe?

Apify automatically rotated all customer API tokens and Apify Proxy passwords as part of their incident response. Users are strongly advised to log into their Apify Console and generate new tokens and update them across all their integrations as an extra precaution.

Q: Do I need to reset my 2FA for Apify?

Yes, Apify has specifically advised users to reset their two-factor authentication (2FA) through the Apify Console. This is because 2FA codes may have been exposed during the intrusion, and resetting them ensures their invalidation.

Q: Was any of my stored account data compromised?

Apify has stated that, as of their latest updates, there is no indication that account data stored on their platform was affected by the incident. However, investigations are ongoing.

Q: What should I do if I use Apify and linked it to GitHub or other services?

Apify revoked OAuth connections to external integrations like GitHub. You will need to re-authenticate these connections. When doing so, always review the permissions being requested to ensure they align with your expectations.

Try Our Developer Utilities

Simplify your engineering workflows with our free browser-native tools: