Apify Security Incident
cynicalpeace
94 points
10 comments
November 13, 2026
Related Discussions
Found 5 related stories in 158.3ms across 12,728 title embeddings via pgvector HNSW
- Apify Security Incident choult · 11 pts · November 12, 2026 · 100% similar
- Linode Security Incident lacoolj · 176 pts · October 30, 2026 · 57% similar
- Security incident disclosure – July 2026 fdb · 24 pts · July 19, 2026 · 56% similar
- Incident with Actions hising · 97 pts · October 05, 2026 · 56% similar
- Incident with Github.com kevcampb · 698 pts · August 17, 2026 · 54% similar
Discussion Highlights (4 comments)
tptacek
Duplicate, also editorialized title. https://news.ycombinator.com/item?id=50469719
radial_symmetry
"- API tokens are now stored only as hashes, which limits the impact of any similar incident." WTF were they not already?
gnabgib
Bleeping Computer's coverage is maybe a bit more detailed Apify rotates API tokens, prompts 2FA resets after breach ( https://www.bleepingcomputer.com/news/security/apify-rotates... )
TZubiri
I feel like an asshole posting a criticism of the whole dependency category every time they get a critical vuln. But if you are building an API service, you don't need an API Management dependency. And it's an additional attack vector. You (as in an engineer or as a company that provides an API service) need to do the actual undelegable job of building an API, just do the work, do the HTTP server, do the rate limiting, do the OAuth integration. Verdict: Time to uninstall software in the category of API Management. That is, if you want to be the very best. If you want to be mediocre, sure use some middleware that provides API, slap some API into your software so that customers that ask for API have API. Otherwise, engineer an external Application Programming Interface into your systems.