Some tips to review Docker Hub Hack of 190k accounts
Tags: hacking, docker, security, devops
Published: 2020-06-24 21:17:20

---
title: Some tips to review Docker Hub Hack of 190k accounts
published: true
date: 2019-04-27 18:05:37 UTC
tags: hacking,docker,security,devops
canonical_url: https://blog.madhuakula.com/some-tips-to-review-docker-hub-hack-of-190k-accounts-addcd602aade
---

![](https://cdn-images-1.medium.com/max/775/1*MXyGHENxlZYvCdD-BKd2eg.png)<figcaption>Docker Hub Hack of 190k accounts compromised and put everyone at risk!</figcaption>

As most of you must be aware, Docker Hub has been compromised very recently and this attack has put almost 190K users at risk. According to me, this is one of the craziest supply chain attacks in the recent history. I say so, because it is not easy to make oneself foolproof against this attack. We might have to review multiple things before we feel safe, and still, we cannot provide the guarantee that we are secure enough.

Read more about this hack in [Hacker News thread](https://news.ycombinator.com/item?id=19763413)

[Docker Hub Hacked - 190k accounts, GitHub tokens revoked, Builds disabled | Hacker News](https://news.ycombinator.com/item?id=19763413)

For your benefit, I have come up with a list of checks which might help you to review your Docker hub, Github account, etc. Listed below are some of the checks that might help you while reviewing your Docker hub, Github accounts. All of these points are taken from my personal checklist, and they might or might not guarantee that you are completely secure.

### Checklist

- Login to your [Docker Hub](https://hub.docker.com) and change your password in account settings page

![](https://cdn-images-1.medium.com/max/1024/1*8qM6absv8Fqqr38tWIdukQ.png)

- Check each of your repository image’s last build time, and see if you could identify any suspicious build. Additionally, check if any new tags were created for the images, or, if new images have been created or pushed manually

![](https://cdn-images-1.medium.com/max/1024/1*BcOvK7bAIhECqLbIwbEVoA.png)

- Review the repository settings and check if any new collaborator has been added without your knowledge

![](https://cdn-images-1.medium.com/max/1024/1*ohiMa8QXChJzQojfqxenYA.png)

- Review all external webhooks. Check if a suspicious webhook has been added to any of the repositories, or, if an existing webhook has been modified suspiciously

![](https://cdn-images-1.medium.com/max/1024/1*okYTgn1K2YRVTpoYJyan0Q.png)

- Review your organization’s team members and ensure that any unknown user has not been added

![](https://cdn-images-1.medium.com/max/1024/1*aKIlYK3B3cpPglMJt6RdOg.png)

- Ensure your automated builds from version control systems have been revoked and reconnected. Also, check for new connections or providers that might have been added suspiciously. Finally verify if the emails are mentioned correctly and that no new or modified webhooks have been added

![](https://cdn-images-1.medium.com/max/1024/1*UQXi0gpHMo4lkzEN8i-D5Q.png)

- Navigate to your version control system provider and ensure you revoke the existing application integration and tokens. Also, review if any new GitHub apps have been added or if the existing ones have been removed

![](https://cdn-images-1.medium.com/max/1024/1*nngOgdxzCfuWt0-xCUwQHQ.png)

- Review yours and your organisation’s GitHub security activity to verify if any suspicious changes have been made over time

![](https://cdn-images-1.medium.com/max/1024/1*4mpvFTUxOVs2MGBlnPMSuA.png)

- Review your organisation’s and your personal account’s audit logs. Review any changes that have been made based on the privileges of the Docker Hub integration with GitHub

![](https://cdn-images-1.medium.com/max/1024/1*Cl2QBKv0_yvTIfPX_dbl7Q.png)

- Some additional checks which might be done includes, verifying your base images and existing images as it is possible that the corresponding owner accounts might have been compromised too. Use some open source image scanners like [Clair](https://github.com/coreos/clair), [Vulners Audit](https://vulners.com/audit), etc. These checks would apply even if you are not in Docker Hub and are using a private registry. This is because you might have ended up using some external base image like nginx, alpine, etc.
- Monitor, and monitor again, all the things (containers) that you are running. This is required because there are chances that some of the running containers might have been compromised already

> These are some of the tips that I came up with and I would love to know what are some of the other thing that you might be thinking of and that could be helpful for our community. Please leave your comments and suggestions here and I will incorporate your suggestions into my post.

#### Contributors

- [Riddhi Shree](https://medium.com/u/a536602bb4c9)

> Please feel free to provide any feedback, suggestions or improvements. If you liked this article, click the 👏 button and share this post so that other people could also benefit from this post.

* * *