Hacker ransoms 23k MongoDB databases and threatens to contact GDPR authorities
A hacker has uploaded ransom notes on 22,900 MongoDB databases left exposed online without a password, a number that accounts for roughly 47% of all MongoDB databases accessible online, ZDNet has learned today.
The hacker is using an automated script to scan for misconfigured MongoDB databases, wiping their content, and leaving a ransom note behind asking for a 0.015 bitcoin (~$140) payment.
The attacker is giving companies two days to pay, and threatens to leak their data and then contact the victim’s local General Data Protection Regulation (GDPR) enforcement authority to report their data leak.
Attacks planting this ransom note (READ_ME_TO_RECOVER_YOUR_DATA) have been seen as early as April 2020.
In a phone call with ZDNet today, Victor Gevers, a security researcher with the GDI Foundation, said initial attacks didn’t include the data wiping step.
The attacker kept connecting to the same database, leaving the ransom note, and then returning again to leave another copy of the same ransom note, a few days later.
But Gevers told ZDNet today the attacker appears to have realized they made a mistake in their script. Since yesterday, the hacker has corrected their script and is now actually wiping MongoDB databases clean.
“It’s all gone,” Gevers told ZDNet. “Everything.”
While some of these databases appear to be test instances, Gevers said that some production systems were also hit and have now had staging data deleted.
Gevers, who reports exposed servers to companies as part of his duties in the GDI Foundation, said he noted the wiped systems earlier today when checking on MongoDB systems he was scheduled to report and get secured.
“Today, I could only report one data leak. Normally, I can do at least between 5 or 10,” Gevers told ZDNet.
Similar attacks happening since late 2016
However, these “MongoDB wiping & ransom” attacks aren’t new, per-se. The attacks Gevers spotted today are just the latest phase of a series of attacks that started back in December 2016, when hackers realized they could make serious money by wiping MongoDB servers and leaving a ransom demand behind, tricking server owners desperate to get their files back.
Back in 2017, Davi Ottenheimer, Senior Director of Product Security at MongoDB, Inc., blamed the attacks –and rightfully so– on database owners who failed to set a password for their databases, and then left their servers exposed online without a firewall.
Almost three years later, nothing appears to have changed. From the 60,000 MongoDB servers left exposed online in early 2017, the needle has barely moved to 48,000 exposed servers today, most of which have no authentication enabled.
Most of the time, these servers get exposed online after administrators follow incorrect MongoDB configuration tutorials, make honest mistakes when configuring their systems, or use server images that come packed with a misconfigured MongoDB system out of the box.
The default MongoDB database setup today comes with secure defaults out of the box, but despite this, we still have tens of thousands of servers that get exposed online on a daily basis for one reason or another. For server admins looking to secure their MongoDB servers the proper way, the MongoDB Security page is the best place to start for getting the right advice.