Protect.Computer
NEWS

Apify Breach: API Tokens Rotated, Some Users Told to Reset 2FA

· 2 min read · Got hacked
Apify Breach: API Tokens Rotated, Some Users Told to Reset 2FA

Apify, a Czech platform developers use for web scraping and browser automation, says an unauthorized third party got into parts of its internal systems on November 9 and 10. The company detected it on November 11 at 12:13 UTC, cut off the access and started an investigation. Its status page, in an update dated November 12, says the attacker “used a compromised credential to obtain a number of account credentials and accessed related Apify accounts,” that the access path is closed, and that Apify has detected no further activity from the attacker since November 11. Apify says it has notified the relevant authorities and is notifying affected users individually, and that a post-mortem will follow.

What Apify did in response, per its status page and BleepingComputer: it rotated critical internal secrets, reset all active sessions, and revoked some OAuth connections to external integrations, including GitHub, as a precaution. Apify says its investigation has not found that those connections could be used as an attack vector. BleepingComputer saw notices telling affected customers that their Apify API tokens and Apify Proxy passwords had been rotated, and another letter advising recipients to reset their two-factor authentication through the Apify Console because their 2FA codes may have been exposed, while saying their passwords remain safe.

The company’s message changed as the investigation went on. BleepingComputer says one notification reported no indication that account data stored on the platform had been affected. The latest status-page update says Apify has now notified customers whose personal information or stored data was accessed, and that details are in the email they received.

How to check if you’re affected

Affected products are Apify platform accounts and anything connected to them: API tokens, Apify Proxy passwords, 2FA setup, and OAuth integrations such as GitHub. Neither the status page nor BleepingComputer’s report gives a count of affected accounts or a list of the data involved.

  • Check your email first. Apify says to follow the instructions in any email you received from it. If you did not get one, Apify says it has not identified your account as affected so far and will contact additional customers directly if that changes.
  • Reset 2FA if told to. BleepingComputer’s sample letter tells affected customers to reset their 2FA through the Apify Console, because 2FA codes may have been exposed.
  • Reconnect integrations. For Actors built from private GitHub repositories, Apify’s steps are: open an Actor built from GitHub, choose “Change provider”, choose GitHub and authorize; this is needed once per account and per organization. Users of other revoked integrations will be prompted to reconnect via a separate email, and Apify told impacted users they would be informed by email when it is safe to reconnect.
  • Update stored credentials. If you use Apify tokens or Proxy passwords in scripts, CI jobs or scheduled tasks, check that they still work. BleepingComputer’s sample notices say Apify rotated tokens and Proxy passwords for affected customers, so we would expect anything still using an old value to fail; that expectation is our inference, not an Apify statement, and the sources do not say where to find the new values.

Sources

Related reading