Observed incident
Bitrise traces an ARTEX intrusion through a dormant internal bot account
Reported
Published here
What happened
Bitrise attributes an October–November intrusion to ARTEX or derived tooling. A November 13 login to a dormant internal bot account without two-factor authentication exposed credentials that enabled access to internal systems and files in 15 customer workspaces.
Parties and reporting
Where this happened
Victim location not disclosed. Real organizations or systems were affected or targeted, but the sources do not say where. Explore the world map.
AI tools and systems: ARTEX or derived software, norma agent SDK, Bitrise CI and cloud credentials
Outcome
Accessed customer files comprised one signing certificate without its password, one provisioning profile and 13 diagnostic build logs. All 15 customers were contacted. Bitrise revoked 919 cloud service-account keys, rotated production credentials and rebuilt infrastructure. Every recorded protected-resource read attempt after the last successful stolen-key call on November 13 was refused, including the November 18 return.
Operating lesson
Remove dormant service accounts, enforce strong authentication and short-lived credentials, and verify customer impact at file level before interpreting broad cloud activity counts.
Evidence and limits
The report identifies tooling, not the operator, its location or the model used. How the bot credentials were obtained remains unestablished. Fifteen counts customer workspaces with unauthorized file access, not all public downloads or all identities queried. One log contained a credential and another an email; signing-certificate access did not include its password. Earlier cross-customer isolation attempts failed. Public install links are not private-data breaches. Initial notices reported no confirmed customer access; the later file-level analysis supersedes that preliminary scope. Exact-event dedup found no named Bitrise event in the baseline; overlap with unnamed ARTEX victims cannot be ruled out.
Sources
- Bitrise first public incident notice: November 13 at 20:44 UTC
Primary source ·
- Bitrise preliminary review and customer guidance
Primary source ·
- Bitrise detailed evidence-graded ARTEX report, version 1.4
Primary source ·