Malware Center
Run, review, and act on server-wide malware findings.
1Overview
Malware Center aggregates approved scans and findings for hosting content. It helps administrators prioritize suspicious files while preserving account ownership.
2Before you begin
Administrator actions can affect multiple customer accounts and server services. This is a security-sensitive task; use the narrowest change that solves the verified issue.
3Step-by-step workflow
Open Malware Center, filter findings by account or domain, inspect the reported path and detection detail, then choose the supported remediation action or contact the account owner. Re-scan after remediation.
- Open Malware Center and choose the account, domain, or supported scan scope.
- Start a scan and wait for its final state instead of submitting the same location repeatedly.
- Filter results by account, date, path, or detection status.
- Open a finding and read the full file path, signature, and scan time.
- Compare suspicious files with a trusted application release or known-good backup.
- Back up affected material before using the supported quarantine, remediation, or removal action.
- Repair the entry point, vulnerable software, or stolen credential that allowed the infection.
- Re-scan and test the affected website before closing the incident.
4Practical example
Example: a suspicious PHP file in an uploads folder should be reviewed in the context of that website. A scan detection does not tell you which plugin or credential originally allowed the file to appear.
5Verify the result
Validate the outcome from the affected account or an independent client connection, not only from the administrator screen.
- Confirm the finding is resolved or deliberately marked as a reviewed false positive.
- Check the website and application logs after file removal or quarantine.
6Common problems and what to check
A scan cannot start: check the scanner service, signature status, and allowed scope.
A finding may be a false positive: preserve the file and review its origin before approving any exclusion.
A file returns after removal: investigate the application vulnerability and access credentials instead of deleting it repeatedly.
7Security, impact, and rollback
A detection is evidence, not automatic permission to delete customer data. Back up the affected files and confirm the finding before quarantine or removal.