Back to all lessons
Awareness Lessons
yesterday

Apify Breach Highlights Credential and Token Security Risks

Written by AI from the linked story. Not reviewed by an editor. How this works

Apify's internal systems were accessed without authorization, triggering an emergency rotation of API tokens, revocation of third-party OAuth connections, and forced 2FA resets for users. This incident illustrates how compromised credentials or access tokens can serve as an attacker's entry point into internal infrastructure, bypassing other security controls. The rapid response — revoking tokens and OAuth grants — was appropriate, but the need to reset 2FA for users suggests authentication mechanisms themselves may have been exposed or weakened. Organizations must treat API tokens and OAuth grants as high-value secrets, subject to the same lifecycle management and monitoring as passwords. Even when user data appears unaffected, unauthorized internal access can undermine trust and expose sensitive operational systems.

Tactical Insight

Immediate actions

  • Rotate all API tokens and revoke OAuth grants immediately upon detection of any unauthorized internal access.
  • Audit active third-party OAuth connections and enforce least-privilege scopes for all integrations.
  • Force re-enrollment of MFA for all users when authentication infrastructure may have been compromised.

Long-term improvements

  • Implement short-lived, automatically expiring API tokens with centralized secret management (e.g., HashiCorp Vault or AWS Secrets Manager).
  • Enforce phishing-resistant MFA (e.g., FIDO2/passkeys) for all user and administrative accounts.
  • Establish a formal OAuth and third-party integration review process to periodically audit and prune unnecessary grants.

Detection measures

  • Deploy continuous monitoring and anomaly detection on API token usage, flagging unusual access patterns or geographic anomalies.
  • Maintain detailed audit logs of all authentication events, token issuances, and OAuth authorizations for rapid forensic analysis.
  • Set automated alerts for bulk token usage or access from unexpected infrastructure.

Back this up with a control

All controls and vendors

Training helps people spot this. These controls make the attack fail even on the day someone does not.