Bitrise has restored most services after unauthorized access to its internal systems. The mobile app build service closed its original incident on November 17 at 09:53 UTC. Its advice to rotate secrets and credentials connected to Bitrise remains in force.

Bitrise says it rotated internal credentials, revoked potentially affected tokens and sessions, and rebuilt its build infrastructure across all data centers. It reviewed services before restoring them and expanded logging. These are the provider’s remediation statements; the forensic investigation continues with external partners.

Restored service leaves exposure questions open

Bitrise’s detailed timeline dates detection to November 13 at 16:32 UTC. Its first public notice appeared at 20:44 UTC that day. The initial recommendation covered Git and source-code credentials. Later updates widened it to all secrets, access tokens and certificates stored in Bitrise.

Early November 14 updates said the accessed system did not store customer data and that investigators had found no evidence of exposed customer data, secrets or source code. Later notices say customers with identified impact are contacted directly, without specifying that impact or a customer count.

Miklos Zoltan’s PrivacyAffairs report, first published November 14 and updated November 17, highlights that change in wording. It does not independently establish which customer credentials were accessed. The later wording also does not establish that every customer’s secrets were stolen.

Evidence status: provider-confirmed unauthorized internal access, with customer exposure still unresolved publicly. The reviewed notices identify no entry point, initial-access date, affected software version or confirmed malicious app release.

Rotate at the issuing service, then reconnect

The affected trust boundary is a build service holding access to repositories and release systems. The relevant inventory depends on what each workspace connected or uploaded.

Bitrise added Protected Secret Masked Review to help identify credentials needing replacement. Its notice locates the feature at the eye icon under Workflow Editor → Secrets and Workspace settings → Shared resources.

For teams using Bitrise:

  • Inventory connected Git credentials, build secrets, tokens and signing certificates. Include shared workspace resources, not only the workflow currently being used.
  • Replace or revoke credentials at their issuing service. Merely changing the value saved in Bitrise leaves an old credential usable elsewhere until its issuer invalidates it.
  • Reconnect integrations with replacement credentials. Follow the issuer’s procedures for signing and release keys, where revocation can affect distribution. Coordinate those changes with the release owner.
  • Review repository and release audit records. Investigate unexpected access, credential use, project changes or releases, and preserve suspicious records. The detection date is not a verified start date for attacker access.
  • Retain any customer-specific impact notice. Ask what data or credentials were involved and for what interval; use that evidence to scope further response.

The provider’s infrastructure rebuild and a customer’s credential rotation address different parts of recovery. A working build does not invalidate a credential copied earlier.

Follow the new incident page

Bitrise’s follow-up notice now carries restoration updates and further customer guidance. Its November 17, 14:43 UTC update says Remote Dev Environments are restored; the page still lists Insights as affected.

Caveat: “Resolved” closes the original operational incident. Bitrise has not published a completed forensic account or a precise inventory of customer exposure.