Vulnerabilities / Threats

10/31/2017
12:00 PM
Dawn Kawamoto
Dawn Kawamoto
Slideshows
50%
50%

How to Make a Ransomware Payment - Fast

Paying ransom in a ransomware attack isn't recommended, but sometimes, it's necessary. Here's how to pay by cryptocurrency.
Previous
1 of 8
Next

Image Source: Steve Heap via Shutterstock

Image Source: Steve Heap via Shutterstock

Against their better judgment, sometimes IT security professionals are pressured to help their CEOs, chief financial officers, or boards of directors make a ransomware payment.

Paying ransom in a ransomware attack is not as easy as wiring money from a bank, or filling a suitcase full of hundred-dollar bills. Ransomware attacks typically call for sending cryptocurrency to unlock kidnapped data, with values ranging from a few hundred to even millions of dollars

And although traditional financial institutions reportedly are beginning to show interest in cyrptocurrencies, that payment avenue will likely remain blocked for ransomware payments under anti-money laundering and know-your-customer regulations that institutions must abide by. Last year, New York prosecutors charged a Bitcoin exchange operator with violating anti-money laundering laws when it facilitated making a ransomware payment, according to a Fortune report. However, Coin Center, a nonprofit cryptocurrency research and advocacy group, contended it should not be a crime to help ransomware victims.

Meanwhile, cybercriminals are ramping up the deadlines for victims to make ransom payments, or face the potential of having their locked up data, files, photos, and video destroyed. Some attacks delete files if a victim can't meet tight deadlines in time.

"People are being put on a countdown timer and data will be deleted if they don't pay. As a result, companies want to make the payment as fast as possible. Jigsaw, for example, will delete an individual file every hour that you don't pay," says Rick McElroy, security strategist for Carbon Black.

Nearly 60% of employees hit by a ransomware attack at work personally paid the extortion money, according to a new report released today by Intermedia.

While law enforcement as well as security experts in general don't recommend paying ransom, here are seven tips for how to make a ransomware payment in that dire case where there is no other choice. 

 

Dawn Kawamoto is an Associate Editor for Dark Reading, where she covers cybersecurity news and trends. She is an award-winning journalist who has written and edited technology, management, leadership, career, finance, and innovation stories for such publications as CNET's ... View Full Bio

Previous
1 of 8
Next
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
REISEN1955
100%
0%
REISEN1955,
User Rank: Ninja
11/1/2017 | 3:48:49 PM
Re: backup, backup and backup again
TOTALLY AGREE!!!  Any business that does not have a valid and tested system restore protocol AND server backup plan deserves what it gets!!!  Tht said - an ransomware payment should come out of the salary pool of the IT staff which would then MAKE THEM MUCH MORE AWARE of the problems.  None of this is NEWS FOR TODAY folks!!!  Valid DR and restore protocols have been around for years.  NOBODY wants to implement or test them. 
jenshadus
50%
50%
jenshadus,
User Rank: Strategist
11/1/2017 | 12:50:57 PM
backup, backup and backup again
My work computer is backed up once a day.  Plus I use a VDI within my laptop and leave few files on my laptop.  Just the essentials for when I travel.  At home I backup everyday, keep my firewall on, and keep the anti-virus scanning.  If I get hit, which I doubt (cross my fingers) I'll just wipe my own computer. 
What We Talk About When We Talk About Risk
Jack Jones, Chairman, FAIR Institute,  7/11/2018
Ticketmaster Breach Part of Massive Payment Card Hacking Campaign
Jai Vijayan, Freelance writer,  7/10/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-14084
PUBLISHED: 2018-07-16
An issue was discovered in a smart contract implementation for MKCB, an Ethereum token. If the owner sets the value of sellPrice to a large number in setPrices() then the "amount * sellPrice" will cause an integer overflow in sell().
CVE-2018-14085
PUBLISHED: 2018-07-16
An issue was discovered in a smart contract implementation for UserWallet 0x0a7bca9FB7AfF26c6ED8029BB6f0F5D291587c42, an Ethereum token. First, suppose that the owner adds the evil contract address to his sweepers. The evil contract looks like this: contract Exploit { uint public start; function swe...
CVE-2018-14086
PUBLISHED: 2018-07-16
An issue was discovered in a smart contract implementation for SingaporeCoinOrigin (SCO), an Ethereum token. The contract has an integer overflow. If the owner sets the value of sellPrice to a large number in setPrices() then the "amount * sellPrice" will cause an integer overflow in sell(...
CVE-2018-14087
PUBLISHED: 2018-07-16
An issue was discovered in a smart contract implementation for EUC (EUC), an Ethereum token. The contract has an integer overflow. If the owner sets the value of buyPrice to a large number in setPrices() then the "msg.value * buyPrice" will cause an integer overflow in the fallback functio...
CVE-2018-14088
PUBLISHED: 2018-07-16
An issue was discovered in a smart contract implementation for STeX White List (STE(WL)), an Ethereum token. The contract has an integer overflow. If the owner sets the value of amount to a large number then the "amount * 1000000000000000" will cause an integer overflow in withdrawToFounde...