A malware incident is easier to handle when the checklist already exists. The goal is not to become a security analyst overnight. It is to avoid the three common mistakes: wiping evidence before anyone understands the infection, removing files without closing the entry point, and restoring service without verifying that the site is actually clean.
This checklist is written for a business owner, marketing manager or operations lead coordinating with a developer or hosting provider. Work through it in order. If personal data or payment data may be involved, bring in legal or privacy advice early.
Phase 1: preserve evidence before you touch anything
- Take a full backup of files and database, and store it offline.
- Export server, application and access logs before they rotate.
- Record the first symptom, the time and the person who noticed it.
- Do not delete suspicious files, users or database rows yet.
- Take screenshots of Google warnings, browser redirects and admin notices.
Phase 2: contain the incident
- Put the site in maintenance mode or take it offline if it is actively serving malware.
- Revoke active sessions and rotate passwords for hosting, CMS, database, FTP/SFTP and DNS.
- Enable MFA on hosting, domain registrar, CMS administrators and email.
- Remove unknown administrator users and unused accounts.
- Disable file editing in the CMS control panel and revoke unused API keys.
- Tell the hosting provider; ask for their logs and any account-level compromise details.
Phase 3: investigate the entry point
- Check the CMS core, theme and plugin versions against the latest releases.
- Review file modification times around the first symptom.
- Compare core files with a clean install or a trusted checksum source.
- Search for unexpected scheduled tasks, cron jobs, redirects and admin users.
- Inspect the database for injected scripts, hidden links and modified options.
- Check for stolen hosting or FTP credentials, especially after staff or agency changes.
Phase 4: remove the infection
- Remove or replace infected files. Reinstall core, theme and plugins from official sources.
- Remove backdoors, webshells and unknown files, not just the visible payload.
- Clean database injections and restore modified rows from a known-good source where possible.
- Remove unused plugins, themes and users.
- Do not restore an old backup without confirming it predates the infection.
- Run a second scan with a different tool to catch what the first scan missed.
Phase 5: harden the site
- Patch the entry point and every other outdated component.
- Set least-privilege file permissions and disable directory listing.
- Add a web application firewall or managed rules where appropriate.
- Limit login attempts and require strong passwords or passkeys for administrators.
- Remove unnecessary XML-RPC, REST endpoints and debug modes.
- Configure daily backups with an off-site copy and a tested restore.
Phase 6: recover and verify
- Test forms, checkout, email, search and key user journeys.
- Request a Google review if Search Console shows a security issue.
- Submit a fresh sitemap and monitor indexing for the next 30 days.
- Monitor logs and file integrity daily for the first two weeks, then weekly.
- Write a short incident report: cause, scope, actions, evidence and remaining risk.
Phase 7: prevent the next incident
- Set a monthly update window for core, theme and plugins.
- Remove abandoned plugins and unused integrations.
- Use MFA everywhere and a password manager for shared credentials.
- Review administrator access quarterly and after every staff change.
- Run a quarterly backup restore test, not just a backup.
- Keep a one-page incident contact tree: hosting, developer, domain, payment provider and legal.
The 30-second triage
If you only have five minutes, do these four things: take a backup, revoke sessions and rotate passwords, enable MFA, and call the hosting provider. Then stop changing files until someone has preserved the evidence.
Roles and timing
A cleanup moves faster when the roles are clear. The business owner approves downtime and customer communication. The technical lead owns containment, investigation and removal. The hosting provider supplies logs and account-level evidence. The marketing lead owns Search Console, sitemap and customer-facing notices. If one person is doing all four jobs, the cleanup will be slower and the evidence will be thinner.
Typical timing for a small business site is one day for triage and containment, one to three days for removal and verification, and one to two weeks for hardening, Search Console review and monitoring. A complex ecommerce site with payment skimming or a compromised server can take longer. Treat any promise of a one-hour fix as a red flag.
What good evidence looks like
- A timeline from first symptom to containment, with the actions and the person responsible.
- The entry point, or a documented explanation of why it could not be determined.
- A list of infected files, database changes, users and scheduled tasks.
- Before-and-after scans from two different tools.
- Evidence that forms, checkout and email still work after cleanup.
- A Search Console review request and the date it was submitted.
- A 30-day monitoring plan with an owner and an alert channel.
After the cleanup: 30 days of monitoring
The first month is when reinfection shows up. Check file integrity and logs daily for two weeks, then weekly. Watch Search Console for new security issues, keep an eye on checkout and form submissions, and review administrator accounts. If the site is reinfected, do not repeat the same removal; reopen the investigation and look for the missed entry point.
Where this fits in our work
For a scoped cleanup and hardening plan, start with Managed Technology & Cybersecurity. The pricing page explains how we scope work. For the cost drivers, read website malware cleanup cost in Bangladesh, and for the business impact read what malware actually costs a small business.
Sources
- Google Search Central, "Hacked sites", accessed 16 November 2026.
- NIST SP 800-83 Rev. 1, Guide to Malware Incident Prevention and Handling, accessed 16 November 2026.
- WordPress Developer Resources, "Hardening WordPress", accessed 16 November 2026.
- OWASP Top 10, accessed 16 November 2026.
Responses (0)
No comments yet. Add the first one below.
Leave a response
Your email address will not be published. Required fields are marked *.