[WordPress] 外掛分享: ShieldXen – Malware Scanner & Site Security Audit

首頁 › 外掛目錄 › ShieldXen – Malware Scanner & Site Security Audit
WordPress 外掛 ShieldXen – Malware Scanner & Site Security Audit 的封面圖片
全新外掛
安裝啟用
—
尚無評分
6 天前
最後更新
—
問題解決
WordPress 6.6+ PHP 7.4+ v1.0.0 上架:2026-11-16

外掛標籤

開發者團隊

⬇ 下載最新版 (v1.0.0) 或搜尋安裝

① 下載 ZIP → 後台「外掛 › 安裝外掛 › 上傳外掛」
② 後台搜尋「ShieldXen – Malware Scanner & Site Security Audit」→ 直接安裝(推薦)
📦 歷史版本下載

原文外掛簡介

ShieldXen checks your site from the inside and tells you, in plain words, what to fix first.
What it checks

Files. Compares WordPress, your plugins and your themes with the official copies, looks for malware signatures, PHP hidden in images or where it doesn’t belong, backups and logs anyone could download, and old copies of WordPress left in the site. For your own code, which has no official copy, it reports changes nobody declared.
The database. Scripts and spam hidden in posts, widgets and settings, administrators and plugins hidden from their screens, accounts and application passwords added behind your back, code stored in options, snippets and scheduled tasks, and triggers that recreate an attacker’s account.
Your own code. Plugins and themes that aren’t on wordpress.org or from a known vendor get quick checks for the mistakes attackers look for (open AJAX and REST handlers, SQL built from request data, unsafe uploads, secret keys in the code), as leads for a developer.
What visitors see. In full scans it reads the home page, the newest posts and pages, and the cart and checkout as a visitor gets them: scripts from new or blocklisted hosts, known malware campaigns such as fake CAPTCHA pages, and secret keys printed into the page source.
Updates and hardening. A PHP version that no longer gets security fixes, premium plugins whose own updater offers an update you haven’t installed, weak keys, open registration with a powerful role, error messages shown to visitors, administrators without 2FA, an over-privileged database user, files anyone can download, missing HTTPS and security headers, and more.

What you get

Fix first. Signs of compromise and the most severe problems go to the top.
A grade you can trust. A site with an open critical problem can’t score better than D.
Every finding explained. Why it matters, how to fix it, and the evidence the check saw, with secrets masked.
A report to share. A print-friendly page of the grade and every open finding, to print or save as PDF.
Email alerts. Optionally, an email when a scan finds a new critical or high problem.
WP-CLI. Run scans and list findings from the command line.

How it works
Nothing runs on your site’s front end. Scans run in short steps from the dashboard, WP-Cron or WP-CLI (wp shieldxen scan), so they work on shared hosting. Every feature is in this plugin, free. There is no account to create.
ShieldXen reports problems. It doesn’t remove malware, restore files or block attacks.
A clean scan isn’t proof a site is clean. The dashboard lists what a scan can’t see.
External services
This plugin connects only to wordpress.org, and only during full and file scans:

api.wordpress.org, for the checksums of the WordPress version you run, to find changed core files. It sends the version and the site’s language. Terms and privacy: https://wordpress.org/about/privacy/
downloads.wordpress.org, for the checksum file and the release zip of each installed plugin and theme that comes from wordpress.org, to find changed files. It sends the plugin’s or theme’s name and version, and only when its files changed since the last check or a week has passed. A zip is downloaded to a temporary file, read without being unpacked, and deleted; each version is downloaded once. Only plugins and themes that WordPress’s own update check found on wordpress.org are asked about. Never sent: what you marked as your own code or a vendor’s, and plugins that declare they update from somewhere else (an “Update URI”). Terms and privacy: https://wordpress.org/about/privacy/

The malware signatures and the other detection data ship inside the plugin; nothing is downloaded to update them. No request follows a redirect, and every one checks the server’s certificate. The plugin also requests pages and files of your own site (the HTTP and live page checks), which stay between the site and itself. When the site’s own certificate fails, those requests report it as a finding and go on checking the pages without verifying it; requests to other servers never do.
Source code
Everything in the plugin is its readable source, including the detection data in data/ (JSON), except the admin screens’ built script and styles in assets/build. Their full readable source ships beside them, in assets/src (React, with @wordpress/scripts). To rebuild assets/build from it, run these in the plugin’s folder: npm install, then npm run build.

延伸相關外掛

文章
Filter
Mastodon