File Integrity

File Integrity

Use file-integrity reporting to find changes under WordPress plugins, mu-plugins, and themes. A changed file is a reason to investigate; it is not by itself proof of malware. This view does not replace a website backup.

Run and review a scan

You need permission to manage Awthy reporting.

1. Open Awthy → Reporting → Site changes.
2. In File changes, select Scan now.
3. Read the scan result before interpreting the rows. A complete result shows files checked and changes recorded.
4. Set Period, Root, and Change type for the question you are investigating, then apply the filters.
5. Open a file's timeline to compare its recorded changes. Use Review period evidence to inspect coverage.

For example, after an expected plugin update, filter to plugin changes and its update period. Check whether the changed files match that update. Investigate unexpected changes before removing or replacing anything.

What the result means

WordPress keeps bounded file metadata and content hashes. File bodies and generated diff bodies are not stored in the WordPress database. Changes can show before/after hashes and sizes when available; those values identify a change, not its full contents.

A partial scan does not prove untouched files are unchanged or missing files were deleted. Unreadable files, changing files, and scan limits can leave coverage incomplete. Correct the reported problem and run another scan.

Recovery and next steps

If a scan fails, note its safe error message and ask your hosting operator to check file access and server logs. Do not loosen permissions across the site merely to get a complete scan.

Use Known-threat detection for supported threat rules and WordPress Mutations for site changes observed through WordPress. Prepare a backup and review site restore before making destructive repairs.