[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fq2I0SbXfrfGCgU-KiZQqixcwVAORB9shHBh0fnlnYt0":3},{"slug":4,"name":4,"version":5,"author":6,"author_profile":7,"description":8,"short_description":9,"active_installs":10,"downloaded":11,"rating":12,"num_ratings":12,"last_updated":13,"tested_up_to":14,"requires_at_least":15,"requires_php":16,"tags":17,"homepage":23,"download_link":24,"security_score":25,"vuln_count":12,"unpatched_count":12,"last_vuln_date":26,"fetched_at":27,"vulnerabilities":28,"developer":29,"crawl_stats":26,"alternatives":36,"analysis":140,"fingerprints":349},"dpabadbotwp","1.27 [20200927]","peter achutha","https:\u002F\u002Fprofiles.wordpress.org\u002Fpeter-achutha\u002F","\u003Cp>The Bad Bot Exterminator Pro is a php program that was developed to block hacker attacks on WordPress websites. Please visit the website at https:\u002F\u002Fwww.drpeterscode.com for more details on the Bad bot Exterminator that blocks hackers, stops brute force login attempts and defends against ddos attacks.\u003C\u002Fp>\n\u003Cp>As of 2018 there are two versions of the Bad Bot Exterminator – the Free Version and the Pro Version which is within the budget of most people. There have been many improvements over the last 5.5 years and is much easier to use. The Free version has been discontinued.\u003C\u002Fp>\n\u003Cp>This plugin, dpabadbotwp works with both the Bad Bot Exterminator Pro & Free versions. The Bad Bot Exterminator is a firewall to protect your WordPress website and is not a plugin but an independent PHP program that runs in parallel with WordPress.\u003C\u002Fp>\n\u003Cp>With the Bad Bot Exterminator\u003Cbr \u002F>\ni. you can lock up your WordPress site so that no one can login to your site.\u003Cbr \u002F>\nii. will track and record every visitor and decides who should be allowed to access your website. It tries to block hackers, bad bots, scrappers, crawlers, spiders, … It can block by IP address or by name of web crawler (in Lenient mode).\u003C\u002Fp>\n\u003Cp>This WordPress plugin, dpaBadBotWP was developed to tell the Bad Bot Exterminator when you are working on your WordPress site and allows you to carry on working by sending your IP address to Bad Bot Exterminator and thereby allowing you unlimited access to your website. By its self this plugin will not be useful if you have not a installed Bad Bot Exterminator.\u003C\u002Fp>\n\u003Cp>It now stops automatic WordPress core updates so that the Bad Bot Exterminator will not be erased.\u003C\u002Fp>\n\u003Cp>Do visit our site https:\u002F\u002Fwww.drpeterscode.com\u002Findex.php for more information on the Bad Bot Exterminator\u003C\u002Fp>\n\u003Ch3>1.01\u003C\u002Fh3>\n\u003Cp>Previous version forgot to check ip address when logged into WordPress control panel. This version corrects that. The moment you are logged in, your current IP address is sent to dpaBadBot.\u003C\u002Fp>\n\u003Ch3>1.02\u003C\u002Fh3>\n\u003Cp>Added a better description of products offered by Software Propulsion with links to respective websites\u003C\u002Fp>\n\u003Ch3>1.03\u003C\u002Fh3>\n\u003Cp>Changed all file names to lower case so that they will be compatible with all servers. If you are upgrading and the plugin has problems accessing files, DELETE this plugin and reinstall the plugin.\u003C\u002Fp>\n\u003Ch3>1.04\u003C\u002Fh3>\n\u003Cp>dpaBadBot PHP program was upgraded to allow you to preview your edited posts. So this plugin had extra security feature added to work with these dpaBadBot upgrades.\u003C\u002Fp>\n\u003Ch3>1.05\u003C\u002Fh3>\n\u003Cp>Removed the check for logout as not a good idea.\u003C\u002Fp>\n\u003Ch3>1.06\u003C\u002Fh3>\n\u003Cp>Changed which ip address is saved. Only latest IP address is saved and all older one’s are deleted.\u003C\u002Fp>\n\u003Ch3>1.07\u003C\u002Fh3>\n\u003Cp>Added multiuser tracking. This version to be used with version 1.06 or later or the Bad Bot Exterminator.\u003C\u002Fp>\n\u003Ch3>1.08\u003C\u002Fh3>\n\u003Cp>Stops automatic WordPress core updates by setting filter ‘auto_update_core’ to ‘__return_false’.\u003C\u002Fp>\n\u003Ch3>1.09\u003C\u002Fh3>\n\u003Cp>Made the PHP code more compatible with the WordPress style by using the debug setting in wp-config.php\u003C\u002Fp>\n\u003Ch3>1.10\u003C\u002Fh3>\n\u003Cp>Corrected some bugs. The directory name can now end with or without ‘\u002F’.\u003C\u002Fp>\n\u003Ch3>1.11\u003C\u002Fh3>\n\u003Cp>Undid some of the upgrades in 1.09 to make it less prone to spurios memory problems.\u003C\u002Fp>\n\u003Ch3>1.12\u003C\u002Fh3>\n\u003Cp>Made some code more compatible with WordPress and checked if file existed.\u003C\u002Fp>\n\u003Ch3>1.13\u003C\u002Fh3>\n\u003Cp>Found out that when you upgrade any plugin, WordPress will delete the existing plugin before downloading the upgrade version. Since this plugin saves all settings in the plugin directory all settings were lost upon upgrading. With version 1.13 a separate directory is created …\u002Fwp-contents\u002Fplugins\u002Fdpabadbotwpdata\u002F and all settings are saved in the altrnative sub-directory. Thus even after upgrading the original seetings are still available.\u003C\u002Fp>\n\u003Cp>Changed all variable names to begin with $spmywp_.\u003C\u002Fp>\n\u003Ch3>1.14\u003C\u002Fh3>\n\u003Cp>changed permission of …\u002Fwp-content\u002Fplugins\u002Fdpabadbotwpdata\u002F sub-directory to 0775 & stop recording visitors not logged in\u003C\u002Fp>\n\u003Ch3>1.15\u003C\u002Fh3>\n\u003Cp>added display of memory in MB too.\u003C\u002Fp>\n\u003Ch3>1.16\u003C\u002Fh3>\n\u003Cp>corrected the link to two other websites.\u003C\u002Fp>\n\u003Ch3>1.17\u003C\u002Fh3>\n\u003Cp>Added display ID and username of those who logged in and moved data directory to \u002Fuploads\u002F directory in line with WordPress standard. As of 2017 March 09, it shows which pages, posts or WP files were accessed. This if for you to look at who logged in and what they did to your copy of WordPress.\u003C\u002Fp>\n\u003Ch3>1.18\u003C\u002Fh3>\n\u003Cp>This plugin now tracks which pages, posts or WP files were accessed. This if for you to look at who logged in and what they did to your copy of WordPress.\u003C\u002Fp>\n\u003Ch3>1.19\u003C\u002Fh3>\n\u003Cp>Version 1.18 had a array assigned wrongly. Its fixed with this version. The table showing who logged and where they went was corrected.\u003C\u002Fp>\n\u003Ch3>1.20\u003C\u002Fh3>\n\u003Cp>Version 1.19 had a searched file name wrong. Its corrected.\u003C\u002Fp>\n\u003Ch3>1.21\u003C\u002Fh3>\n\u003Cp>Removed session start as it was closing the Bad Bot Exterminator when logging out of WordPress. Changed the comments.\u003C\u002Fp>\n\u003Ch3>1.22\u003C\u002Fh3>\n\u003Cp>Tracing of pages added. Removed ‘\u002F’ from data sent to The Bad Bot Exterminator.\u003C\u002Fp>\n\u003Ch3>1.23\u003C\u002Fh3>\n\u003Cp>Tried to improve PHP code speed \u002F effeciency. Declared undefined variables. Added Speed Check for WordPress webpages through the Bad Bot Exterminator Pro. Changed all links to new website at https:\u002F\u002Fwww.drpeterscode.com\u003C\u002Fp>\n\u003Ch3>1.24\u003C\u002Fh3>\n\u003Cp>added .htaccess file to uploads directory\u003C\u002Fp>\n\u003Ch3>1.25\u003C\u002Fh3>\n\u003Cp>added code to generate sitemap data\u003C\u002Fp>\n\u003Ch3>1.26\u003C\u002Fh3>\n\u003Cp>correcter variable name is php shutdown function and improved speed test\u003C\u002Fp>\n\u003Ch3>1.27\u003C\u002Fh3>\n\u003Cp>corrected detection of undefined array\u003C\u002Fp>\n","This plugin, dpaBadBotWP, automatically tells Bad Bot Exterminator firewall software, your current IP address and you will not be blocked from working …",10,3570,0,"2020-09-27T08:27:00.000Z","5.5.18","3.9.1","",[18,19,20,21,22],"bad-bot","block-hackers","brute-force-login","hack","security","https:\u002F\u002Fwww.drpeterscode.com\u002Fbad-bot-exterminator-protects-wordpress-sites-from-hackers-cyber-ddos-dos-attacks.php","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdpabadbotwp.zip",85,null,"2026-03-15T15:16:48.613Z",[],{"slug":30,"display_name":6,"profile_url":7,"plugin_count":31,"total_installs":32,"avg_security_score":25,"avg_patch_time_days":33,"trust_score":34,"computed_at":35},"peter-achutha",2,40,30,84,"2026-04-04T03:48:30.093Z",[37,62,81,98,119],{"slug":38,"name":39,"version":40,"author":41,"author_profile":42,"description":43,"short_description":44,"active_installs":45,"downloaded":46,"rating":47,"num_ratings":48,"last_updated":49,"tested_up_to":50,"requires_at_least":51,"requires_php":52,"tags":53,"homepage":57,"download_link":58,"security_score":59,"vuln_count":60,"unpatched_count":12,"last_vuln_date":61,"fetched_at":27},"block-wp-login","Block wp-login","1.5.5","Oliver Campion","https:\u002F\u002Fprofiles.wordpress.org\u002Fdomainsupport\u002F","\u003Ch4>Block Access to wp-login.php\u003C\u002Fh4>\n\u003Cp>This plugin does the following:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Locates wp-login.php in your WordPress installation and duplicates it\u003C\u002Fli>\n\u003Cli>Locates .htaccess and inserts lines to block the default wp-login.php and creates a new secret address to use for legitimate login\u003C\u002Fli>\n\u003Cli>Will email the site admin if an administrator signs in with an un-recognised IP address\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>When installed your server will return “403 Forbidden“ when attempts are made to access the default wp-login.php file. This has two benefits; it prevents hackers from using brute force methods to hack your website and it reduces the load on the server when such brute force attacks are launched on your site as WordPress isn’t run at all.\u003C\u002Fp>\n\u003Cp>Please note, this plugin uses .htaccess so is only compatible with Apache web servers, it is not compatible with Nginx web servers.\u003C\u002Fp>\n","This plugin completely blocks access to wp-login.php and creates a new secret login URL",600,19911,94,9,"2025-12-04T12:47:00.000Z","6.9.4","3.5.0","5.6",[19,54,55,22,56],"login-security","secure","security-plugin","https:\u002F\u002Fwebd.uk\u002Fsupport\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fblock-wp-login.1.5.5.zip",99,1,"2019-06-27 00:00:00",{"slug":63,"name":64,"version":65,"author":66,"author_profile":67,"description":68,"short_description":69,"active_installs":70,"downloaded":71,"rating":72,"num_ratings":60,"last_updated":73,"tested_up_to":74,"requires_at_least":75,"requires_php":76,"tags":77,"homepage":79,"download_link":80,"security_score":72,"vuln_count":12,"unpatched_count":12,"last_vuln_date":26,"fetched_at":27},"guardiankey","GuardianKey","5.7","gbernardes","https:\u002F\u002Fprofiles.wordpress.org\u002Fgbernardes\u002F","\u003Cp>GuardianKey is a service to protect systems in real-time against authentication attacks. It implements GK Auth Security for login protection and GKTinc dissuasion challenges, helping detect and block malicious accesses, and notify the legitimate user and the system administrator.\u003C\u002Fp>\n\u003Cp>Beyond the security, the GuardianKey solution provides a good user experience, because the user is not required to provide extra information or to execute tasks during the login. When GKTinc is enabled, the challenge runs automatically during login, with server-side validation in the plugin.\u003C\u002Fp>\n\u003Cp>GuardianKey’s approach provides a risk assessment in real-time. The events and risks can be explored in the GuardianKey’s administration panel.\u003C\u002Fp>\n\u003Ch3>How GuardianKey works\u003C\u002Fh3>\n\u003Cp>The GuardianKey detection engine analyzes the events sent by your online system to the GuardianKey servers.\u003C\u002Fp>\n\u003Cp>The detection engine uses Machine Learning and our secret mathematical risk formula to combine the following three analysis approaches: Threat Intelligence, Behavioral Profiling, and Psychometric Profiling. Using these three pillars, our engine computes a risk for each event sent by the protected systems. In real time, the online attempt can be blocked, an extra requirement can be requested to the user, or notifications can be triggered.\u003C\u002Fp>\n\u003Cp>All data sent to GuardianKey servers are doubly encrypted, and NOT send passwords or sensitive data.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>More information at https:\u002F\u002Fguardiankey.io\u002F\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Ch3>Plugin Installation\u003C\u002Fh3>\n\u003Col>\n\u003Cli>Install GuardianKey from WordPress plugin directory, and activate plugin\u003C\u002Fli>\n\u003Cli>Go to https:\u002F\u002Fpanel.guardiankey.io\u002Fauth\u002Fregister, and create account in GuardianKey\u003C\u002Fli>\n\u003Cli>Access GuardianKey panel (https:\u002F\u002Fpanel.guardiankey.io\u002F) and go to Settings->Authgroups->edit\u002Fview\u002FDeploy information and get keys\u003C\u002Fli>\n\u003Cli>Access Administration->Tools->GuardianKey in your WP and put keys of GuardianKey\u003C\u002Fli>\n\u003Cli>Configure GKTinc by filling API Key, Protection Group Hash ID, and Default Challenge Level\u003C\u002Fli>\n\u003Cli>If you want notify users, change “Notify Users” option to “yes”\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch3>Using GuardianKey\u003C\u002Fh3>\n\u003Cp>Access https:\u002F\u002Fpanel.guardiankey.io and login using the credentials sent to your e-mail address during the registration. You can recover the pass if you forgot it.\u003C\u002Fp>\n\u003Cp>GKTinc is optional and can be enabled in the plugin settings. When enabled, the plugin loads the GKTinc JS setup, injects the config generated by the SDK, and validates each login server-side.\u003C\u002Fp>\n\u003Cp>There is a documentation for the panel available at https:\u002F\u002Fguardiankey.io\u002Fdocs\u003C\u002Fp>\n","GuardianKey is a service to protect systems in real-time against authentication attacks. It implements GK Auth Security for login protection and GKTin …",20,5103,100,"2026-02-06T17:14:00.000Z","6.9.0","4.4","5.5",[78,19,54,22],"authentication","http:\u002F\u002Fwordpress.org\u002Fplugins\u002Fguardiankey\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fguardiankey.5.7.zip",{"slug":82,"name":83,"version":84,"author":85,"author_profile":86,"description":87,"short_description":88,"active_installs":10,"downloaded":89,"rating":12,"num_ratings":12,"last_updated":16,"tested_up_to":90,"requires_at_least":91,"requires_php":16,"tags":92,"homepage":16,"download_link":96,"security_score":72,"vuln_count":12,"unpatched_count":12,"last_vuln_date":26,"fetched_at":97},"ais-ip-blocker","AIS: IP Blocker","2.2.0","AIS TECHNOLABS","https:\u002F\u002Fprofiles.wordpress.org\u002Faistechnolabspvtltd\u002F","\u003Cp>IP Blocker for WordPress allows you to block the malicious IP Addresses, Spammers and Hackers. Now, You can block IP addresses according to your conditions.\u003C\u002Fp>\n\u003Cp>By blocking the Unwanted or Spammy IP Addresses, you can prevent hacking attempts on your wordpress website.\u003C\u002Fp>\n\u003Cp>Admin can get also mail notification when some-one’s IP get blocked.\u003C\u002Fp>\n\u003Cp>The blocked IPs won’t be able to scrap the precious content too from your WordPress Site. You can choose to either display the blocked message or an empty page to the blocked users. And anytime you can delete that IP from the blocking list if you know that it’s not performing malicious activities.\u003C\u002Fp>\n\u003Ch4>Plugin Features\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Cstrong>Block Unlimited IP Addresses from accessing your website\u003C\u002Fstrong>\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Display predefined message or a blank page to the blocked user\u003C\u002Fstrong>\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Free 24X7 Support\u003C\u002Fstrong>\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Automatic IP Blocking on Suspicious Activity, Auto-blocking if hits more url within stipulated time\u003C\u002Fstrong>\u003C\u002Fli>\n\u003C\u002Ful>\n","Blocks malicious IP Addresses, Spammers and Hackers from accessing page without compromising the performance of your WordPress Website.",1808,"6.0.11","6.0",[93,19,94,95,22],"blacklist","block-ip","ip-blocker","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fais-ip-blocker.zip","2026-03-15T10:48:56.248Z",{"slug":99,"name":100,"version":101,"author":102,"author_profile":103,"description":104,"short_description":105,"active_installs":106,"downloaded":107,"rating":108,"num_ratings":109,"last_updated":110,"tested_up_to":111,"requires_at_least":91,"requires_php":52,"tags":112,"homepage":115,"download_link":116,"security_score":117,"vuln_count":31,"unpatched_count":60,"last_vuln_date":118,"fetched_at":27},"wp-limit-login-attempts","WP Limit Login Attempts","2.6.5","Arshid","https:\u002F\u002Fprofiles.wordpress.org\u002Farshidkv12\u002F","\u003Cp>Limit Login Attempts for login protection, protect site from brute force attacks.Brute Force Attack aims at being the simplest kind of method to gain access to a site: it tries usernames and passwords, over and over again, until it gets in. WP Limit Login Attempts plugin limit rate of login attempts and block IP temporarily. It is detecting bots by captcha verification.\u003C\u002Fp>\n\u003Cp>Go to \u003Ccode>Settings > WP Limit Login\u003C\u002Fcode>.\u003C\u002Fp>\n\u003Ch4>Features\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Login Security – Limit Login Attempts and track user login attempts\u003C\u002Fli>\n\u003Cli>Captcha Verification \u003C\u002Fli>\n\u003Cli>Light weight plugin \u003C\u002Fli>\n\u003Cli>Mechanism for slow down brute force attack \u003C\u002Fli>\n\u003Cli>Redirect to home page, when abnormal request (It will stop hacking tools)\u003C\u002Fli>\n\u003Cli>\u003Cstrong>GDPR\u003C\u002Fstrong> compliant. With this feature turned on, all logged IPs get obfuscated (md5-hashed).\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Limit Login Attempts\u003C\u002Fh4>\n\u003Cp>A brute force attack is a trial-and-error mеthоd uѕеd tо оbtаin infоrmаtiоn such аѕ a user раѕѕwоrd оr реrѕоnаl idеntifiсаtiоn number (PIN). In a brute force attack, аutоmаtеd software iѕ uѕеd tо gеnеrаtе a lаrgе numbеr оf соnѕесutivе guesses аѕ to thе value of thе desired data. Brute force attack may bе uѕеd by сriminаlѕ tо crack еnсrурtеd dаtа, оr bу security аnаlуѕtѕ to tеѕt an оrgаnizаtiоn’ѕ nеtwоrk security.\u003C\u002Fp>\n\u003Cp>If уоu аdорt thе use оf this plugin, it will limit thе number оf timеѕ a uѕеr can аttеmрt tо log intо уоur ассоunt. Aftеr a сарtсhа verification would have bееn rеԛuеѕtеd, thе mесhаniѕm will ѕlоw dоwn brutе fоrсе аttасk hаving thе роwеr tо redirect tо home page аnd соmрlеtеlу аvоid intruder intо уоur рrесiоuѕ ассоunt.\u003C\u002Fp>\n\u003Ch4>Captcha Verification\u003C\u002Fh4>\n\u003Cp>WP Limit Login Attempts plugin provides an extra protection by Captcha.\u003Cbr \u002F>\nCaptcha Verification in seven attempts. It will be highly helpful for removing bots.\u003C\u002Fp>\n\u003Cp>For more service ,\u003Ca href=\"http:\u002F\u002Fwww.ciphercoin.com\" rel=\"nofollow ugc\">Please visit\u003C\u002Fa>\u003C\u002Fp>\n\u003Ch4>Donations\u003C\u002Fh4>\n\u003Cp>WP Limit Login Attempts plugin protecting your admin. Please make donation, I really appreciate it .\u003C\u002Fp>\n\u003Ch4>Support\u003C\u002Fh4>\n\u003Cp>http:\u002F\u002Fwww.ciphercoin.com\u002Fcontact\u002F\u003C\u002Fp>\n\u003Cspan class=\"embed-youtube\" style=\"text-align:center; display: block;\">\u003Ciframe loading=\"lazy\" class=\"youtube-player\" width=\"750\" height=\"422\" src=\"https:\u002F\u002Fwww.youtube.com\u002Fembed\u002F_T8SWmMcawo?version=3&rel=1&showsearch=0&showinfo=1&iv_load_policy=1&fs=1&hl=en-US&autohide=2&wmode=transparent\" allowfullscreen=\"true\" style=\"border:0;\" sandbox=\"allow-scripts allow-same-origin allow-popups allow-presentation allow-popups-to-escape-sandbox\">\u003C\u002Fiframe>\u003C\u002Fspan>\n","Limit rate of login attempts and block IP temporarily. Brute force attack protection. GDPR compliant. Captcha enabled.",10000,441779,92,300,"2024-08-04T01:13:00.000Z","6.6.5",[78,21,113,114,22],"login","loginizer","https:\u002F\u002Fciphercoin.com\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp-limit-login-attempts.zip",68,"2022-12-27 00:00:00",{"slug":120,"name":121,"version":122,"author":123,"author_profile":124,"description":125,"short_description":126,"active_installs":127,"downloaded":128,"rating":129,"num_ratings":32,"last_updated":130,"tested_up_to":131,"requires_at_least":132,"requires_php":16,"tags":133,"homepage":137,"download_link":138,"security_score":34,"vuln_count":60,"unpatched_count":12,"last_vuln_date":139,"fetched_at":27},"exploit-scanner","Exploit Scanner","1.5.2","Donncha O Caoimh (a11n)","https:\u002F\u002Fprofiles.wordpress.org\u002Fdonncha\u002F","\u003Cp>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.\u003C\u002Fp>\n\u003Cp>It does not remove anything. That is left to the user to do.\u003C\u002Fp>\n\u003Cp>Latest MD5 hash values for Exploit Scanner:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>17e2ccfc834d691bc68cc5c64f9bed89  exploit-scanner.php (1.5.2)\u003C\u002Fli>\n\u003Cli>1d5f9d6220fe159cd44cb70a998a1cd7  hashes-4.6.php\u003C\u002Fli>\n\u003Cli>fbdf61c17f65094c8e331e1e364acf68  hashes-4.6.1.php\u003C\u002Fli>\n\u003Cli>477d128d84802e3470cec408424a8de3  hashes-4.7.php\u003C\u002Fli>\n\u003Cli>d53210f999847fbd6f5a2ecac0ad42f2  hashes-4.7.5.php\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Latest SHA1 hash values for Exploit Scanner:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>1decc1e47a53d1cab9e8f1ef15b31682198367ee  exploit-scanner.php (1.5.2)\u003C\u002Fli>\n\u003Cli>5cec64380a2acdc876fd22fbbbbf8c335df1ed3f  hashes-4.6.php\u003C\u002Fli>\n\u003Cli>99d9e7be23a350f3d1962d0f41e7b4e28c00841e  hashes-4.6.1.php\u003C\u002Fli>\n\u003Cli>1eeab377a1afc6d776827a063678d2461b29e71d  hashes-4.7.php\u003C\u002Fli>\n\u003Cli>8c890a6af26bb74e9d17e5d2b21d6be27764da45  hashes-4.7.5.php\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>See the \u003Ca href=\"http:\u002F\u002Focaoimh.ie\u002Fexploit-scanner\u002F\" rel=\"nofollow ugc\">Exploit Scanner homepage\u003C\u002Fa> for further information.\u003C\u002Fp>\n\u003Ch3>Interpreting the Results\u003C\u002Fh3>\n\u003Cp>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\u003Cbr \u002F>\non the side of caution; if you are unsure then ask in the \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fsupport\u002F\" rel=\"ugc\">Support Forums\u003C\u002Fa>,\u003Cbr \u002F>\ndownload a fresh copy of a plugin, search the Internet for similar situations, et cetera. You should be most concerned if the scanner is:\u003Cbr \u002F>\nmaking matches around unknown external links; finding base64 encoded text in modified core files or the \u003Ccode>wp-config.php\u003C\u002Fcode> file;\u003Cbr \u002F>\nlisting extra admin accounts; or finding content in posts which you did not put there.\u003C\u002Fp>\n\u003Cp>Understanding the three different result levels:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Severe:\u003C\u002Fstrong> results that are often strong indicators of a hack (though they are not definitive proof)\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Warning:\u003C\u002Fstrong> these results are more commonly found in innocent circumstances than Severe matches, but they should still be treated with caution\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Note:\u003C\u002Fstrong> lowest priority, showing results that are very commonly used in legitimate code or notifications about events such as skipped files\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Help! I think I have been hacked!\u003C\u002Fh3>\n\u003Cp>Follow the guides from the Codex:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fcodex.wordpress.org\u002FFAQ_My_site_was_hacked\" rel=\"nofollow ugc\">Codex: FAQ – My site was hacked\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fcodex.wordpress.org\u002FHardening_WordPress\" rel=\"nofollow ugc\">Codex: Hardening WordPress\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Ensure that you change \u003Cstrong>all\u003C\u002Fstrong> of your WordPress related passwords (site, FTP, MySQL, etc.). A regular backup routine\u003Cbr \u002F>\n(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\u003Cbr \u002F>\na clean backup and fresh set of files and, of course, use a new set of passwords.\u003C\u002Fp>\n\u003Ch3>Updates\u003C\u002Fh3>\n\u003Cp>Updates to the plugin will be posted here, to \u003Ca href=\"http:\u002F\u002Focaoimh.ie\u002F\" rel=\"nofollow ugc\">Holy Shmoly!\u003C\u002Fa> and the \u003Ca href=\"http:\u002F\u002Focaoimh.ie\u002Fexploit-scanner\u002F\" rel=\"nofollow ugc\">WordPress Exploit Scanner\u003C\u002Fa> page will always link to the newest version.\u003C\u002Fp>\n\u003Ch3>Other Languages\u003C\u002Fh3>\n\u003Cp>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:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ca href=\"http:\u002F\u002Fwpbiz.jp\u002Ffiles\u002Fexploit-scanner-hashes\u002Fja\u002F\" rel=\"nofollow ugc\">Japanese\u003C\u002Fa> – thanks to Naoko\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"http:\u002F\u002Ftalkpress.de\u002Fartikel\u002Fexploit-scanner-hash-deutsch-wordpress\" rel=\"nofollow ugc\">German\u003C\u002Fa> – thanks to Robert Wetzlmayr\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>The hash files should only be declaring an array called $filehashes and the majority of the hashes should still be the same.\u003C\u002Fp>\n","Search the files and database of your WordPress install for signs that may indicate that it has fallen victim to malicious hackers.",9000,1067302,64,"2017-11-28T06:49:00.000Z","4.7.32","3.3",[21,134,135,22,136],"hacking","scanner","spam","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fexploit-scanner\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fexploit-scanner.1.5.2.zip","2013-05-29 00:00:00",{"attackSurface":141,"codeSignals":185,"taintFlows":295,"riskAssessment":330,"analyzedAt":348},{"hooks":142,"ajaxHandlers":181,"restRoutes":182,"shortcodes":183,"cronEvents":184,"entryPointCount":12,"unprotectedCount":12},[143,149,153,156,159,162,165,169,174,178],{"type":144,"name":145,"callback":146,"file":147,"line":148},"action","admin_menu","spmy_dpabadbot_actions","dpabadbotWP-functionality.php",488,{"type":144,"name":150,"callback":151,"file":147,"line":152},"save_post","spmy_dpabadbot_post_numbers",489,{"type":144,"name":154,"callback":151,"file":147,"line":155},"post_updated",490,{"type":144,"name":157,"callback":151,"file":147,"line":158},"edit_post",491,{"type":144,"name":160,"callback":151,"file":147,"line":161},"publish_post",492,{"type":144,"name":163,"callback":151,"file":147,"line":164},"wp_logout",531,{"type":144,"name":166,"callback":167,"file":147,"line":168},"init","spmy_dpabadbot_login_hook",532,{"type":170,"name":171,"callback":172,"file":147,"line":173},"filter","auto_update_core","__return_false",533,{"type":144,"name":175,"callback":176,"priority":109,"file":147,"line":177},"wp_footer","dpabadbotbottomofpagelink",534,{"type":144,"name":175,"callback":179,"priority":106,"file":147,"line":180},"dpabadbotendofpage",535,[],[],[],[],{"dangerousFunctions":186,"sqlUsage":231,"outputEscaping":238,"fileOperations":293,"externalRequests":12,"nonceChecks":12,"capabilityChecks":12,"bundledLibraries":294},[187,191,194,197,199,201,204,206,208,210,213,216,218,221,223,225,227,228],{"fn":188,"file":147,"line":189,"context":190},"unserialize",58,"$tmp = unserialize( $tmpx );",{"fn":188,"file":147,"line":192,"context":193},62,"$tmpa = unserialize( $tmpb );",{"fn":188,"file":147,"line":195,"context":196},117,"$spmywp_dpabadbot_setup_data = unserialize( $spmywp_dpabadbot_setup_tmp );",{"fn":188,"file":147,"line":198,"context":196},252,{"fn":188,"file":147,"line":200,"context":196},284,{"fn":188,"file":147,"line":202,"context":203},301,"$spmywp_dpabadbot_ip_addrs = unserialize( $spmywp_dpabadbot_ip_tmp );",{"fn":188,"file":147,"line":205,"context":203},322,{"fn":188,"file":147,"line":207,"context":190},360,{"fn":188,"file":147,"line":209,"context":196},391,{"fn":188,"file":147,"line":211,"context":212},405,"$spmywp_dpabadbot_setup_data_log = unserialize( $spmywp_dpabadbot_setup_tmp_log );",{"fn":188,"file":147,"line":214,"context":215},415,"$spmywp_dpabadbot_uploads_ip_file200_data = unserialize( spmy_dpabadbot_read_file(  $spmywp_dpabadbo",{"fn":188,"file":147,"line":217,"context":203},499,{"fn":188,"file":219,"line":220,"context":196},"spmy_dpabadbot_form.php",104,{"fn":188,"file":219,"line":222,"context":212},123,{"fn":188,"file":219,"line":224,"context":212},179,{"fn":188,"file":219,"line":226,"context":215},189,{"fn":188,"file":219,"line":205,"context":203},{"fn":188,"file":219,"line":229,"context":230},328,"$spmywp_dpabadbot_ip_addrs200 = unserialize( $spmywp_dpabadbot_ip_tmp200 );",{"prepared":12,"raw":31,"locations":232},[233,236],{"file":147,"line":234,"context":235},129,"$wpdb->get_results() with variable interpolation",{"file":147,"line":237,"context":235},157,{"escaped":31,"rawEcho":239,"locations":240},31,[241,244,246,247,249,250,252,253,255,256,258,259,261,263,264,266,267,269,271,272,273,275,277,279,280,281,283,285,287,289,291],{"file":147,"line":242,"context":243},364,"raw output",{"file":219,"line":245,"context":243},263,{"file":219,"line":245,"context":243},{"file":219,"line":248,"context":243},264,{"file":219,"line":248,"context":243},{"file":219,"line":251,"context":243},265,{"file":219,"line":251,"context":243},{"file":219,"line":254,"context":243},266,{"file":219,"line":254,"context":243},{"file":219,"line":257,"context":243},267,{"file":219,"line":257,"context":243},{"file":219,"line":260,"context":243},272,{"file":219,"line":262,"context":243},273,{"file":219,"line":262,"context":243},{"file":219,"line":265,"context":243},274,{"file":219,"line":265,"context":243},{"file":219,"line":268,"context":243},282,{"file":219,"line":270,"context":243},283,{"file":219,"line":270,"context":243},{"file":219,"line":270,"context":243},{"file":219,"line":274,"context":243},356,{"file":219,"line":276,"context":243},379,{"file":219,"line":278,"context":243},382,{"file":219,"line":278,"context":243},{"file":219,"line":278,"context":243},{"file":219,"line":282,"context":243},387,{"file":219,"line":284,"context":243},408,{"file":219,"line":286,"context":243},434,{"file":219,"line":288,"context":243},435,{"file":219,"line":290,"context":243},436,{"file":219,"line":292,"context":243},437,12,[],[296],{"entryPoint":297,"graph":298,"unsanitizedCount":328,"severity":329},"\u003Cspmy_dpabadbot_form> (spmy_dpabadbot_form.php:0)",{"nodes":299,"edges":323},[300,305,310,314,318],{"id":301,"type":302,"label":303,"file":219,"line":304},"n0","source","$_POST (x4)",153,{"id":306,"type":307,"label":308,"file":219,"line":268,"wp_function":309},"n1","sink","echo() [XSS]","echo",{"id":311,"type":302,"label":312,"file":219,"line":313},"n2","$_POST",315,{"id":315,"type":316,"label":317,"file":219,"line":313},"n3","transform","→ spmy_dpabadbot_write_file()",{"id":319,"type":307,"label":320,"file":147,"line":321,"wp_function":322},"n4","fopen() [File Access]",215,"fopen",[324,326,327],{"from":301,"to":306,"sanitized":325},false,{"from":311,"to":315,"sanitized":325},{"from":315,"to":319,"sanitized":325},5,"medium",{"summary":331,"deductions":332},"The \"dpabadbotwp\" plugin v1.27 exhibits a mixed security posture. On the positive side, it reports zero known CVEs and a history free of vulnerabilities, suggesting a generally stable codebase. The static analysis also indicates a very small attack surface with no identified AJAX handlers, REST API routes, shortcodes, or cron events, which is a strong indicator of good security practice in limiting potential entry points.\n\nHowever, significant concerns arise from the code analysis. The presence of 18 dangerous function calls, specifically `unserialize`, is a major red flag, especially given the absence of any nonce or capability checks. This combination is highly risky, as unserializing untrusted data can lead to Remote Code Execution (RCE) or other severe vulnerabilities. Furthermore, the fact that none of the SQL queries use prepared statements and a mere 6% of output is properly escaped indicates a high probability of SQL Injection and Cross-Site Scripting (XSS) vulnerabilities, respectively. The taint analysis showing flows with unsanitized paths, even without critical or high severity ratings, reinforces these concerns.\n\nWhile the plugin's vulnerability history is clean, this does not negate the inherent risks identified in the static analysis. The lack of security checks on critical functions like `unserialize` and the poor practices regarding SQL queries and output escaping are significant weaknesses. The absence of any bundled libraries is a neutral observation in this context. In conclusion, despite a lack of reported vulnerabilities, the plugin's current state presents substantial risks due to fundamental security oversights in code implementation.",[333,336,338,341,344,346],{"reason":334,"points":335},"Dangerous function 'unserialize' without checks",15,{"reason":337,"points":10},"SQL queries without prepared statements",{"reason":339,"points":340},"Low percentage of properly escaped output",8,{"reason":342,"points":343},"Flows with unsanitized paths",7,{"reason":345,"points":10},"No nonce checks",{"reason":347,"points":10},"No capability checks","2026-03-17T00:22:21.566Z",{"wat":350,"direct":355},{"assetPaths":351,"generatorPatterns":352,"scriptPaths":353,"versionParams":354},[],[],[],[],{"cssClasses":356,"htmlComments":357,"htmlAttributes":358,"restEndpoints":359,"jsGlobals":360,"shortcodeOutput":361},[],[],[],[],[],[362],"\u003Cdiv style=\"text-align:center\">\u003Ca target=\"_blank\" href=\"https:\u002F\u002Fdrpeterscode.com\u002Fbad-bot-exterminator-protects-wordpress-sites-from-hackers-cyber-ddos-dos-attacks.php\">Protected by the Bad Bot Exterminator Pro\u003C\u002Fa>\u003C\u002Fdiv>"]