Skip to the content.

This page is a sub page of the case file for case DIVD-2026-00007 - Victim Notification Operation Endgame S03E03, which contains the general information about this case.

It was determined that your website was spreading malware via the SocGholish malware downloader during Operation Endgame edition S03E03

If you are reading this it probably means that your website was spreading malware via the SocGholish malware downloader, and maybe still is. You website was likely compromised through stolen administrator credentials.

What does this mean?

Your WordPress adminisator credentials have been stolen at some point. Criminals have used these credentials to compromise your WordPress site and impant the SocGholish stealer there. The malware downloader has been using your site to serve fake browsers update dialog screens to convince innocent visitors of you website to download infostealer malware.

What should I do?

Your website has been compromised. We have sent you the URL and the email address of the account on it that was used to compromise it.

The following articles describe the malware and how to remove it:

Summary of steps

We have created the AI summary below to help you

What is SocGholish?

SocGholish (also known as FakeUpdates) is a JavaScript-based malware campaign that compromises legitimate websites by injecting malicious scripts. Visitors to infected sites are presented with fake browser or software update prompts, tricking them into downloading malware. Once executed, secondary payloads can lead to ransomware infections, credential theft, or unauthorized network access.

The malware is associated with threat actor TA569 and is notable for its multi-layered infection approach, which can make detection and cleanup more difficult.

Common signs of infection:

Cleanup Steps

Step 1 – Identify the Infection

Use one or more scanning tools to confirm infection and locate malicious code:

Also check for unauthorized DNS subdomains — SocGholish sometimes uses domain shadowing, adding subdomains (e.g. update.yourdomain.com) that point to malicious servers.

Step 2 – Take a Full Backup

Before touching anything, create a complete backup of:

This ensures you have a fallback in case cleanup goes wrong.

To prevent further visitors from being exposed to the malicious payload, consider placing the site in maintenance mode or blocking public access temporarily.

Step 4 – Revoke and Reset All Credentials

Change all credentials that could have been compromised or used for unauthorized access:

Use strong, unique passwords for each.

Step 5 – Locate and Remove Malicious Code

Manually inspect the WordPress installation for injected scripts and unauthorized files.

Key locations to check:

WordPress plugins that help locate injections:

In the database: Check wp_posts, wp_options, and wp_usermeta for injected <script> tags or base64-encoded content. The siteurl, home, and widget option fields are common targets.

⚠️ Note: Some SocGholish variants use malicious PHP files that load additional obfuscated code layers, fetching the final payload from an external server. The total number of infected files can run into the thousands. If manual cleanup is impractical, use an automated solution or restore from a known-clean backup.

Step 6 – Run a Full Malware Scan

After manual cleanup, run a full server-side scan with a security plugin (Wordfence, Sucuri, or MalCare) to catch anything missed.

Step 7 – Update Everything

Outdated components are the most common entry point for this malware:

Remove any plugins or themes that are unused or abandoned.

Step 8 – Fix File Permissions

Incorrect file permissions can leave the site vulnerable to re-infection:

Step 9 – Harden the Installation

After cleanup, implement additional hardening measures:

Step 10 – Verify the Site is Clean

Re-run external and internal scans to confirm no malicious code remains. Check the page source of the live site for any lingering <script> injections.

Step 11 – Request Review from Search Engines and Email Services

If the site was flagged or blacklisted:

Step 12 – Monitor and Maintain

More questions?

The main case file contains a Frequently Asked Questions (FAQ) section. If that does not answer your questions, please reply to the email you received or email us at DIVD-2026-00007@csirt.divd.nl.

For more information, see the main case file.