Skip to content
FrameFrame home
PlatformBreach CheckFrame agentExtensionPrivacyBusinessPricing
Sign inSample report
FrameFrame home

Your digital life. Back in your hands.

100% Canadian-owned · Support: support@frameprivacy.com

Product

  • Platform
  • Sample report
  • Breach Check
  • Frame agent
  • Extension
  • Mobile app
  • Pricing
  • Frame Business
  • Changelog

Resources

  • Blog
  • Help centre
  • Free leak test
  • Status
  • Data-broker catalog
  • RSS feed

Company

  • About
  • Our privacy promise
  • Contact
  • Press and brand

Legal

  • Legal hub
  • Privacy Policy
  • Terms
  • Security
  • Cookies
  • Accessibility

© 2026 Frame Labs Inc. All rights reserved.

en Englishfr Français
Your Privacy ChoicesSystem status

All posts

Breach · 4 min read

Apify says an intruder reached some customers’ accounts and stored data

The web scraping company says someone used a stolen credential on November 9 and 10 to open related accounts. It has emailed the customers whose data was accessed.

BBy Brody · FramePublished November 13, 2026
A cloud-warning icon in a blue circle inside dotted rings, with small key and database icons around it, on a dark background.

If you use Apify to collect data from websites or to run automated jobs, check whether the company has emailed you. On November 12, 2026, Apify said some customers had personal information or stored data accessed after an intruder got into internal systems and customer accounts. People who have not received that email have not been identified as affected so far. The investigation is still open.

What happened

Apify, based in the Czech Republic, runs a cloud platform for web scraping and automation. The company says it has 91,000 customers.

On its status page, Apify says an unauthorized party got into parts of its internal systems on November 9 and 10, 2026. Staff detected the activity on November 11 at 12:13 UTC, cut off the access, and started an investigation. A later update says the intruder used a compromised credential to obtain more account credentials and then opened related Apify accounts. Apify says that path is closed, and that it has seen no further activity from the attacker since November 11.

On November 12, Apify said it had emailed customers whose personal information or stored data was accessed. The email, not the public status page, is where those customers were told what of theirs was involved. SecurityWeek reported that one customer posted a notification on Reddit listing names, email addresses, billing details, account activity and IP addresses, plus salted password hashes, two-factor recovery codes, phone numbers, and tokens tied to Google and GitHub sign-in. The same notification, as SecurityWeek describes it, said card data was limited to the cardholder name, the expiry date and the last four digits. Full card numbers and security codes were not exposed. Apify has not published that list itself, and it has not said how many accounts were reached.

What Apify has done since

Through November 13, Apify said it had rotated critical internal secrets, revoked some OAuth connections to outside services including GitHub, and added monitoring. It said the investigation had not found that those OAuth connections were the way in. Customers who build Apify Actors from private GitHub repositories were told to reconnect GitHub: open an Actor built from GitHub, choose “Change provider,” then GitHub, and authorize once per account and per organization.

On November 13 the company also said API tokens are now stored only as hashes, that it had added network restrictions between internal services, and that it was reviewing the whole stack. It asked every user to restrict storage access: in the console, Settings, then General resource access, set to Restricted. While that setting is open, Apify says, anyone who knows a storage ID can read that storage.

A further update on November 16 said Apify believes it has found the most likely root cause, closed the vulnerability it thinks allowed the first access, and hardened the path the attacker used. It said it had found no evidence of further unauthorized access. API tokens are now shown only once, when you create them. The company said it would publish the next update and a preliminary incident report by November 20, and that it had notified the relevant authorities.

What you can do

  1. If Apify emailed you, follow that message. It is the notice for your account. If you have not received one, Apify says you have not been identified as affected so far. That can still change.
  2. Change your Apify password if you reuse it anywhere else, and turn on two-step sign-in if it is not already on. If your notice mentioned recovery codes, generate new ones and retire the old set.
  3. Reconnect GitHub if you build Actors from private repositories, using the steps above, and reconnect any other integration Apify prompts you about.
  4. Restrict storage access as Apify asked, so a storage ID alone is not enough to read the data.
  5. Treat a new API token as something you will see only once. Store it somewhere you already trust. If you lose it, create another and delete the lost one.
  6. Watch for phishing. Apify says it will never ask for your password, two-factor codes or payment details.

How Frame helps

This incident may include email addresses, but Apify has not published a list, and Frame does not have a copy of it. If a catalog later adds this breach, add it to a verified email in Frame and Frame shows what it exposed, gives you a short checklist and counts it in your exposure report. Frame can also look up your verified emails in Have I Been Pwned’s breach database. Frame never collects or stores the leaked records themselves.

Related coverage

  • Stolen GitHub accounts pushed a secret stealer into thousands of repositories: another November case where a GitHub connection was the thing worth locking down again.
  • How scammers use leaked data to make phishing personal, and how to spot it: why a message that knows your account still may not be Apify.

Sources

  • Apify, status incident updates, November 11 to 16, 2026
  • SecurityWeek, Apify Confirms Customer Data Accessed in Cyberattack, November 13, 2026
  • Breaches
  • Guides
More in Breaches

More stories

  • BreachColes is investigating a cyber security incident and says it has found no data taken so farNovember 17, 2026 · 4 min read
  • BreachJINS says a vendor breach may include up to 18.29 million member accountsNovember 17, 2026 · 4 min read
  • BreachLegoland Korea says a reservation vendor may have exposed annual-pass detailsNovember 17, 2026 · 4 min read

New posts, by email.

About once a month. Plain-language privacy notes, nothing else. I never share your address.

Sent by Frame · privacy@frameprivacy.com · Privacy Policy

See what’s exposed about you.

Frame is in private beta. See what it finds, and how it helps you take it down, in a sample report built from made-up data.

See a sample exposure report
FrameFrame home
PlatformBreach CheckFrame agentExtensionPrivacyBusinessPricing
Sign inSample report

See what’s exposed about you.

Frame is in private beta. See what it finds, and how it helps you take it down, in a sample report built from made-up data.

See a sample exposure report