內容簡介
此外掛會搜尋你網站上的檔案，以及你資料庫中的文章和評論表格，尋找任何可疑的項目。它還會檢查你的作用中外掛清單是否有異常的檔案名稱。
它不會刪除任何東西，這部分需要使用者自行處理。
Exploit Scanner 的最新 MD5 hash 值：
17e2ccfc834d691bc68cc5c64f9bed89 exploit-scanner.php (1.5.2)
1d5f9d6220fe159cd44cb70a998a1cd7 hashes-4.6.php
fbdf61c17f65094c8e331e1e364acf68 hashes-4.6.1.php
477d128d84802e3470cec408424a8de3 hashes-4.7.php
d53210f999847fbd6f5a2ecac0ad42f2 hashes-4.7.5.php
Exploit Scanner 的最新 SHA1 hash 值：
1decc1e47a53d1cab9e8f1ef15b31682198367ee exploit-scanner.php (1.5.2)
5cec64380a2acdc876fd22fbbbbf8c335df1ed3f hashes-4.6.php
99d9e7be23a350f3d1962d0f41e7b4e28c00841e hashes-4.6.1.php
1eeab377a1afc6d776827a063678d2461b29e71d hashes-4.7.php
8c890a6af26bb74e9d17e5d2b21d6be27764da45 hashes-4.7.5.php
更多資訊請參閱 Exploit Scanner 的首頁。
解讀結果
這個掃描器可能會發現假陽性 (也就是不包含惡意程式碼的檔案)。但還是要以謹慎為主，如果不確定，請詢問支援論壇、下載外掛的最新版本、搜尋類似狀況等等。當掃描器發現以下情況時，應該要格外注意：
在未知的外部連結周圍找到配對項目
在修改過的核心檔案或 wp-config.php 檔案中找到 base64 編碼的文字
列出額外的管理員帳戶
在文章中發現你沒有放置的內容
了解三個不同的結果等級：
危急：通常是駭客攻擊的強烈跡象 (但不是最終證據)
警告：這些結果在無罪情況下更常見，但仍應謹慎處理
備註：最低優先級，顯示常用於合法程式碼或忽略檔案等事件的結果
救命啊！我被駭了！
請遵從 Codex 提供的指南：
Codex: FAQ – My site was hacked
Codex: Hardening WordPress
請確認更改所有與 WordPress 相關的密碼 (網站、FTP、MySQL 等等)。定期備份 (手動或使用外掛) 非常有用；如果您發現您的網站被駭了，您可以輕鬆從乾淨的備份和新的檔案中恢復您的網站，當然，也需要使用新的一組密碼。
更新
插件的更新將通過此處、Holy Shmoly! 和 WordPress Exploit Scanner 頁面上的最新版本連結發佈。
其他語言
對於使用其他語言版本的 WordPress 的使用者，一些檔案 hash 值可能是不正確的，因為某些字符串必須硬編碼為它們翻譯後的形式。以下是由社群其他成員提供的其他語言版本的檔案 hash 值：
Japa
外掛標籤
開發者團隊
📦 歷史版本下載
原文外掛簡介
This plugin searches the files on your website, and the posts and comments tables of your database for anything suspicious. It also examines your list of active plugins for unusual filenames.
It does not remove anything. That is left to the user to do.
Latest MD5 hash values for Exploit Scanner:
17e2ccfc834d691bc68cc5c64f9bed89 exploit-scanner.php (1.5.2)
1d5f9d6220fe159cd44cb70a998a1cd7 hashes-4.6.php
fbdf61c17f65094c8e331e1e364acf68 hashes-4.6.1.php
477d128d84802e3470cec408424a8de3 hashes-4.7.php
d53210f999847fbd6f5a2ecac0ad42f2 hashes-4.7.5.php
Latest SHA1 hash values for Exploit Scanner:
1decc1e47a53d1cab9e8f1ef15b31682198367ee exploit-scanner.php (1.5.2)
5cec64380a2acdc876fd22fbbbbf8c335df1ed3f hashes-4.6.php
99d9e7be23a350f3d1962d0f41e7b4e28c00841e hashes-4.6.1.php
1eeab377a1afc6d776827a063678d2461b29e71d hashes-4.7.php
8c890a6af26bb74e9d17e5d2b21d6be27764da45 hashes-4.7.5.php
See the Exploit Scanner homepage for further information.
Interpreting the Results
It is likely that this scanner will find false positives (i.e. files which do not contain malicious code). However, it is best to err
on the side of caution; if you are unsure then ask in the Support Forums,
download a fresh copy of a plugin, search the Internet for similar situations, et cetera. You should be most concerned if the scanner is:
making matches around unknown external links; finding base64 encoded text in modified core files or the wp-config.php file;
listing extra admin accounts; or finding content in posts which you did not put there.
Understanding the three different result levels:
Severe: results that are often strong indicators of a hack (though they are not definitive proof)
Warning: these results are more commonly found in innocent circumstances than Severe matches, but they should still be treated with caution
Note: lowest priority, showing results that are very commonly used in legitimate code or notifications about events such as skipped files
Help! I think I have been hacked!
Follow the guides from the Codex:
Codex: FAQ – My site was hacked
Codex: Hardening WordPress
Ensure that you change all of your WordPress related passwords (site, FTP, MySQL, etc.). A regular backup routine
(either manual or plugin powered) is extremely useful; if you ever find that your site has been hacked you can easily restore your site from
a clean backup and fresh set of files and, of course, use a new set of passwords.
Updates
Updates to the plugin will be posted here, to Holy Shmoly! and the WordPress Exploit Scanner page will always link to the newest version.
Other Languages
Unfortunately for people using WordPress versions for other locales some of the file hashes may be incorrect as some strings have to be hardcoded in their translated form. Here are some file hashes for WordPress in other languagues provided separately by other members of the community:
Japanese – thanks to Naoko
German – thanks to Robert Wetzlmayr
The hash files should only be declaring an array called $filehashes and the majority of the hashes should still be the same.
