Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Cloud

3/22/2018
09:02 AM
Jai Vijayan
Jai Vijayan
Slideshows
Connect Directly
Twitter
LinkedIn
RSS
E-Mail
50%
50%

7 Ways to Protect Against Cryptomining Attacks

Implementing basic security hygiene can go a long way in ensuring your systems and website don't get hijacked.
Previous
1 of 8
Next

Cybercriminals are increasingly hijacking enterprise systems and websites for cryptocurrency mining.

Crowdstrike and several other security vendors have recently reported incidents where businesses have suffered serious application - and operational - disruptions after attackers took over their systems to mine for Monero, and to a lesser extent, other digital currencies like Ethereum and Zcash.

In many other instances, criminals are surreptitiously installing cryptominers on websites and hijacking systems belonging to people visiting the sites.

Unlike ransomware and other malware, cryptominers are often legitimate software tools that are not always detected by anti-malware products. Since the only thing they do is use a system's CPU resources to crunch algorithms, cryptomining tools can sometime run invisibly without anyone detecting them. Many cryptomining tools deliberately throttle CPU and power usage so their presence on a system becomes even more unobtrusive. In fact, performance slowdowns often are the only indication that a computer has been hijacked for cryptocurrency mining.

Like many other unwanted software tools, cryptocurrency-mining software presents a threat mainly to organizations that fail to follow basic and long-prescribed security hygiene. The tools are distributed like any other malware product, and protecting against them requires the same measures.

Here are some of the best practices you should already be following to protect against cryptomining tools - and any malware.

 

 

Jai Vijayan is a seasoned technology reporter with over 20 years of experience in IT trade journalism. He was most recently a Senior Editor at Computerworld, where he covered information security and data privacy issues for the publication. Over the course of his 20-year ... View Full Bio

Previous
1 of 8
Next
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 5/28/2020
Stay-at-Home Orders Coincide With Massive DNS Surge
Robert Lemos, Contributing Writer,  5/27/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: Can you smell me now?
Current Issue
How Cybersecurity Incident Response Programs Work (and Why Some Don't)
This Tech Digest takes a look at the vital role cybersecurity incident response (IR) plays in managing cyber-risk within organizations. Download the Tech Digest today to find out how well-planned IR programs can detect intrusions, contain breaches, and help an organization restore normal operations.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-11844
PUBLISHED: 2020-05-29
There is an Incorrect Authorization vulnerability in Micro Focus Service Management Automation (SMA) product affecting version 2018.05 to 2020.02. The vulnerability could be exploited to provide unauthorized access to the Container Deployment Foundation.
CVE-2020-6937
PUBLISHED: 2020-05-29
A Denial of Service vulnerability in MuleSoft Mule CE/EE 3.8.x, 3.9.x, and 4.x released before April 7, 2020, could allow remote attackers to submit data which can lead to resource exhaustion.
CVE-2020-7648
PUBLISHED: 2020-05-29
All versions of snyk-broker before 4.72.2 are vulnerable to Arbitrary File Read. It allows arbitrary file reads for users who have access to Snyk's internal network by appending the URL with a fragment identifier and a whitelisted path e.g. `#package.json`
CVE-2020-7650
PUBLISHED: 2020-05-29
All versions of snyk-broker after 4.72.0 including and before 4.73.1 are vulnerable to Arbitrary File Read. It allows arbitrary file reads to users with access to Snyk's internal network of any files ending in the following extensions: yaml, yml or json.
CVE-2020-7654
PUBLISHED: 2020-05-29
All versions of snyk-broker before 4.73.1 are vulnerable to Information Exposure. It logs private keys if logging level is set to DEBUG.