Amplitude internal-systems event-data incident

The company says it contained and remediated the September 28 access and contacted affected customers.

Last modified

Summary

  • Environment: Localized portion of Amplitude internal systems
  • Operational impact: No outage duration established in the security notice
  • Financial impact: No confirmed incident cost quantified
  • Record status: Developing record. Reviewed October 30, 2026; updated as evidence emerges.

What happened

Amplitude says it detected, contained and remediated unauthorized access to part of its internal systems on September 28, 2026. [1]

Impact

Event data belonging to less than 0.3% of customer accounts was affected. This is an account percentage, not an end-user count. Amplitude said no end-user information was exposed for its other customers. [1]

Timeline

  1. Unauthorized access detected and remediated

    Amplitude describes containment on the day of detection.

    [1]
  2. Customer security update published

    The Trust Center update explains the limited customer-account scope.

    [1]
  3. Briefing updated

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

Threat Group & Attack Vector

Amplitude did not identify the access method or actor. It explicitly separated this incident from the recent PHP and Node.js vulnerabilities discussed elsewhere in its Trust Center. [1]

Actors

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

TTPs

  • No specific MITRE ATT&CK technique is currently mapped for this case.

Response

The company contacted affected customers and continued assessing impact with independent forensic support. Detailed exposed fields and an affected-person total remain undisclosed. [1]