Bitrise’s November 18 preliminary review says the November 13 attacker used valid credentials for an internal testing bot without two-factor authentication. The credential source remained under investigation. Files were accessed in fifteen customer workspaces: a signing certificate without its secret-store password, a provisioning profile and thirteen diagnostic logs. One log contained a credential and another an email address.

The company reported no indication of secret-store access or targeting, while GitHub audit logs were still outstanding, and recommended rotating secrets, tokens, certificates and connected Git credentials. Its detection advice has a concrete prerequisite: Google Secret Manager data-access read audit logs must be enabled to detect unusual secret-read volumes. Correlating a read with first use from a new address within an hour is one proposed signal.

bitrise incident