In the meantime while PowerDNN tries to generate consulting revenue from their scanner, you can avoid the extortion and protect your DNN web property by using the following technique:

1. Login to your site using a Host account.
2. Select Host / File Manager from the navigation menu
3. Select each file which has a filename in the format of ##.##.##.txt ( ie. 04.08.02.txt )
4. Select the Delete Files option and Confirm
5. Since there may be multiple pages of files, repeat until all of the ##.##.##.txt files are removed.

Once you have completed the above steps, the scanner will report:

Verified website as a DotNetNuke Website.
Your DotNetNuke Version is between and 0.0.0.
 
There are no security vulnerabilities in your website.
You may now quit this wizard.

Please note that the above steps do not actually solve any security issues. Instead, they prevent hackers from determining what version of DotNetNuke you are running and potentially exploiting your site. It also prevents the general public from viewing False Positive security reports about your site and losing confidence in your business. To properly address security issues, you need to regularly follow the Security Policy page and try to keep up with the latest product releases.

It is unfortunate that PowerDNN's lack of cooperation has led to public discussions of this nature. I sincerely apologize.

I'm not saying PowerDNN's sites aren't patched by any means, but I think Chads recent post and Shaun's workaround may raise some questions in this area.

The "scanner" tool problem can be resolved at the ISP firewall level by blocking PowerDNN endpoint. As I have stated in my prior posts, this tool is designed to mislead the average DNN user, to scare them in to subscribing to their service or give an impression that DNN is flawed without PowerDNNs help. We have received several frantic phone calls from our customers yesterday before we blocked the PowerDNN “scanner”, these people were questioning the viability of DNN because of the PR stunt PowerDNN has pulled. Furthermore, they justify this action by the need to protect their customers, my question is who gave them the authority to patch our customer sites hosted on our servers or sites hosted with any other hosting provider with their hack-patch?  I think this is unethical behavior, and is equivalent of someone screaming “bomb, bomb” in a busy mall to get ahead of the line.

We host several large government and political election campaign DNN sites, these people do not like to be jerked around like that, neither do we. In the future, I hope they do not publicly issue home brew patches outside of their own network.

If PowerDNN wants to compete in the hosting market, this is certainly not the way to do business. PowerDNN is not the only DNN host, nor are the authority on how DNN should be hosted or maintained. Leave the DNN patching and maintenance to people that know what they are doing and have community best interest in mind.