---
title: "Comment by Sarwar Hossein on \"Do you still trust the \"Update Plugin\" button on WordPress after this incident?\" | Hashnode"
description: "Really important write-up. The scariest part is that this kind of attack does not depend on users installing a random plugin — it abuses the trust users already"
url: "https://hashnode.com/posts/do-you-still-trust-the-update-plugin-button-on-wordpress-after-this-incident/6a4c5116ad09d40f6b411ff0/comment/6a4e1219a0a143e09fa6c535"
---

[Discussion](https://hashnode.com/posts/do-you-still-trust-the-update-plugin-button-on-wordpress-after-this-incident/6a4c5116ad09d40f6b411ff0)

Comment [Do you still trust the "Update Plugin" button on WordPress after this incident?](https://hashnode.com/posts/do-you-still-trust-the-update-plugin-button-on-wordpress-after-this-incident/6a4c5116ad09d40f6b411ff0)

[Sarwar Hossein](https://hashnode.com/@sarwar3511)

[Jul 8](https://hashnode.com/posts/do-you-still-trust-the-update-plugin-button-on-wordpress-after-this-incident/6a4c5116ad09d40f6b411ff0/comment/6a4e1219a0a143e09fa6c535)

Really important write-up. The scariest part is that this kind of attack does not depend on users installing a random plugin — it abuses the trust users already place in the normal update process.

For our Webequipe PDF Search plugin, this is a strong reminder to keep the release process strict: staging tests before release, clear changelogs, limited access to release accounts, final ZIP review, Free/Pro compatibility checks, and post-release monitoring.

Features are important, but for plugins that handle uploaded documents, predictable and transparent updates matter just as much. Thanks for documenting this in detail.
