WordPress site hacked, entire database encrypted, no password — what if I ignore it and reinstall?

do a fresh install bro this is too hard start from scratch. anyway if the db password is cracked check with security team but hosting restore is for the rescue...

Database is protected; good news, if access is lost you can recover from backup. Check the MySQL dump, if there's shell code in base64 that backup is dirty too. If you have SSH access, cross-check file timestamps with access.log — find the compromise date, grab the newest backup from before that.

bro there's a lot to do but it's not that complicated and once aain — restore from the 7-day backup, then review plugins. delete any weird plugins. and what you need to do now: change all passwords FTP MySQL, cPanel all of them. and install fail2ban, let's see...

WordPress sites are usually compromised due to plugin vulnerabilities or weak passwords. Do these steps: 1) Identify the oldest clean backup, 2) Download it, 3) Check on local machine (virus scan, file hashes), 4) Restore, 5) Update all plugins, 6) Change all passwords (DB user, FTP, cPanel, WordPress admin), 7) Install a WP Security plugin, 8) Monitor for two weeks, if it gets hacked again backup the database — this time switch to a new hosting.

even the biggest companies get their wordpress sites hacked but you got hacked too? welcome to the club 😂 learn your lesson change your password install an ssl cert and youll be good.

We experienced almost the exact same thing last year. Hasty decisions become decisions you have to fix six months later.

If permission and scope aren't in writing, don't start that test. I'm also curious if anyone does it differently.

You're right, I've been down that road too. If you don't write this down from the start, it leads to arguments later.

If you post the result here, it will help others too.

I was thinking the same thing. Don't hesitate to ask; those who don't ask always pay more.

That's all sorry if I went on too long.

Ive been down this road let me tell you. The biggest time-waster for us was not knowing who had the final say.

This is my opinion, I'm not claiming it's absolute truth.

Saved.

I disagree with you on this point. Mistakes made on the wordpress hacked what to do side are usually reversible but expensive.

If you get three different answers on a topic, the question was asked wrong. If you have questions, write them; Ill answer as best I can.

This approach has a cost, which isn't discussed. Don't rely on a single measure; go layer by layer.

Hope this helps.

Exactly like that. Don't hesitate to ask; those who don't ask always pay more.

Forgotten test environments are more often the entry point than live systems. This is my opinion, I'm not claiming it's absolute truth.

Let me summarize what's been said so far. Most time waste accumulates in tasks waiting for approval.

If permission and scope aren't in writing, don't start that test.

My questions are cleared up, thanks. Solutions that work at a small scale collapse when you grow; I learned this late.

An automated scan report is not the same as a penetration test. Proven by experience.

the answer above hits the nail on the head then if you dont write this down from the start it leads to arguments later.

There's one point I'm curious about. Payment information changes are never verified through the channel they came from.

I'm also curious if anyone does it differently.

You're right, I've been down that road too. The harder it is to reverse a decision, the slower you should make it.

Proven by experience.