[!(https://thehackernews.com/images/-zOlEApVOiSg/YMCbAoxckBI/AAAAAAAACzY/BDUdtmDiujsWEVKdp_qfBuwh9ihFnvWkgCLcBGAsYHQ/s0/kubeflow-malware.jpg)](<https://thehackernews.com/images/-zOlEApVOiSg/YMCbAoxckBI/AAAAAAAACzY/BDUdtmDiujsWEVKdp_qfBuwh9ihFnvWkgCLcBGAsYHQ/s0/kubeflow-malware.jpg>) Cybersecurity researchers on Tuesday disclosed a new large-scale campaign targeting Kubeflow deployments to run malicious cryptocurrency mining containers. The campaign involved deploying [TensorFlow](<https://en.wikipedia.org/wiki/TensorFlow>) pods on Kubernetes clusters, with the pods running legitimate [TensorFlow images](<https://hub.docker.com/r/tensorflow/tensorflow/tags?page=1&ordering=last_updated>) from the official Docker Hub account. However, the container images were configured to execute rogue commands that mine cryptocurrencies. Microsoft said the deployments witnessed an uptick towards the end of May. [Kubeflow](<https://www.kubeflow.org/docs/about/kubeflow/>) is an open-source machine learning platform designed to deploy machine learning workflows on [Kubernetes](<https://kubernetes.io/docs/concepts/overview/what-is-kubernetes/>), an orchestration service used for managing and scaling containerized workloads across a cluster of machines. The deployment, in itself, was achieved by taking advantage of Kubeflow, which exposes its UI functionality via a dashboard that is deployed in the cluster. In the attack observed by Microsoft, the adversaries used the centralized dashboard as an ingress point to create a pipeline to run TensorFlow images that perform cryptocurrency mining tasks. "The burst of deployments on the various clusters was simultaneous. This indicates that the attackers scanned those clusters in advance and maintained a list of potential targets, which were later attacked on the same time," Microsoft's Senior Security Research Engineer Yossi Weizman [said](<https://techcommunity.microsoft.com/t5/azure-security-center/new-large-scale-campaign-targets-kubeflow/ba-p/2425750>) in a report. The intrusions also echo [similar attacks](<https://www.microsoft.com/security/blog/2020/06/10/misconfigured-kubeflow-workloads-are-a-security-risk/>) observed by Microsoft Azure Security Center last April that abused Internet-exposed Kubeflow dashboards to deploy a backdoor container for a crypto-mining operation. Weizman told The Hacker News that there's no evidence that the two campaigns were undertaken by the same threat actors. [!(https://thehackernews.com/images/-lkqROLFDwI4/YMCZF_sUswI/AAAAAAAACzQ/ZNwdYzlOMy8z2m-yR4cQWD2UCYaGLgcuwCLcBGAsYHQ/s0/malware.jpg)](<https://thehackernews.com/images/-lkqROLFDwI4/YMCZF_sUswI/AAAAAAAACzQ/ZNwdYzlOMy8z2m-yR4cQWD2UCYaGLgcuwCLcBGAsYHQ/s0/malware.jpg>) The ongoing attacks are said to have used two different TensorFlow images — tagged "latest" and "latest-gpu" — to run the malicious code. Utilizing legitimate TensorFlow images is also a clever design to avoid detection in that TensorFlow containers are prevalent in machine learning-based workloads. Furthermore, Microsoft said the attackers are able to take advantage of the images to run GPU tasks using CUDA, thereby enabling the adversary to "maximize the mining gains from the host." "As part of the attacking flow, the attackers also deployed [a] reconnaissance container that queries information about the environment such as GPU and CPU information, as preparation for the mining activity," Weizman said. "This also ran from a TensorFlow container." The development comes days after Palo Alto Networks' Unit 42 threat intelligence team disclosed a brand new form of malware called [Siloscope](<https://thehackernews.com/2021/06/researchers-discover-first-known.html>) designed to compromise Kubernetes clusters through Windows containers. Users running Kubeflow are recommended to ensure that the centralized dashboard isn't insecurely exposed to the Internet, and if deemed necessary, require that they be protected behind authentication barriers. Microsoft has also published a [threat matrix for Kubernetes](<https://www.microsoft.com/security/blog/2021/03/23/secure-containerized-environments-with-updated-threat-matrix-for-kubernetes/>) to better understand the attack surface of containerized environments and assist organizations in identifying current gaps in their defenses to secure against threats targeting Kubernetes. Earlier this April, the company, alongside other members of Center for Threat-Informed Defense, teamed up to release what's called the [ATT&CK for Containers matrix](<https://www.microsoft.com/security/blog/2021/04/29/center-for-threat-informed-defense-teams-up-with-microsoft-partners-to-build-the-attck-for-containers-matrix/>) that builds upon the Kubernetes threat matrix to detect "risks associated with containers, including misconfigurations that are often the initial vector for attacks, as well as the specific implementation of attack techniques in the wild." Found this article interesting? Follow THN on [Facebook](<https://www.facebook.com/thehackernews>), [Twitter __](<https://twitter.com/thehackersnews>) and [LinkedIn](<https://www.linkedin.com/company/thehackernews/>) to read more exclusive content we post.