WordPress Backdoor Rebuilds Itself After Cleanup Using Files, Database, and Shared Memory
-
Cybersecurity researchers at Sucuri have detailed a WordPress compromise in which attackers deployed a layered persistence framework designed to survive standard cleanup efforts. The backdoor has been codenamed SC, named after the "SC_" markers embedded throughout the injected content. Sucuri describes the malware as a "self-healing mesh", meaning multiple redundant components work together to restore the malicious payload if any single piece is removed.
The core of the design is redundancy across three separate storage layers:
- Files on the server hosting injected code
- The database, where malicious entries are planted
- Shared memory, used as an additional persistence location
Because each layer can rebuild the others, removing the infection from only one location is not sufficient. The remaining components can detect the missing pieces and restore the full payload without the attacker needing to re-infect the site.
Practical takeaway: sites hit by this family of malware likely require a coordinated cleanup that addresses files, database records, and shared memory together, rather than treating them as isolated artifacts. Standard file-level scanning alone may leave the persistence mechanism intact.
Source: The Hacker News
Has your organization dealt with a WordPress compromise that reappeared after cleanup, and how did you approach removing all persistence layers?
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login