[{"data":1,"prerenderedAt":31},["ShallowReactive",2],{"doc-en-hacked-website-plesk":3},{"path":4,"slug":5,"title":6,"description":7,"category":8,"subcategory":9,"icon":10,"date":11,"author":12,"order":13,"image":14,"tags":15,"keywords":21,"docGroup":28,"docGroupIcon":28,"link_fr":29,"bodyHtml":30},"\u002Fdocs\u002Fen\u002Fcloud\u002Fhebergement-web\u002Fhacked-website-plesk","hacked-website-plesk","What to Do If Your Website Is Hacked on Plesk","Respond to a hacked website on Winheberg Plesk web hosting, Imunify scanner, logs, WordPress integrity, restore, passwords and updates.","cloud","hebergement-web","tabler:file-text","2026-11-02","Winheberg",150,"\u002Fstatics\u002Fimages\u002Fdocs\u002Fen\u002Fhebergement-web\u002Fhacked-website-plesk.webp",[16,17,18,19,20],"Security","Malware","Imunify","Plesk","Web Hosting",[22,23,24,25,26,27],"hacked website","website malware","imunify","clean hacked site","hacked wordpress","website security","","\u002Fdocs\u002Fhebergement-web\u002Fsite-pirate-plesk","\u003Ch2>Context\u003C\u002Fh2>\n\u003Cp>A hacked website shows signs that are often subtle. Visitors redirected to ad or scam websites, unknown PHP files in your webspace, a Google warning in search results or email sent in bulk from your domain should all alert you.\u003C\u002Fp>\n\u003Cp>Most intrusions go through an outdated plugin or theme, or a weak password. On your \u003Ca href=\"https:\u002F\u002Fwinheberg.com\u002Fen\u002Fcloud\u002Fweb-hosting\">Winheberg web hosting\u003C\u002Fa>, Plesk gives you the tools to spot malicious files, understand how the attacker got in and bring your website back to a healthy state.\u003C\u002Fp>\n\u003Cp>This guide follows the order to respect, from diagnosis to cleanup and then protection.\u003C\u002Fp>\n\u003Cdiv class=\"markdown-alert markdown-alert-note\">\u003Cspan class=\"alert-icon\">\u003Csvg xmlns=\"http:\u002F\u002Fwww.w3.org\u002F2000\u002Fsvg\" width=\"16\" height=\"16\" viewBox=\"0 0 24 24\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\">\u003Ccircle cx=\"12\" cy=\"12\" r=\"10\"\u002F>\u003Cline x1=\"12\" y1=\"16\" x2=\"12\" y2=\"12\"\u002F>\u003Cline x1=\"12\" y1=\"8\" x2=\"12.01\" y2=\"8\"\u002F>\u003C\u002Fsvg>\u003C\u002Fspan>\u003Cdiv class=\"markdown-alert-body\">\u003Cp>The Winheberg Plesk panel is displayed in French. Menu, field and button names are quoted below exactly as they appear on screen, followed by their English meaning.\u003C\u002Fp>\n\u003C\u002Fdiv>\u003C\u002Fdiv>\n\u003Ch2>Prerequisites\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>A Winheberg web hosting plan with access to the Plesk panel\u003C\u002Fli>\n\u003Cli>The approximate time you noticed the problem\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cdiv class=\"markdown-alert markdown-alert-important\">\u003Cspan class=\"alert-icon\">\u003Csvg xmlns=\"http:\u002F\u002Fwww.w3.org\u002F2000\u002Fsvg\" width=\"16\" height=\"16\" viewBox=\"0 0 24 24\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\">\u003Cpath d=\"M12 22c5.523 0 10-4.477 10-10S17.523 2 12 2 2 6.477 2 12s4.477 10 10 10z\"\u002F>\u003Cpath d=\"M12 8v4\"\u002F>\u003Cpath d=\"M12 16h.01\"\u002F>\u003C\u002Fsvg>\u003C\u002Fspan>\u003Cdiv class=\"markdown-alert-body\">\u003Cp>Before deleting anything, create a backup of the current state of the website with our guide \u003Ca href=\"https:\u002F\u002Fwinheberg.com\u002Fen\u002Fdocs\u002Fhebergement-web\u002Fbackup-restore-website-plesk\">How to Back Up and Restore Your Website on Plesk\u003C\u002Fa> It keeps the traces useful for the investigation and protects you from a mistake.\u003C\u002Fp>\n\u003C\u002Fdiv>\u003C\u002Fdiv>\n\u003Ch2>1. Check the malware scanner\u003C\u002Fh2>\n\u003Cp>Open your domain from \u003Cstrong>Sites Web &amp; Domaines\u003C\u002Fstrong> (\u003Cem>Websites &amp; Domains\u003C\u002Fem>). In the \u003Cstrong>Tableau de bord\u003C\u002Fstrong> (\u003Cem>Dashboard\u003C\u002Fem>), \u003Cstrong>Sécurité\u003C\u002Fstrong> (\u003Cem>Security\u003C\u002Fem>) section, click \u003Cstrong>Imunify\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003Cimg src=\"\u002Fstatics\u002Fimages\u002Fdocs\u002Fen\u002Fhebergement-web\u002Fhacked-website-plesk-1793616260994-c641860a922433dd2694df9f.webp\" alt=\"Imunify malware scanner in Plesk with the list of malicious files\" width=\"800\" \u002F>\n\n\u003Cp>The \u003Cstrong>Malveillants\u003C\u002Fstrong> (\u003Cem>Malicious\u003C\u002Fem>) tab lists the files detected in your hosting, with their date in \u003Cstrong>Détecté\u003C\u002Fstrong> (\u003Cem>Detected\u003C\u002Fem>), the threat \u003Cstrong>Type\u003C\u002Fstrong>, the \u003Cstrong>Raison\u003C\u002Fstrong> (\u003Cem>Reason\u003C\u002Fem>) and the \u003Cstrong>Statut\u003C\u002Fstrong> (\u003Cem>Status\u003C\u002Fem>). The \u003Cstrong>Historique\u003C\u002Fstrong> (\u003Cem>History\u003C\u002Fem>) tab traces the actions already taken on these files.\u003C\u002Fp>\n\u003Cp>Note the path of the flagged files, it often points to the plugin or folder the attacker went through.\u003C\u002Fp>\n\u003Ch2>2. Trace the origin in the logs\u003C\u002Fh2>\n\u003Cp>Open the domain \u003Cstrong>Journaux\u003C\u002Fstrong> (\u003Cem>Logs\u003C\u002Fem>), \u003Cstrong>Outils Dévelop.\u003C\u002Fstrong> (\u003Cem>Dev Tools\u003C\u002Fem>) section of the \u003Cstrong>Tableau de bord\u003C\u002Fstrong>, and search the \u003Cstrong>Message\u003C\u002Fstrong> field for the names of the files flagged by Imunify.\u003C\u002Fp>\n\u003Cp>Lines of the \u003Cstrong>access\u003C\u002Fstrong> type show who called these files and when. A series of \u003Ccode>POST\u003C\u002Fcode> requests to an unknown PHP file, for instance in \u003Ccode>wp-content\u002Fuploads\u002F\u003C\u002Fcode>, most often reveals a backdoor. Reading the logs is detailed in our guide \u003Ca href=\"https:\u002F\u002Fwinheberg.com\u002Fen\u002Fdocs\u002Fhebergement-web\u002Fwebsite-error-logs-plesk\">How to Read the Error Logs of Your Website on Plesk\u003C\u002Fa>\u003C\u002Fp>\n\u003Ch2>3. Check WordPress integrity\u003C\u002Fh2>\n\u003Cp>For a WordPress website, open the \u003Cstrong>WordPress\u003C\u002Fstrong> tab of your domain and click \u003Cstrong>Vérifier l&#39;intégrité de WordPress\u003C\u002Fstrong> (\u003Cem>Verify WordPress integrity\u003C\u002Fem>). WP Toolkit compares the WordPress core files with those of the official version and flags the ones that were modified.\u003C\u002Fp>\n\u003Cimg src=\"\u002Fstatics\u002Fimages\u002Fdocs\u002Fen\u002Fhebergement-web\u002Fhacked-website-plesk-1793574219994-d00f1065337e22220a04d8b1.webp\" alt=\"WordPress website card in Plesk with Verify WordPress integrity\" width=\"665\" \u002F>\n\n\u003Cp>Take the opportunity to check the \u003Cstrong>Mises à jour\u003C\u002Fstrong> (\u003Cem>Updates\u003C\u002Fem>) block and the \u003Cstrong>Plug-ins\u003C\u002Fstrong> list, an abandoned or outdated plugin is the prime suspect.\u003C\u002Fp>\n\u003Ch2>4. Restore a clean backup\u003C\u002Fh2>\n\u003Cp>The safest way to get rid of an intrusion is to go back to an earlier backup. Open \u003Cstrong>Sauvegarder et restaurer\u003C\u002Fstrong> (\u003Cem>Back Up and Restore\u003C\u002Fem>), pick a backup dated before the first signs, and restore the \u003Cstrong>Sites\u003C\u002Fstrong> and the \u003Cstrong>Base de données\u003C\u002Fstrong> (\u003Cem>Database\u003C\u002Fem>).\u003C\u002Fp>\n\u003Cdiv class=\"markdown-alert markdown-alert-warning\">\u003Cspan class=\"alert-icon\">\u003Csvg xmlns=\"http:\u002F\u002Fwww.w3.org\u002F2000\u002Fsvg\" width=\"16\" height=\"16\" viewBox=\"0 0 24 24\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\">\u003Cpath d=\"M10.29 3.86L1.82 18a2 2 0 0 0 1.71 3h16.94a2 2 0 0 0 1.71-3L13.71 3.86a2 2 0 0 0-3.42 0z\"\u002F>\u003Cline x1=\"12\" y1=\"9\" x2=\"12\" y2=\"13\"\u002F>\u003Cline x1=\"12\" y1=\"17\" x2=\"12.01\" y2=\"17\"\u002F>\u003C\u002Fsvg>\u003C\u002Fspan>\u003Cdiv class=\"markdown-alert-body\">\u003Cp>A backup taken after the intrusion also contains the malicious files. Go back far enough, even if it means losing the content of the last few days, which you can enter again afterwards. Our automatic backups only go back over a rolling 7 days, so act fast or use a copy you downloaded.\u003C\u002Fp>\n\u003C\u002Fdiv>\u003C\u002Fdiv>\n\u003Cp>If no clean backup exists, delete the files flagged by Imunify, reinstall the core of your application and replace each plugin with its latest version downloaded from the official source.\u003C\u002Fp>\n\u003Ch2>5. Change every password\u003C\u002Fh2>\n\u003Cp>An attacker who gained access may have collected credentials. Change them all, once the website is clean.\u003C\u002Fp>\n\u003Cdiv class=\"md-table md-table--info md-table--striped\">\u003Cdiv class=\"md-table__caption\">Passwords to change\u003C\u002Fdiv>\u003Cdiv class=\"md-table__scroll\">\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Access\u003C\u002Fth>\n\u003Cth>Where to change it\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\u003Ctr>\n\u003Ctd>Plesk account\u003C\u002Ftd>\n\u003Ctd>Your profile menu, at the top of the panel\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>System user and FTP\u003C\u002Ftd>\n\u003Ctd>Domain \u003Cstrong>Infos de connexion\u003C\u002Fstrong> (\u003Cem>Connection Info\u003C\u002Fem>), pencil next to \u003Cstrong>Mot de passe\u003C\u002Fstrong> (\u003Cem>Password\u003C\u002Fem>), then \u003Cstrong>FTP\u003C\u002Fstrong> for additional accounts\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Databases\u003C\u002Ftd>\n\u003Ctd>\u003Cstrong>Bases de données\u003C\u002Fstrong>, \u003Cstrong>Gestion des utilisateurs\u003C\u002Fstrong> (\u003Cem>User Management\u003C\u002Fem>), then your website configuration with the new password\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Website administrators\u003C\u002Ftd>\n\u003Ctd>The profile of each administrator in your application\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Email addresses\u003C\u002Ftd>\n\u003Ctd>\u003Cstrong>Boîte mail\u003C\u002Fstrong> (\u003Cem>Mail\u003C\u002Fem>), by clicking each address\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\u003C\u002Ftable>\n\u003C\u002Fdiv>\u003C\u002Fdiv>\n\u003Ch2>6. Update and harden the website\u003C\u002Fh2>\n\u003Cp>Update your application, its plugins and its themes, then delete the ones you do not use. Also check that your domain uses PHP 8.2 or later in \u003Cstrong>Paramètres PHP\u003C\u002Fstrong> (\u003Cem>PHP Settings\u003C\u002Fem>), older versions no longer receive security fixes.\u003C\u002Fp>\n\u003Cp>In the \u003Cstrong>Sécurité\u003C\u002Fstrong> section of the \u003Cstrong>Tableau de bord\u003C\u002Fstrong>, the \u003Cstrong>Advisor\u003C\u002Fstrong> tool lists security recommendations suited to your subscription.\u003C\u002Fp>\n\u003Ch2>Troubleshooting\u003C\u002Fh2>\n\u003Ch3>❌ The website is hacked again after the cleanup\u003C\u002Fh3>\n\u003Cp>The entry point was not closed.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Look in the logs for the requests that precede the files coming back\u003C\u002Fli>\n\u003Cli>Check that no old FTP account or unknown administrator still exists\u003C\u002Fli>\n\u003Cli>Restore an older backup and update everything before putting the website back online\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>❌ Google shows &quot;This site may be hacked&quot;\u003C\u002Fh3>\n\u003Cp>The warning stays until Google checks the website again.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Add your website to Google Search Console, then open the section dedicated to security issues\u003C\u002Fli>\n\u003Cli>Once the cleanup is done, request a review from that same section\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>Best practices\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>Turn on automatic updates for your application and its plugins\u003C\u002Fli>\n\u003Cli>Keep regular backups, and a downloaded copy outside the server\u003C\u002Fli>\n\u003Cli>Use unique passwords and a password manager\u003C\u002Fli>\n\u003Cli>Delete the plugins, themes and accounts you no longer use\u003C\u002Fli>\n\u003Cli>Regularly check the Imunify \u003Cstrong>Malveillants\u003C\u002Fstrong> tab\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>Need help?\u003C\u002Fh2>\n\u003Cp>If you cannot clean your website, or if our team reported suspicious activity to you, open a ticket with our support from your \u003Ca href=\"https:\u002F\u002Fbilling.winheberg.com\">client area\u003C\u002Fa>, \u003Cstrong>Technical\u003C\u002Fstrong> department, filling in the \u003Cstrong>Related Product\u003C\u002Fstrong> field with the web hosting concerned. Mention the date of the first symptoms and the files flagged by Imunify.\u003C\u002Fp>\n\u003Cp>Your website is healthy again, and better protected than before 🔒\u003C\u002Fp>\n",1794526350728]