EN
Deutsch English Français Homepage Svenska Homepage 日本語 Homepage Español Homepage Norsk bokmål Homepage 简体中文 Homepage Русский Homepage Italiano Homepage Ελληνικά Homepage العربية Homepage

WordPress incidents · Malicious code · Backdoors

Has your WordPress site been hacked?
We investigate what happened.

We investigate suspicious files, malware and potential backdoors. Our findings inform the cleanup, recovery and security measures we agree with you. We handle access and existing backups with care.

What the workflow can look like

From first signs
to verification.

01

Preserve findings and the starting state

02

Address malicious code and entry points

03

Verify functionality and plan preventive measures

Example workflow · Scope agreed with you

Understand the problem. Design a solution that fits.

Understand what happened, then address the findings.

A visible problem can have several causes. Deleting one file or restoring a backup may leave an attacker’s access intact. Within the agreed scope, we review files, the database, user accounts and suspicious changes.

Assess the incident and its scope

Record the domain, symptoms and any notices from the hosting provider. Preserve the relevant state before making changes.

Address malware and backdoors

Remove malicious code found during the investigation, replace affected components and secure identified unauthorized access points. We identify areas we could not verify or fully assess.

Follow-up checks and ongoing operation

We test key functions and document remaining risks. If there are warnings or suspensions, we help coordinate the response. The final decision to lift a restriction rests with the relevant third party.

Defined in advance

What to include in your first request.

Send the website address, the symptoms you noticed and roughly when they started. Let us know about any hosting suspension and available backups. Leave passwords and keys out of the initial form. We will agree how to share access securely. Uncoordinated deletions or restores can make the incident harder to investigate.

Example workflow

See what this changes in practice.

An online store redirects visitors to an unrelated domain. We assess the affected areas, preserve the current state and investigate the files and database. After the agreed cleanup, we check redirects, user accounts and key store functions. The findings determine the exact scope.

Working with Dreamseven

From the first conversation
to a result you can verify.

01

Assess the request

Confirm the symptoms, access and urgency.

02

Preserve the findings

Record the starting state and define what to investigate.

03

Clean up and verify

Address the findings and check key functions.

04

Handover and prevention

Review the results, open issues, updates and backups.

A clear next step

Request help.

Tell us your goal and where things stand. We will agree the scope, the access we need and the next steps.

  • Home
  • Industries
  • Portals
  • References
  • Contact