Persistence

WordPress Cron Malware

Malware uses scheduled WordPress cron events to reinfect files, fetch payloads or recreate malicious users.

Symptoms

These are common signs associated with this type of WordPress compromise. The exact behavior can vary by hosting setup, cache layer, plugins and how the attacker configured the payload.

• Infection returns at intervals.
• Unknown scheduled actions appear.
• Files are re-created after deletion.

Technical overview

Attackers register malicious cron tasks through backdoors, compromised plugins or injected database options.

Important: visible symptoms are rarely the whole incident. A safe recovery should identify both the payload and the persistence mechanism that allowed it to run.

Indicators of compromise

During investigation, these indicators are commonly reviewed. They do not prove compromise alone, but they help map scope and root cause.

Investigation process

WP•FIX treats this as an incident, not a simple file deletion task. The review normally includes WordPress core integrity, theme and plugin files, uploads, database options, users, cron events, redirects, cache layers and the most likely entry point.

Recovery process

• Create a safe recovery point before changing production data.
• Remove malicious files, scripts, database payloads and persistence mechanisms.
• Replace compromised components with clean versions where appropriate.
• Review administrator users, credentials and access paths.
• Harden the site and document the recovery path.

Prevention

Prevention depends on the root cause. Common controls include removing nulled components, updating vulnerable plugins, reducing administrator access, hardening login paths, adding monitoring and keeping verified backups.

FAQ