WordPress.org Plugin Authors Receive Suspicious Requests For Repository Access

A suspicious request has been circulating via email, soliciting WordPress.org plugin authors to give a third party write access to their repositories. The originator of these requests goes by the username bestweblayout on WordPress.org and operates the bestweblayout.com domain.

The issue was first reported by WordPress user FractalizeR, who posted the contents of the email:

“Hello Vladislav.

My name is Grigoriy and I am a representative of BestWebLayout. Our team specializes in WordPress development services.

We saw that your WP-SynHighlight plugin was updated more than 4 years ago. We would like to offer you our assistance and participation in further development and maintenance of this plugin. In other words, we would like to get your permission and access to plugin repository on wordpress.org. In such way we will become the plugin contributors along with you and will be able to control testing and development of this tool within the WordPress community.

Our activity will include plugin updates, compatibility testing, support, etc.

We have already talked to WordPress support team (they said that WordPress is open-source community and such contribution is welcome), who asked us to contact you with such a request. Please let me know if you are ready to accept our offer. Feel free to contact me with any questions.

Thanks!

Grigoriy”

FractalizeR’s initial reaction to the email was one of suspicion. “The offer itself is a little strange,” he said. [pullquote]”If I want to contribute, I donate code. I don’t ask write access to the repository.”[/pullquote]

@Codix, another recipient of the email, decided to ask for contributions first. “I got the same offer and I suggested they should submit a patch to one issue before I can grant them access,” he said. “Still they insist they need to be listed as a contributor.”

A handful of other plugin developers reported on the same thread that they have received the same email, which they forwarded to plugins@wordpress.org. Mika Epstein, a member of the WordPress.org plugin review team, confirmed that they did not ask bestweblayout to get in touch with the authors.

In the meantime, bestweblayout posted on the thread in defense of the email solicitations:

We aren’t involved in any illegal affairs. Earlier on forum there was a question about the possibility of cooperation with the authors of neglected plugins. And it said that it is not a problem to cooperate with the authors. So we decided to help WordPress community with these plugins. We only collect information about plugins, which were simply neglected by authors and have not been updated with the latest changes of WordPress. Some of the authors refused, but some of them agreed. Sorry that it looks like spam.

Those who have reported having received the requests are uniformly suspicious of the technique that is being employed for gaining write access to their repositories. Epstein addressed bestweblayouts to explain why their requests are not being well-received. “It looks like spam because you’re sending this out to a LOT of people, and as of yet, haven’t done anything with the plugins,” she said. [pullquote]”Which is, sadly, a tactic of some spammers. They’ll take over legit plugins and turn them into guideline violation spam fests.” [/pullquote]

WordPress plugin developer Jeff Sayre was another recipient of the email and he cites several issues with the approach that indicate it may be a potential threat. The fact that anyone is free to fork a plugin and develop their own version was the first indication. Developers can let the original author know, as a courtesy, but permission is not required.

Secondly, the “approval” implied in the email request is suspect. “The fact that the email makes it appear that they have “approval” from the WP repo team to contact me is another big, red flag,” Sayre said. “No one requires approval from anyone at WP to contact a plugin author. I receive emails all the time about updating my plugins.” Despite Epstein having made it clear that approval has not been given, the folks at bestweblayout continue to circulate the same email without modification.

A Warning to All WordPress.org Plugin Authors

Sayre has some sage words of warning to anyone who may receive this request or something similar. In case the offer of free updates to your plugin sounded like a dream come true to you, it’s a good idea to consider what is at stake. He cautions all concerned:

Providing such credentials to an unknown, therefore untrusted party, is never wise as it could be a significant security threat. Malicious code could be entered into your plugin and you, in effect, would be complicit in its insertion. If you do not know someone, it is never wise to team up with them without fully vetting their integrity and the quality of their work.

Obviously, you should be very wary of giving anyone write access to your plugin repositories. The motivation for the request could be harmless or it could be a ploy to gain access to WordPress.org plugins in order to unleash spamagaddon. When it comes to collaborating on code, it’s best to work only with developers you trust. If you’re not interested in collaborating, the safest route would be to suggest that they fork your work and credit you.

15

15 responses to “WordPress.org Plugin Authors Receive Suspicious Requests For Repository Access”

  1. Even their website (bestweblayout.com) looks like it’s trying to copy wordpress.org. I agree with Code Master (in the forums thread) that they’re either being “malicious or incompetent.” Why not just fork the old plugin and re-release it with the updates?

  2. Part of the issue that creates the problem is that there is no good way to do pull requests with SVN – or, at least, with the specific SVN repository for Plugins. There is simply no good way to vet such unsolicited requests for contribution. They could be legit, or they could be scurrilous. It’s easy to say “you can just donate code” – but where and how do you do that? If I find an abandoned Plugin, and want to contribute code to bring that Plugin up-to-date, there is no standardized way to do that.

    And while forking is certainly a viable approach from a developer perspective, it is less-than-ideal from a user perspective (no way to update directly from an obsolete original to an up-to-date fork; proliferation of Plugins for the same functionality makes finding the right/best one more difficult, etc.).

    I think that’s why more and more developers are moving to GitHub for their development environment. With GitHub, anyone can submit a pull request, that can then be easily incorporated by the original developer.

    My advice to bestweblayout: if you’re legit, establish some credibility by finding GitHub-hosted Plugins, and make pull requests to them. And for obsolete Plugins that don’t have a GitHub repository, create a fork of your own, and then email the original developers with links to your forked updates on GitHub.

    • Chip, you make a good point. There really isn’t a *good* way to offer code to a plugin developer who has their plugin in the repository. However, asking for update credentials to the repository is very much a *bad* way to offer help to a plugin developer. Even if it’s a legit offer, it looks very, very suspicious.

      And, I think you make a very convincing argument for using GitHub instead. In fact, just the other day, I stumbled across a plugin meant to help you update plugins hosted via GitHub. Naturally, it was on GitHub! https://github.com/jkudish/WordPress-GitHub-Plugin-Updater
      Any thoughts on that plugin?

    • It’s easy to say “you can just donate code” – but where and how do you do that?

      The plugins Trac is probably the best place to submit patches if the plugin author did not mention any GitHub repository in the readme. It’s far from perfect, but it’s not more difficult than submitting patches to WordPress Core IMO. And this trac recently got the same redesign treatment than core.trac, so it looks good now! :)

      I would also suggest posting a link to the Trac ticket in a new forum thread to let the plugin author know about your patch, just in case.

  3. Here’s an email I received on January 6th …

    Hello Ryan,

    My name is Grigoriy and I am a representative of BestWebLayout. Our team specializes in WordPress development services.

    We saw that your Suckerfish Dropdown Menu and PixoPoint Theme Integrator plugins were updated more than 5 years ago. We would like to offer you our assistance and participation in further development and maintenance of these plugins. In other words, we would like to get your permission and access to plugin repository on wordpress.org. In such way we will become the plugin contributors along with you and will be able to control testing and development of these tools within the WordPress community.

    Our activity will include plugin updates, compatibility testing, support, etc.

    We have already talked to WordPress support team (they said that WordPress is open-source community and such contribution is welcome), who asked us to contact you with such a request. Please let me know if you are ready to accept our offer. Feel free to contact me with any questions.

    Thanks!

    Grigoriy

  4. This sounds all too familiar.

    It’s not just the mass/indiscriminate emailing, implication of permission from official sources, but also the domain name that adds to the sketchiness.

    What kind of name is “BestWebLayout” for a legit web services company? It’s like Girigory literally just mashed keywords into Google’s Keyword Planner and grabbed the first one available in .com.

    I suspect he may have relatively benign intentions to start, and just wanted to build up his credibility by having a bunch of established plugins listed on his WordPress.org profile page.

    This isn’t the way of going about doing it, and ironically damaged his reputation far more than he would’ve gained by getting access to a few plugins.

  5. Hmm. A marketing company sees an opportunity with a popular, but under-maintained plugin to make inroads with the WordPress community (and presumably drum up some business) . . . reminds me of Blink Web Effects and the Social Media Widget plugin malware fiasco early last year.

Newsletter

Subscribe Via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.