Title: Weird DB names Last modified: November 4, 2020 --- # Weird DB names * Resolved [josmatic](https://wordpress.org/support/users/josmatic/) * (@josmatic) * [5 years, 7 months ago](https://wordpress.org/support/topic/weird-db-names/) * Hi, Am I infected or what? * Some tables has similar names, difference are small. Please look names of tables bellow (look for _bkp and similar). * Names of tables in database: * wp_commentmeta wp_comments wp_links wp_options wp_postmeta wp_posts wp_revslider_css wp_revslider_css_bkp wp_revslider_layer_animations wp_revslider_layer_animations_bkp wp_revslider_navigations wp_revslider_navigations_bkp wp_revslider_sliders wp_revslider_sliders_bkp wp_revslider_slides wp_revslider_slides_bkp wp_revslider_static_slides wp_revslider_static_slides_bkp wp_termmeta wp_terms wp_term_relationships wp_term_taxonomy wp_usermeta wp_users wp_wfbadleechers wp_wfblockediplog wp_wfBlockedIPLog wp_wfblocks wp_wfBlocks7 wp_wfblocksadv wp_wfconfig wp_wfConfig wp_wfCrawlers wp_wfcrawlers wp_wfFileChanges wp_wffilemods wp_wfFileMods wp_wfHits wp_wfHoover wp_wfIssues wp_wfKnownFileList wp_wfLiveTrafficHuman wp_wfLocs wp_wfLogins wp_wfNotifications wp_wfPendingIssues wp_wfReverseCache wp_wfSNIPCache wp_wfStatus wp_wfTrafficRates wp_wfhits wp_wfhoover wp_wfissues wp_wfleechers wp_wflockedout wp_wflocs wp_wflogins wp_wfls_2fa_secrets wp_wfls_settings wp_wfnet404s wp_wfreversecache wp_wfscanners wp_wfstatus wp_wfthrottlelog wp_wfvulnscanners wp_woocommerce_api_keys wp_woocommerce_attribute_taxonomies wp_woocommerce_downloadable_product_permissions wp_woocommerce_order_itemmeta wp_woocommerce_order_items wp_woocommerce_payment_tokenmeta wp_woocommerce_payment_tokens wp_woocommerce_sessions wp_woocommerce_shipping_zones wp_woocommerce_shipping_zone_locations wp_woocommerce_shipping_zone_methods wp_woocommerce_tax_rates wp_woocommerce_tax_rate_locations * Any advice? Viewing 5 replies - 1 through 5 (of 5 total) * [Harris O.](https://wordpress.org/support/users/hfort/) * (@hfort) * [5 years, 7 months ago](https://wordpress.org/support/topic/weird-db-names/#post-13621350) * Those databases belong to your Revolution slider plugin. The bkp usually means backup. You will need to get in touch with the Revslider developer and ask about that. It doesn’t seem to be a hack though. It’s probably related to upgrading the plugin’s version. * Thread Starter [josmatic](https://wordpress.org/support/users/josmatic/) * (@josmatic) * [5 years, 7 months ago](https://wordpress.org/support/topic/weird-db-names/#post-13623550) * Ok, but what about this * wp_wfblocks wp_wfBlocks7 wp_wfblocksadv * wp_wfconfig wp_wfConfig * wp_wfCrawlers wp_wfcrawlers * wp_wffilemods wp_wfFileMods * wp_wfissues wp_wfIssues * This seems strange to me. * Best regards. * Plugin Support [wfpeter](https://wordpress.org/support/users/wfpeter/) * (@wfpeter) * [5 years, 7 months ago](https://wordpress.org/support/topic/weird-db-names/#post-13626337) * Hi [@josmatic](https://wordpress.org/support/users/josmatic/), thanks for seeking out our help about these tables. * The good news is that there’s nothing suspicious here but I’m happy to explain what’s happened to create them and how you can go about deleting them if you wish, although this is not essential. * Often we’ll see the lower/uppercase (camelcase) name mix duplications of tables when you or your site developer has moved from a Windows to Linux hosting environment. This could just be something as simple as a development phase on a Windows machine to finally going live on the Linux server too. * You could export your settings at **Wordfence > Tools > Import/Export Options**, then check the **Delete Wordfence tables and data on deactivation** checkbox, deactivating your Wordfence plugin in WordPress, reactivating it again and importing the settings you previously exported. Legacy and duplicate tables would be removed automatically. * **Please note that after a reset you would need to optimize the firewall again and disable Learning Mode too. Also, firewall settings like whitelist entries cannot be exported so make a note of these beforehand if you have any.** * Alternatively, if you wish to remove duplicate tables that begin with **wp_wf** manually, only remove the ones that have an older timestamp as they’re the ones not being currently used. * Thanks, * Peter. * Thread Starter [josmatic](https://wordpress.org/support/users/josmatic/) * (@josmatic) * [5 years, 7 months ago](https://wordpress.org/support/topic/weird-db-names/#post-13628289) * Tnx [@wfpeter](https://wordpress.org/support/users/wfpeter/) this explain me a lot. When I migrate from live server to development I use some hash key for importing settings and thats can be catch. Also before migration to another server I delete “_wf” tables” and setup it again at destination server. * Best regards. * Plugin Support [wfpeter](https://wordpress.org/support/users/wfpeter/) * (@wfpeter) * [5 years, 7 months ago](https://wordpress.org/support/topic/weird-db-names/#post-13628970) * Hi [@josmatic](https://wordpress.org/support/users/josmatic/), thanks for your feedback. * That makes sense, hope you have all the information you need now. If anything crops up with Wordfence in the future that you’d like help with, don’t hesitate to contact us here again in a new topic. * Peter. Viewing 5 replies - 1 through 5 (of 5 total) The topic ‘Weird DB names’ is closed to new replies. * ![](https://ps.w.org/wordfence/assets/icon.svg?rev=2070865) * [Wordfence Security - Firewall, Malware Scan, and Login Security](https://wordpress.org/plugins/wordfence/) * [Frequently Asked Questions](https://wordpress.org/plugins/wordfence/#faq) * [Support Threads](https://wordpress.org/support/plugin/wordfence/) * [Active Topics](https://wordpress.org/support/plugin/wordfence/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/wordfence/unresolved/) * [Reviews](https://wordpress.org/support/plugin/wordfence/reviews/) * 5 replies * 3 participants * Last reply from: [wfpeter](https://wordpress.org/support/users/wfpeter/) * Last activity: [5 years, 7 months ago](https://wordpress.org/support/topic/weird-db-names/#post-13628970) * Status: resolved