![]() |
VOOZH | about |
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.
Overview: The content below offers a comprehensive overview of Jetpack Scan, a powerful security scanning tool by Jetpack. It explains the features, benefits, and important details regarding the use of Jetpack Scan, including which plans include it, how to get started, the importance of server credentials, navigating the dashboard, frequency of scans, fixing threats, and privacy information. Users can learn about the types of threats detected, examples of threats, and how Jetpack Scan helps enhance the security of WordPress sites.
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.
Jetpack Scan is available to users who have purchased the Jetpack Scan, Jetpack Security, or Jetpack Complete plans. It is also the scan solution for any new Jetpack Security or Jetpack Complete purchase.
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.
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.
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.
You can reach the Jetpack Scan from your WP Admin dashboard by following these steps:
On the History page, you’ll see a list of all threats detected on the site in the past. They can be filtered by their fix/ignore status, and ignored threats can be fixed.
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.
Jetpack scans:
plugins, mu-plugins, themes, and uploads directories.wp-config.php.Scans occur daily or when manually triggered.
When Jetpack Scan detects a threat to your site, you have the following options:
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.
Jetpack Scan will check your WordPress installation to see if any core files have been changed or deleted. Generally, these files should never be changed, so please remember when working on your site. 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.
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.
Plugins that have known security vulnerabilities will be detected by Jetpack Scan. If a newer version has patched the threat, you can update the plugin with one click. We allow you to delete the plugin from your site if there is no newer version with a fix.
You’re always welcome to contact us if you have any questions about security threats or suspicious codes.
Currently, Jetpack Scan does not support multisite.
Please contact support. We’re happy to advise.
Jetpack Scan is deactivated by default and requires an upgrade to a paid solution (Jetpack Scan, Jetpack Security, or Jetpack Complete) to unlock/activate.
| 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 scanner and in the scan history). | Site Visitors None. |
| Data Synced (Read More) | |
| Site Owners / Users None. | Site Visitors None. |