The site is defaced, redirecting, sending spam, or flagged by browsers.
One free session per client: the first 4 hours with a specialist, plus unlimited AI as a tool.
A real senior specialist leads. Name on first reply. AI is a tool; a human checks the result.
01
What this problem looks like, how you can tell, and what is at stake if it stays.
What a compromise looks like, why 'restore and hope' often fails, and why we will not invent incident counts or a guarantee of a perfect forensic reconstruction.
A plugin, a stolen password, a forgotten admin, or a vulnerable app gave someone a foothold. Files changed. Users may be at risk. Search or hosting already sent a warning. A simple restore might bring the hole back with the site.
You feel exposed and responsible. You do not know what to tell customers, and you do not want to make it worse by wiping the wrong thing.
A compromised site is no longer yours alone until you take it back. Cleaning up is part of the duty you already have to the people who trusted that URL.
You want the attacker out, the malware gone, and a path back to a clean service you can trust.
A website hacked is a live incident: defacement, spam pages, a redirect, a crypto miner, or a phishing form appeared, and you are not sure the attacker is gone. You need containment, not a slogan.
A plugin, a leaked password, a forgotten admin, or a vulnerable dependency can be the way in. We will not invent a recovery time we have not earned, and we will not promise a complete forensic history if logs are gone.
Treat unexpected content, unexpected redirects, and unexpected admin activity as an incident until they are explained.
Including spam landing pages, a miner, or a phishing form.
Or partners tell you they were sent somewhere else.
Or a password stopped working because someone else changed it.
Or the inbox is filling with bounce reports.
A webshell or a modified core file is a common finding.
That feeling is already a reason to contain.
Before — if you leave it
If you only 'put the old files back,' the attacker can return. Visitors can be redirected to malware. Mail can be abused. Recovery later is harder if evidence is destroyed without a copy.
After — if we close it
The immediate abuse is stopped, the known malware is removed, the entry path you found is closed, and you have a factual note of what we saw and what still needs watching.
Recognize your situation? Message us, we will sort it out.
02
Where this usually comes from, why it shows up in fast or AI-assisted work, and how to check it yourself.
The way in is often ordinary: a plugin, a password, or a forgotten admin. Finding it matters as much as cleaning the visible damage.
Especially unmaintained ones that still run in production.
A shared admin password, a leaked key, or a leftover contractor account.
Or a world-writable upload directory.
A package or a script that was already hostile when it was installed.
The compromise may not have started in your theme.
Assistants will leave a debug route, a default password, or a plugin 'for later.' Fast launches also skip updates.
Do not 'clean' blindly by overwriting files if you have not contained access. A short, careful look is better than a noisy wipe that you cannot explain later.
Change what you still control, and do not keep using a machine you think is already taken.
A new PHP file in uploads is a clue.
The attacker may have moved the domain, not only the theme.
Deleting evidence in a panic makes the later work harder.
That changes who you must tell; we are not your legal counsel.
Recognize your situation? Message us, we will sort it out.
03
A senior specialist leads. AI is a tool. A human checks the result.
This is an incident, not a shameful secret. The useful order is: contain, understand, clean, close the hole, and only then talk about going fully live again.
DevHero is Human First. A specialist leads the recovery. AI may help us search files and logs. A human expert checks the cleanup. We are not a public-relations firm, and we will not invent a legal notice for you.
AI may help us search files for known signatures. A human expert decides what to take offline, what to keep, and what a clean restore looks like.
How a typical weekday case moves
Write on WhatsApp or Telegram. We take hard incident work. We do not invent a recovery clock, and we do not replace formal legal advice.
A screenshot, a spam URL, or an admin clue is enough to start.
Within a minute you should see their name. They are alerted, and can be called if they do not respond.
A deep forensic reconstruction may be larger, especially if logs are gone.
We contain what we can, find the way in when evidence allows, clean or restore, and help you come back with tighter access. A human checks that the site you reopen is one you can defend.
We help you contain access, preserve enough evidence, find the foothold, remove what should not be there, rotate credentials, and close the hole we can see. A full forensic report or a long hardening programme is a complex project. We do not promise that every historic intrusion can be fully reconstructed in 24 hours.
Access, obvious backdoors, and anything still serving hostile content.
Logs, copies, and a note of what changed.
A plugin, a password, a file, or a neighbouring host, if the evidence supports it.
Not a cosmetic hide of the spam page with the shell left behind.
Honesty about remaining risk is part of the result.
For a typical weekday case in scope, the aim is a contained site and a path back, not a novel-length forensic report.
A clearer picture of what is hostile and what still looks intact.
Containment steps taken or ready for you to approve.
A clean or cleaner state, or a restore plan, when evidence and backups allow.
A human-checked result.
A list of access changes and of questions we could not answer from the logs.
The URL and a screenshot already help. Do not paste every password into the first message; tell us which access exists, and be careful from a machine you trust.
Screenshots, spam paths, or a browser warning.
WordPress, another CMS, or a custom site.
And whether you already changed passwords.
A clean backup is often the difference between a day and a rebuild.
We will be honest about the technical picture; legal notice stays with you.
First 4 hours with a specialist + unlimited AI: free, once per client. Further work is paid, on request. A human leads and checks the result.
Free (first session)
Larger work uses a different rate, on request. We say so before we continue.
On request
The base plan is weekdays only. Weekend work is a separate product. Any surcharge is stated up front, before any call, and depends on complexity. Amount: on request.
On request
The first session is free: the first 4 hours with a specialist, plus unlimited AI, once per client. Work beyond that, the complex-project rate, and the weekend rate are paid, on request.
One free session per client: the first 4 hours with a specialist, plus unlimited AI as a tool.
Recognize your situation? Message us, we will sort it out.
04
What not to do next, the stacks we see in this kind of work, and how to keep the fix in place.
Panic wipes and silent 'fixes' often leave the attacker a second door.
A webshell or a new admin can remain.
You may give the attacker more access.
If credentials were the way in, they still are.
You may need them.
Say what you cleaned and what you could not prove.
Tell us the CMS and the host. If we should not take it, we will say so.
Plugins, themes, and core files.
A 'simple' site can still have an open door.
The compromise may live above the theme.
If payments may have been touched, say so early.
A restored site is not automatically a safe site. Access and updates have to change.
Including host, DNS, and mail.
Fewer doors.
Unmaintained code is a recurring way in.
Uploads should not be a place to execute code if you can avoid it.
A second visit is common if the door stayed open.
A file you have never tried is not a plan.
Default users and debug routes are invitations.
Do not assume it is 'just a cache.'
Recognize your situation? Message us, we will sort it out.
05
Straight answers about this problem, the session, and what happens next.
If it is serving hostile content, containment often comes first. Tell us what is live; we will help you decide the next technical step.
No honest specialist can. We will tell you what we cleaned, what we rotated, and what we could not prove.
Write on WhatsApp or Telegram with the URL and a screenshot if you have one. No form, no web chat.
No. That stays with you and your counsel. We do the technical incident work.
Then the work may be a careful clean in place, or a rebuild of what you can still trust. We will be honest about the effort.
No. This page is for an active compromise. The security-holes page is for holes you want closed before an incident.
No.
Not as a default, especially if logs are gone. A typical session aims at containment and a clean path back.
Sometimes, if the snapshot is clean and the way in is closed. A restore that still has the same plugin and the same password is a sequel.
Tell us the stack. If we should not take it, we will say so.
Yes. Each client gets one free session: the first 4 hours with a specialist, plus unlimited AI as a tool. The 24-hour line is how quickly we aim to start and close a typical weekday case in scope, not 24 hours of unpaid work. Further work is paid, on request.
If the site is already serving something you did not put there, write on WhatsApp or Telegram. You will talk to a person.
One free session per client: the first 4 hours with a specialist, plus unlimited AI as a tool.