Hacking into Mysql and data encryption

[Brandsum]

Yes. But it has only CURD permissions.

 

[Daestrum]

As I wrote, it was only my test server with no important, sensitive data etc.
So there is no need for any action, I will not pay anything. There are application test garbage.

This is the wrong attitude. You MUST report it or they will just do it to someone else.
You didn't lose real data but the fact remains it is a criminal offence, so must be reported.
Also report it to bitcoin - the address they gave, they can take action against the recipient of any payments made.

 

[Brandsum]

How did it end with you? I read the mention in the network that they don't really have a copy of the data but they do "Drop Database" right away.

Luckily I had a backup copy of the whole db.

 

[Haris Hafeez]

I think you should develop locally or on a machine that is not Internet facing. That way, you don't need to worry about test databases being stolen.
For production or other supporting environments (uat, dev, DR sites etc), you need to lock down the databases such that only a certain user can access from a certain machine. If you're deploying in AWS for example, you can shut down all access to your db other than that by your application server by placing your db in a non public facing VM, allowing connections from only your app servers ip addresses and harden it even further by using IAM roles. No simple solution to securing anything but it's a start.