Threat feed

Bitrise bot account breach

Bitrise CI platform breached through internal bot account lacking two-factor authentication

Posted · Spectrum Delta Research Team

Summary

Mobile continuous integration platform Bitrise disclosed that an unattributed attacker used valid credentials for an internal testing-bot account that lacked two-factor authentication to access 15 customer workspaces, downloading a code-signing certificate, a provisioning profile and 13 build logs before the platform was shut down on November 13 (grade A/1). The attacker had spent weeks preparing an enumeration and privilege-escalation scheme, ran builds whose scripts probed the build environment for credentials and tested cross-account listing, and accessed internal Bitrise repositories, infrastructure configuration and build-machine logs. Bitrise declared a severity-one incident, took the platform offline within hours, rotated all production secrets and 919 cloud service account keys, and rebuilt build infrastructure from trusted sources across two continents. Defenders should enforce two-factor authentication on every bot and service account, and alert on builds whose scripts enumerate environment credentials or attempt cross-account listing.

Breakdown

Targets

Organizations

  • Organization: Bitrise

Technical exposure

  • CI platforms holding service and bot accounts without 2FA
  • Build environments expose credentials to scripts they run
  • Code-signing certificates and build logs in customer workspaces

Adversary

Unattributed · Bitrise first-party disclosure (grade A/1)

Procedures (4)

  1. Valid credentials for an internal testing-bot account without 2FA

    Logs

    • Bitrise sign-in and account audit logs · Authentications by bot and service accounts from unexpected IP addresses, especially accounts not enrolled in two-factor authentication
  2. Weeks of enumeration and privilege escalation from the bot account

    • T1087Account Discovery

    Logs

    • Bitrise platform audit logs · Bulk enumeration queries, permission and role changes, and cross-account listing attempts performed by service accounts
  3. Build-time scripts probing the environment for credentials

    • T1552Unsecured Credentials

    Logs

    • Bitrise build logs · Builds running scripts that enumerate environment variables, secret paths and credential stores, or probe other accounts from the build environment
  4. Unauthorized access to customer workspaces and signing material

    • T1530Data from Cloud Storage

    Logs

    • Bitrise workspace file access logs · Bulk file downloads by non-customer service accounts, including code-signing certificates, provisioning profiles and diagnostic build logs

Sources

Grades are source reliability (A–F) and information credibility (1–6).

Questions, detections or sightings of Bitrise bot account breach? Bring them to the community.