Title: Backdoor:PHP/Fobushell.D
Last modified: August 22, 2016

---

# Backdoor:PHP/Fobushell.D

 *  Resolved [frankske_699](https://wordpress.org/support/users/frankske_699/)
 * (@frankske_699)
 * [11 years, 2 months ago](https://wordpress.org/support/topic/backdoorphpfobushelld/)
 * Downloaded my site via ftp just now and Microsoft Security Essentials complainded
   about a backdoor in wp-content\plugins\gravityforms-nl\ddyt.php
 * Is it ok to ignore this?
 * [https://wordpress.org/plugins/gravityforms-nl/](https://wordpress.org/plugins/gravityforms-nl/)

Viewing 1 replies (of 1 total)

 *  Plugin Author [Remco Tolsma](https://wordpress.org/support/users/remcotolsma/)
 * (@remcotolsma)
 * [11 years, 2 months ago](https://wordpress.org/support/topic/backdoorphpfobushelld/#post-5865404)
 * I don’t think it’s a good idea to ingore this. Your website is probably hacked
   and you should clean this up. The `ddyt.php` file is not part of our plugin. 
   You should also try to find out how that file ended up there.
 * [https://plugins.trac.wordpress.org/browser/gravityforms-nl/tags/2.9.1](https://plugins.trac.wordpress.org/browser/gravityforms-nl/tags/2.9.1)

Viewing 1 replies (of 1 total)

The topic ‘Backdoor:PHP/Fobushell.D’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/gravityforms-nl_707c8b.svg)
 * [Gravity Forms (nl)](https://wordpress.org/plugins/gravityforms-nl/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/gravityforms-nl/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/gravityforms-nl/)
 * [Active Topics](https://wordpress.org/support/plugin/gravityforms-nl/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/gravityforms-nl/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/gravityforms-nl/reviews/)

 * 1 reply
 * 2 participants
 * Last reply from: [Remco Tolsma](https://wordpress.org/support/users/remcotolsma/)
 * Last activity: [11 years, 2 months ago](https://wordpress.org/support/topic/backdoorphpfobushelld/#post-5865404)
 * Status: resolved