SOCLYDE logo
Current languageEN
Cybersecurity newscybersecurityapify

Apify users need to review tokens and integrations

Apify confirms access to customer accounts. Review account notices, API tokens, two-factor authentication and GitHub integrations before restarting jobs.

Published on

By Soclyde

Two colleagues review an integration in an online retail studio

In summary

  • Apify is investigating unauthorized access on November 9 and 10.
  • Token and two-factor authentication instructions depend on the account notice.
  • Reconnect GitHub through the official console and test dependent jobs.

Explore next

Soclyde resources

Article contents

Apify has confirmed an intrusion on November 9 and 10, 2026, detected on November 11. A compromised credential led to access to customer accounts. Small businesses using its automation platform should locate their provider notification before restoring integrations.

An investigation with an evolving scope

Apify’s official November 12 update separates access to its internal systems from access to customer accounts. The company says it closed the access path and contacted identified customers. An account without an email has not been identified as affected so far; this remains an interim finding.

Keep the date and contents of your own notice. It is the reference for distinguishing actions required for your account from precautions announced across the platform.

Follow the notice for your account

BleepingComputer examined notifications describing API token and Proxy password rotation, and a two-factor authentication reset instruction for some recipients. Security.NL separately links to a customer notice and highlights that the affected account count is unknown. This does not establish identical exposure for every customer.

List the integrations your business actually runs through Apify, such as product-catalog updates or price collection. Do not paste an old token into a support request while documenting those dependencies.

Reconnect through the official console

Open Apify using your usual bookmark. Follow the steps in your notice, including any requested two-factor authentication reset. Verify messages asking you to return a token by email with official support before acting.

Apify provides instructions for reconnecting GitHub for Actors built from private repositories. It describes the OAuth revocation as precautionary rather than evidence of a GitHub vulnerability.

Test automation before full recovery

We recommend a controlled restart: identify the owner of each automation, update required secrets in its execution environment, and run a limited test. Then confirm scheduled jobs and connected services work with the replacement access.

Record the changes without recording the secret values. A successful job does not prove the investigation into customer data is complete.

The connection with Soclyde

Apify’s incident highlights the need to track administrative logins separately from integration access. Soclyde helps keep unique passwords in an encrypted vault on your devices. It does not replace Apify’s controls or automatically rotate API tokens and OAuth authorizations.

What to remember

Follow your Apify notice, review changed access and validate each automation before restarting it. Our password generator helps prepare separate passwords for the services you administer.

Frequently asked questions

Were all Apify accounts affected?

Apify says it notified customers whose information or stored data was accessed. As of November 12, accounts without a notification had not been identified as affected so far. The investigation remains ongoing.

Should I replace an Apify API token?

Follow your account-specific notification. If a token was rotated, replace it in the integrations that use it and test dependent jobs from a trusted device.

Does the OAuth revocation prove GitHub was breached?

No. Apify describes a precaution and says it has not found these connections to be an attack vector. Reconnect through the official console.

References

Sources and references

Need advice?

Design your password strategy with Soclyde

Schedule a dedicated walkthrough with the team to see how local-first security adapts to your stack.

Talk with us

Keep reading