Apify 安全事件
Apify Security Incident

原始链接: https://status.apify.com/incidents/sxd1dj5j6749

Apify 正在调查一起事件:未经授权的第三方于 11 月 9 日至 10 日使用被泄露的凭证,以获取账户凭证并访问 Apify 账户。访问路径已关闭,自 11 月 11 日起未检测到进一步攻击者活动,受影响用户正在被单独通知。作为预防措施,Apify 撤销了一些 OAuth 连接并轮换了关键内部密钥,尽管被撤销的连接未被发现为攻击向量。修复工作正在进行中,有关部门已收到通知。用户应遵循邮件中的说明,如需要重新连接 GitHub 以使用私有仓库 Actor,并在提示时重新连接集成。下次更新预计在 6 小时内发布,随后将发布事后分析。

Hacker News 最新 | 过去 | 评论 | 提问 | 展示 | 招聘 | 提交 登录 Apify 安全事件 ( apify.com ) 8 分 由 choult 40 分钟前 | 隐藏 | 过去 | 收藏 | 讨论 帮助 指南 | 常见问题 | 列表 | API | 安全 | 法律 | 申请加入 YC | 联系 搜索:
相关文章

原文
Update: Our investigation is ongoing.

On 9 and 10 November, an unauthorized third party used a compromised credential to obtain a number of account credentials and accessed related Apify accounts. This access path is closed, and we have detected no further activity from the attacker since 11 November.

We are notifying affected users individually. Do not hesitate to reach out to us with questions.

We have:
- As a precaution, revoked some OAuth connections to external integrations. Our investigation has not found that these connections could be used as an attack vector.
- As a precaution, rotated various critical internal secrets.
- We continue with dozens of additional activities, about which we will share information in later updates and a post-mortem.
- We notified the relevant authorities.

For you:
- If you got an email from us, follow its instructions.
- If you build Actors from private GitHub repos, reconnect GitHub: open an Actor built from GitHub → "Change provider" → GitHub → authorize (once per account and per organization).
- If prompted, reconnect your integrations.

Next update within 6 hours, and a postmortem follows the remediation.

联系我们 contact @ memedata.com