Security · Cardiff & UK
Hacked website recovery
Contain the problem, recover carefully and address the route back in.
- Starting price
- From £475 + VAT
- Best for
- PHP or WordPress sites showing signs of unauthorised access or malware
- Leaves you with
- A documented recovery, agreed validation and a follow-up security plan
- Scope & timing
- Recovery starts with triage and an agreed response window. Availability, access and incident complexity determine what we can take on.
A clear scope. A useful outcome.
Unexpected redirects, altered pages, suspicious administrator accounts or unfamiliar files need a controlled response. Removing the visible symptom may leave the original entry point or another persistence mechanism in place. We help establish what is known, preserve useful evidence and agree a recovery route with the system owner and host.
The scope may include containment, review of affected code and files, restoration from a verified source, credential changes and application hardening. We separate engineering recovery from specialist forensic or legal work. Where the incident needs expertise beyond the agreed engagement, we make that dependency clear before presenting restoration as a complete resolution.
- An initial incident record covering symptoms, known changes and available evidence.
- An agreed containment and evidence-preservation plan with the owner and hosting provider.
- A recovery approach using reviewed code and files or a suitable verified backup.
- Relevant patching, access review and credential rotation through an agreed secure process.
- Validation checks, a record of remaining uncertainty and a practical hardening and monitoring handover.
How the work runs.
- Establish what is knownRecord when the symptoms appeared, which systems are affected and what evidence is available. Avoid deleting files or overwriting logs before deciding what needs to be preserved.
- Contain with the ownerAgree proportionate restrictions and host actions to reduce further exposure. Review privileged access and decide which services can remain available while recovery is prepared.
- Restore and address causesRecover from an appropriate verified source, review unauthorised changes and apply relevant fixes. Coordinate credential rotation and access changes with the systems that depend on them.
- Validate and hand overCheck the recovered journeys, permissions and relevant indicators. Document what was established, what remains uncertain and who owns the follow-up checks, so reopening the site is an informed decision.
Agree the boundaries first.
- Recovery cannot guarantee that all historical activity is reconstructable or all stolen data is recoverable.
- Specialist digital forensics, legal advice, regulatory reporting and round-the-clock monitoring are not implied by this engineering engagement.
Questions before we start.
- Should I restore a backup immediately?
- First consider containment and evidence preservation with your host or incident lead. A backup may already contain the compromise, and restoring over the current system can remove useful evidence. We assess the available sources and recovery implications before choosing one.
- Is patching PHP enough after a suspected breach?
- No. Applying a security fix addresses the relevant vulnerability but does not remove unauthorised accounts, altered files or other changes an attacker may have made. Recovery needs a separately agreed assessment and validation scope.
- Can you recover a hacked WordPress site?
- We can assess the site, host access, backups and observed symptoms to decide whether an engineering recovery is suitable. Scope may include core and plugin files, themes, administrator access and hosting configuration, with specialist escalation where needed.
- What should we include in the first message?
- Provide the public URL, hosting provider, approximate time symptoms started and a short description. Avoid sending passwords, customer data or full logs through the enquiry form. Preserve relevant records and use your host's incident contact if immediate containment is needed.
Work directly with QDev
Tell us what needs to change.
Related technical work.
Security
PHP2Shell assessment & patching
Assess PHP2Shell exposure and patch affected PHP runtimes. QDev helps with host coordination, controlled deployment and verification for the October 2026 CVEs.
You leave with An exposure record, patch evidence and verified application checks
Price From £375 + VAT
Explore PHP2Shell assessment & patchingMigration
Website & hosting migration
Move websites and PHP applications between hosts with QDev. Get a migration plan covering data, DNS, redirects, background jobs, testing and recovery.
You leave with A verified destination environment and a documented cutover
Price From £600 + VAT
Explore Website & hosting migrationSecurity
Web application security review
Review PHP code, access control and deployment configuration with QDev. Get prioritised security findings, with remediation and retesting scoped separately.
You leave with Prioritised findings, a remediation plan and clearly stated review limits
Price From £1,500 + VAT
Explore Web application security reviewStart with the facts.
Send the site, the hosting provider and what has changed. We'll reply with the next step and what it depends on.