src_636032c91a0b4c9a97
- Source-provided label
- Not reported
- Evidence class
- mentioned in report
- Confidence
- Not reported
- Observed
- Oct 01, 2026 14:37 UTC
- Retrieved
- Oct 08, 2026 03:52 UTC
WordPress Backdoor Rebuilds Itself After Cleanup Using Files, Database, and Shared Memory
Cybersecurity researchers have shed light on a WordPress compromise in which threat actors deployed multiple persistence mechanisms to ensure that the final payload kept returning without having to infect the site again. The backdoor has been codenamed SC after the "SC_" markers present in the injected content. Sucuri has described the malware as a "self-healing mesh" that's
Reference details
- Source category
- Research & news
- Report title
WordPress Backdoor Rebuilds Itself After Cleanup Using Files, Database, and Shared Memory- First reported
- Oct 01, 2026 14:37 UTC
- Last reported
- Oct 01, 2026 14:37 UTC
- Catalog updated
- Oct 08, 2026 03:52 UTC
- Record ID
feaf6d7958b8f7755b3748bb57f57301ab791a209175c555c8ff67a2403d8f51
Published indicators
Network indicators are visibly defanged. This page does not make them clickable or send them to another service.
No validated file hashes or network indicators are stored for this record.
Source observations
This record contains metadata and attribution only. It does not host, download, unpack, render, or execute malware samples.
Feed collection status
Sources represented on this page. Publication and observation dates describe the content; successful batch dates describe local collection. A recent batch does not certify complete coverage or current provider availability.
1 sources: 0 stale, 0 needing attention, 0 paused, 1 unverified.
Review source update dates and status
- src_636032c91a0b4c9a97Collection status unverifiedLast successful batch: Unverified
Stale means older than twice the recorded collection interval, with a minimum of one hour; without an interval, the threshold is 24 hours. Cached content remains available while a feed is stale, paused, or unverified.