Dropbox security incident

A phishing page captured GitHub credentials and an authentication code; Dropbox disabled the attacker’s access.

Last modified

Summary

  • Environment: GitHub repositories used by Dropbox developers
  • Operational impact: 130 repositories copied; core applications and infrastructure unaffected
  • Financial impact: No financial loss quantified in the reviewed evidence
  • Record status: Developing record. Reviewed October 19, 2026; updated as evidence emerges.

What happened

Dropbox reported that an attacker copied 130 GitHub repositories in October 2022. Its original report describes CircleCI impersonation emails and a fake login page that captured GitHub credentials and a one-time password. [2]

Impact

The code contained developer credentials, principally API keys. Associated data included a few thousand names and email addresses of employees, customers, sales leads and vendors. [2]

Dropbox said customer account contents, login passwords and payment information were unaffected, as were core application and infrastructure code. [2]

Timeline

  1. GitHub warning and access disabled

    GitHub reported suspicious activity beginning the previous day; Dropbox disabled access.

    [2]
  2. Incident report published

    Dropbox published its findings.

    [2]
  3. Briefing updated

    This briefing was last reviewed and updated on October 19, 2026.

Threat Group & Attack Vector

The phishing page impersonated CircleCI. [2]

Actors

  • No threat actor group has been identified in the reviewed public evidence.

TTPs

Response

Dropbox coordinated credential rotation, engaged forensic experts, notified affected people and authorities, and accelerated WebAuthn adoption. Its log review found no evidence of successful credential abuse. [2]