WordPress Compromise Recovery
Forensic cleanup and hardening for persistent malware in legacy environments.
- Payload and persistence analysis
- Core and plugin integrity checks
- Recovery followed by operational remediation
Security Engineering
My security work grows out of operating long-lived production systems: malware investigation, WordPress compromise cleanup, integrity verification, hardening, and policies that reduce preventable exposure across a large fleet.
I approach incidents as system failures rather than isolated bad files. Recovery includes identifying persistence, restoring trust, preserving business function, and reducing the chance of recurrence.
Philosophy
Security is not a cleanup step. It is a property of how the system is designed and operated.
Treat every unexplained change as evidence, not noise.
Reduce attack surface through updates, retirement, least privilege, and operational standards.
Problems
The most valuable work usually begins where a system has accumulated complexity, operational risk, or assumptions no one has revisited.
Approach
I establish a trustworthy baseline, trace indicators across files, database content, users, scheduled tasks, and configuration, then remove both payload and persistence.
After recovery, I verify from multiple angles and address the operational conditions that made the compromise durable.
Selected Projects
Forensic cleanup and hardening for persistent malware in legacy environments.
Designed AI-assisted workflows that accelerate malware investigation while keeping technical responsibility with the engineer.
AI functions as an analytical assistant. Verification and final judgment remain human responsibilities.
A supportability and planned-obsolescence framework for a large production fleet.
Calendar Defender
A practical engineering project exploring collaborative AI review rather than depending on a single model to produce solutions.
Independent AI models reviewed architecture, challenged assumptions, explored edge cases, and critiqued implementation approaches before human synthesis.
The result was not simply better code. It was a repeatable engineering process that improved transparency, reasoning quality, and confidence in technical decisions.
Experience
Zee Creative · 2011–Present
Lead developer and systems architect for a large, long-lived portfolio of production websites and integrations.
SunGard Higher Education · approximately 8 years
Technical lead in enterprise higher-education software, working across large Oracle systems, performance testing, defect analysis, and release delivery.
Technologies
Business Value
Deleting the obvious malicious file may restore a page while leaving the attacker’s access intact.
Durable recovery restores confidence in the whole system and changes the conditions that allowed the incident to persist.
Contact
For technical leadership, architecture, modernization, or complex systems work, contact me directly.
Contact JulieA system is not clean because the warning disappeared. It is clean when trust has been rebuilt.