Some of this might be explainable in this fashion, but not all.
https://www.wordfence.com/blog/2019/03/peculiar-php-present-...
> Firstly, the plugin includes a content filter that automatically replaces references to Blogerize, a service which claims to be a beginner’s blogging course, with references to Pipdig’s own services.
> Phil you need to stop with the lies. Not only do you outright lie about having the ability to kill sites with your plugin, you state that this was implemented in response to a security breach you experienced in July 2018. The code was implemented in November 2017.
https://twitter.com/nickstadb/status/1112444919409446912
Unfortunately, pipdig wiped and recreated the repo an hour ago, so that history is no longer available there at least.
I was just trying to give them the benefit of the doubt if this was done to try to combat piracy.
With GPL some piracy is expected though, and this isn't the right way to combat it.
WordPress plugins and development is still the Wild Wild West.
Most developers are good but they are some Black/Gray Hats out there for sure.
They were probably obfuscating those functions to hide them from the people selling their themes. Sounds like they were also disabling this plugin as well.
But they definitely went about things the wrong way, including functions like that and obfuscating them is definitely not the right way to do things.
I think a simple, we're sorry we had included these functions in this manner to combat the company stealing our themes last year. We understand this was wrong and a fresh clean version of the plugin will be out this week.
We will do things the right way from now on, you can trust us and we welcome audits of all our code.