# Bitrise Got Hacked. Here's What Mobile Teams Should Do Now Author: Cory McAboy Published: 2026-11-17 Source: https://rapptr.com/blog/bitrise-security-incident-rotate-keys/ Categories: Cybersecurity, Software engineering [Embedded media]() On November 13, Bitrise detected unauthorized access to one of its internal systems and took its services offline. If your team builds mobile apps, there is a good chance Bitrise sits somewhere in your release pipeline, so this one is worth your attention. Bitrise is telling every customer to rotate the secrets, tokens and certificates they store on the platform. The company says the affected system does not store customer data and that it has not found evidence that customer secrets were exposed. Rotation is a precaution, but it is one I would take today. The [Bitrise status page]() has the latest updates. ## What Bitrise does ![The Bitrise logo.]() Bitrise is a CI/CD platform built for mobile apps. It automates the release process, which covers code signing, building, testing and uploading an app to the App Store. To do that work, teams set up an account on Bitrise and store secrets that the build process uses. Those secrets often include signing certificates, App Store Connect keys and Git access tokens. Many teams also store AI keys from providers like OpenAI or Anthropic so their builds can call those services. [Embedded media]() ## Rotate your keys now If you use Bitrise, rotate every secret you stored there as soon as you can sign in. Bitrise also recommends rotating any Git and source code credentials connected to the platform. - Git provider tokens for GitHub or Bitbucket - App Store Connect and Google Play keys - Signing certificates and provisioning profiles - Third-party API keys, especially AI keys from OpenAI or Anthropic Revoke the old keys once the new ones are in place. Adding a new key does nothing if the old one still works. It is also worth checking your AI providers' usage dashboards for any activity you don't recognize. ## Bitrise is not the first This is a sad development, but I think it is part of a trend. [OpenCode]() and [Railway]() both disclosed security incidents in recent months that exposed customer keys. When you think about it, the payoff for hacking these platforms is huge. They can hold tens of thousands of AI keys, if not hundreds of thousands. Someone who gets those keys can run a lot of AI compute and send the bill to other people. [Embedded media]() ## Expect CI/CD prices to go up It is in the best interest of these platforms to raise their security standards and stay ahead of these attacks. That work is not free. Unfortunately, I think most of them will pass that cost on to customers. I would expect CI/CD services to get more expensive over the next while. That is the reality of building with AI right now. [Embedded media]() ## You don't have to use Bitrise [AI agents]() can now handle a lot of the build and release work on their own. They are not as polished at it as Bitrise yet, but they are getting close. One setup I like is Claude Managed Agents running the build steps, paired with GitHub Actions to trigger them on every push. ![A three-step release pipeline: GitHub Actions kicks off a run on every push, Claude Managed Agents build, test and sign the app, and the build ships to the App Store and TestFlight.]() ## We can help you sort it out If you are not sure which keys to rotate, or you want to rethink how your mobile apps get built and shipped, reach out. My name is Cory, I'm at Rapptr Labs, and I'd be happy to talk it through. [**Get in touch with Rapptr**]() ## Frequently Asked Questions **What happened in the Bitrise security incident?** On November 13, 2026, Bitrise detected unauthorized access to an internal system and took its services offline. Bitrise is asking customers to rotate the secrets, tokens and certificates they store on the platform as a precaution. **Were Bitrise customer secrets stolen?** Bitrise says the affected system does not store customer data and that it has not found evidence that customer secrets were exposed. It still recommends that every customer rotate their secrets. **Which keys should I rotate after the Bitrise breach?** Rotate every secret stored on Bitrise, including Git tokens, App Store Connect and Google Play keys, signing certificates and any AI keys. Revoke the old keys after the new ones are in place. **Why are CI/CD platforms being targeted?** These platforms can hold huge numbers of AI keys for their customers. Stolen keys let attackers run AI compute that other people pay for, which makes the platforms valuable targets. **What can I use instead of Bitrise?** AI agents can now handle much of the build and release process. One option is Claude Managed Agents running the build steps, paired with GitHub Actions to trigger them.