Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

What to do if you've committed sensitive data to a Bitbucket Cloud repository


You have accidentally committed a file containing sensitive data.


Security researchers and threat actors alike are actively scanning hosted git repositories like yours, looking for passwords, secrets, and other useful configuration info potentially hiding in your data.

There are several free and openly available tools to automate the discovery of sensitive data across services like Bitbucket Cloud.

Using information found in publicly accessible repositories, attackers can then access and compromise your services and systems, often without your knowledge.

Unfortunately, the process to backtrack a mistake like this is not as straightforward as removing the lines or files in question, so we've outlined some steps for you below.


You should take the following actions as soon as possible:

  1. Remove the file with the sensitive content from repository, for more details please refer to:

  2. Once the file is removed, you need to make sure you remove it from the repository history as well, it can be done by using the BFG repo cleaner:

  3. Push the cleaned repository to Bitbucket remote and raise a support ticket for us to run the GC on the repository (

  4. To avoid adding and committing sensitive files back to the repository in the future, we highly recommend adding those file to .gitignore, that way you are sure you do not expose your credentials publicly:

  5. Rotate any passwords, keys or other credentials to avoid any malicious use following the exposure.

  6. Perform thorough review of all your repositories to ensure any sensitive keys, passwords or other data have been removed. If necessary repeat the steps above to remove any additional files and re-write the repository history.


Further Reading

Some further reading on this topic:

1 comment

Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Feb 05, 2020

Horrible things can happen sometimes :-)

Like # people like this


Log in or Sign up to comment
AUG Leaders

Atlassian Community Events