Overcoming the Pitfalls of HPC-based Cryptojacking Detection in Presence of GPUs

7 Citations (Scopus)

Abstract

With the rising number of devices connected to the internet, the number of cyber-attacks on these devices increases in parallel. There are several strategies that an attacker can pursue, like stealing intellectual property of a victim or encrypting data to demand ransom for the decryption. In this work, we are focusing on the detection of so called cryptojacking attacks, in which an attacker that gained access to a system, then introduces programs that use the processing power of the victim device to mine cryptocurrencies. The presence of such an attack is not obvious right away and the longer an attacker manages to remain undetected, the longer they can profit having the victim foot the power bill. In this study, we combine previous approaches to demonstrate that cryptojacking attacks can be detected with an accuracy of 96 we present a method to determine which performance events result in the best detection rates, thus allowing the selection of a few performance events that can be monitored simultaneously by modern consumer CPUs. In a next step, we show that the CPU counters-based detection mechanism fails when an attacker switches from using the CPU resources to GPUs for the mining tasks. Based on these findings we then improve the previous detection approaches by extending the CPU performance counters with GPU-specific metrics resulting in 99.86based cryptojacking attack class. In addition to a high detection rate the presented approach only causes a negligible performance loss while monitoring the whole system, which allows for continuous monitoring of live systems.
Original languageEnglish
Title of host publicationProceedings of the Thirteenth ACM Conference on Data and Application Security and Privacy
Place of PublicationNew York, NY, USA
PublisherAssociation for Computing Machinery
Publication date24.04.2023
Pages177–188
ISBN (Print)9798400700675
DOIs
Publication statusPublished - 24.04.2023

Cite this