Jetpack Scan
Last updated:
You can review security scan results in one centralized location, fix problems, and restore backups. If Jetpack does notice a problem, you’ll receive an instant email alert. You can repair the majority of security threats with just one click and get back to running your business.
Take a look at all the security features Jetpack offers.
Important: Jetpack Scan is not intended to be a service to clean up already hacked or malware-infected sites. While Jetpack Scan can fix some hacked files after purchase, we do rely on the site not being infected at the time of purchase and having a clean version to compare any changed files to. In that case, we suggest following this guide to cleaning a hacked site.
Which Plans Include Jetpack Scan?
Jetpack Scan is available to users who have purchased the Jetpack Scan, Jetpack Pro, or Jetpack Complete plans. Existing Jetpack Security subscriptions retain their included Scan features.
Note: Once the site is connected to Jetpack Scan, your site will remain on the Jetpack Scan solution, even if you change or add a Jetpack plan or move your site to a new host.
Getting Started
Jetpack Scan is activated as soon as your purchase is complete, and your first scan is kicked off immediately.
Note: In order for Jetpack Scan to scan a website, it needs to be able to create files in the /jetpack-temp/ directory (which is located in the root of the site alongside /wp-content/ and /wp-includes/. It writes a temporary helper file to this directory during the scan and removes it after the scan is complete.
If your site is hosted on a server that prevents files from being changed, you will need to work with your host to ensure that Jetpack is able to write files to the /jetpack-temp/ directory.
Adding Server Credentials to Jetpack Scan
Jetpack Scan can check your site for malware without requiring server credentials. You can also resolve detected threats using one-click (auto) fixes without credentials, as long as you’re using Jetpack Protect v4.2 or higher.
However, providing server credentials (like SSH, SFTP, or FTP) can make scans faster and more reliable.
To learn how to securely add remote access credentials, see SSH, SFTP, FTPS, and FTP Credentials guide.
On a self-hosted site with Jetpack 16.4 or later, you can also add or update credentials from WP Admin. Go to Jetpack → Protect → Settings and click Add server credentials (or Manage server credentials) in the Scan card. Your site’s settings in Jetpack Cloud open in a new tab.
Find Scan in WP Admin
On a self-hosted site with Jetpack 16.4 or later, Scan lives on the Protect page in WP Admin, along with the firewall, Login protection, and Downtime monitoring. To find it:
- In WP Admin, go to Jetpack → Protect.
- The Overview tab opens first. Its Scan results card shows whether your site is clear, or lists the threats Scan found, with the time of the last scan.
- To start a new scan, click Scan site at the top of the page. You can leave the page while it runs. The scan carries on.
- With a Scan plan, your site is scanned automatically every day. Without one, the card checks for known vulnerabilities automatically every day. Either way, the card shows when the last scan ran.
If a scan doesn’t finish, the Scan results card shows Your last scan didn’t complete and “We can’t confirm your site is free of threats until a scan finishes.” See Troubleshoot Jetpack Scan.
The History tab lists every threat found on your site in the past. Switch between the Fixed and Ignored views. You can unignore an ignored threat from there.
You can also review scan results in Jetpack Cloud. On sites hosted on WordPress.com, and on Jetpack versions before 16.4, click Scan in the Jetpack menu in WP Admin to open the Scan page in Jetpack Cloud, with its Scanner and History views. If the Jetpack Protect plugin is active, Jetpack → Protect opens the plugin’s page instead.
Don’t have a Scan plan? The Protect page still checks WordPress, your plugins, and your themes for known vulnerabilities once a day, for free. You’ll see those results in the same Scan results card, along with what Scan adds: malware scanning of every file, one-click fixes, and scan history.
How Jetpack Scan Works
Once a scan completes, you will receive a notification if any threats are found. These notifications will be in WP Admin, via email, and on your WordPress.com dashboard.
If your site is hosted on WordPress.com, email notifications for security threats are not sent. WordPress.com handles threat remediation automatically in the background, so manual action is not required.
What data is scanned?
Jetpack scans:
- All files in the
plugins,mu-plugins,themes, anduploadsdirectories. - Select files from your WordPress root directory, like
wp-config.php. - Other select files inside the wp-content directory.
What data is not scanned?
- Jetpack does not scan your site’s database.
How often do scans occur?
Scans occur daily or when manually triggered.
How do I fix threats?
When Jetpack Scan detects a threat to your site, you have the following options:
- Most threats come with a one-click fix. In the Scan results card, click Auto-fix on the threat’s row.
- Click “View” on a threat (or the threat itself) to open Threat details, which explains what Jetpack found and how to resolve it. From there you can click Auto-fix it or “Ignore it.
- The ⋮ menu on each row has the other actions that apply, such as Delete plugin, View on WordPress.org, and Ignore.
- To ignore several threats at once, select their checkboxes (or Select all) and click Ignore.
If the fix deletes a plugin or theme, Jetpack asks you to confirm first. Read the warning: deleting an active plugin or theme may break your site, so deactivate it and check your site before you go on. Then type the plugin or theme’s slug in the field and click “Confirm deletion“.
Fixed and ignored threats move to the History tab.
However, sometimes a website can get hacked more severely, meaning an auto fix (one-click fix) by Jetpack Scan is impossible. In that case, we suggest following this guide to cleaning a hacked site. It will help guide you through identifying and cleaning up a hacked site and strengthening the site’s security to help prevent future hacks.
Examples of Threats that Jetpack Scan May Find
Outdated or insecure plugins and themes
Jetpack Scan detects plugins and themes that have known security vulnerabilities. If a newer version has patched the threat, you can update the plugin or theme with one click. If no newer version contains a fix, you can delete it from your site.
You’re always welcome to contact us if you have any questions about security threats or suspicious codes.
Understanding the version number in a threat alert
When Jetpack Scan flags a vulnerable plugin or theme, the version in the alert is the version Scan detected installed on your site. An alert looks like this:
Vulnerable Plugin: PluginName (version 7.4.2)
That number is the installed version Scan recorded. It is not the version in which the vulnerability was discovered.
The threat details separately list the affected version range from the vulnerability advisory (also called the security advisory or disclosure), written as a comparison such as ≤ 7.4.2, which means every version up to and including 7.4.2 is affected.
A version comparison on its own does not tell you whether your site is at risk, so do not assume a newer version protects you. Jetpack Scan flags a plugin or theme based on its advisory in WPScan, the vulnerability database behind Jetpack Scan. If the advisory still lists the vulnerability as unfixed, Scan keeps flagging newer versions too, including the latest one.
If you’ve updated the plugin or theme and Scan still flags it, contact the plugin or theme developer and share the WPScan advisory with them. To find it, open the threat’s Threat details and click the Learn more link in the What did Jetpack find? section. The developer works with the source that reported the vulnerability to get it marked as fixed in the advisory. Once the advisory is updated, the alert clears.
Running a new scan does not clear the alert while the advisory lists the vulnerability as unfixed. We can’t change the advisory’s record either, so the developer is the right contact. You do not need to deactivate or roll back anything, or check the changelog yourself, based on the version numbers alone.
Changes to Core WordPress Files
Jetpack Scan will check your WordPress installation to see if any core files have been changed or deleted. Generally, WordPress core files should never be changed. WordPress functionality can and should be altered by using plugins and themes instead.
If you didn’t make the changes to your core WordPress files, you should consider the files suspicious and consider replacing them. You can always contact us if you’re unsure of the changes you see.
Other Vulnerabilities
Web-based shells give an attacker full access to your server — allowing them to execute malicious code, delete files, make changes to your database, and many more dangerous things.
Shells are usually found in files, and they can be removed by deleting any infected files from your server and replacing them with a clean version from your backup.
Reporting False Positives
A false positive is a threat alert for a plugin, theme, or file that isn’t actually vulnerable or malicious.
If Jetpack Scan still flags a plugin or theme after you update it, its WPScan advisory may list the vulnerability as unfixed. Contact the plugin or theme developer about that alert. See Understanding the version number in a threat alert. For any other alert you think is a mistake, contact us and we’ll check it for you.
Multisite
Currently, Jetpack Scan does not support multisite.
Still need help?
Please contact support. We’re happy to advise.
Privacy Information
Jetpack Scan is deactivated by default and requires an upgrade to a paid solution (Jetpack Scan, Jetpack Pro, or Jetpack Complete) to unlock/activate. Existing Jetpack Security subscriptions also retain access.
| Data Used | |
|---|---|
| Site Owners / Users We currently scan the following data: files in your plugins, themes, and uploads directories, and select files from your WordPress root directory and `wp-content` directory. This includes all WordPress’s unique and irreplaceable data and everything properly integrated into the WordPress installation. In addition to the data we scan, we also use (and store) your server access credentials (if provided): SSH and/or FTP/SFTP. These credentials are explicitly provided by you when activating Jetpack Scan. For feature usage tracking (detailed below): IP address, WordPress.com user ID, WordPress.com username, WordPress.com-connected site ID, user agent, referring URL, timestamp of event, browser language, country code, and user site count. We may also use scanned content to improve our performance but do not otherwise store it long-term. | Site Visitors None. |
| Activity Tracked | |
| Site Owners / Users We track several events around the usage of this feature: requests to view threats, fix threats, run a scan, and click on the header of a threat (in the scan results and in the scan history). | Site Visitors None. |
| Data Synced (Read More) | |
| Site Owners / Users None. | Site Visitors None. |