by algorisys 0 (0 reviews)

Algo Spam User Wiper

Name: Algo Spam User Wiper
Author: algorisys

Find WordPress users by email domain, soft-delete them into Trash, permanently delete in batches, and block blacklisted domains from registering.

Algo Spam User Wiper ranks #60,001 among WordPress.org plugins with 0+ active installations, is #3,855 of 5,058 in the Security category, and was last updated Sep 3, 2026. Data from WordPress.org, refreshed twice daily — see methodology.

Tested up to WP 7.0.8 (Current: 7.1.4)

v1.6.7 Current Version v1.6.7

Updated 1 month ago Last Update on 03 Sep, 2026

Refreshed 2 days ago Last Refreshed on

#3,855 of 5,058 in Security

View on WordPress.org

Rank

#60,001

— No change

Active Installs

-100%

KW Avg Position

N/A

— No change

Downloads

198

+2 today

Support Resolved

— No change

Rating

Review 0 out of 5

0 (0 reviews)

Next Milestone 10

Total Progress 20%

0+ 10+

32,433

Ranks to Climb

Growth Needed

8,000,000

Active Installs

Pro

Unlock Exact Install Count

See the precise estimated active installs for this plugin, calculated from real-time ranking data.

Exact install estimates within tiers
Track install growth over time
Milestone progress predictions

Upgrade to Pro

Need 8 more installs to reach 10+

Rank Changes

Current #60,001

Change

Best #

Upgrade to Pro

Unlock 30-day and 90-day rank history charts with a Pro subscription.

Upgrade Now

Active Installs Growth

Upgrade to Pro

Active Installs 0,000,000+

Growth +0.0%

Peak 0,000,000

Downloads Growth

Downloads

Growth

Peak

Upgrade to Pro

Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.

Upgrade Now

Reviews & Ratings

0.0

0 reviews

Overall 0%

0 (0%)

Track This Plugin

Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.

Start Tracking Free

Plugin Details

Version: 1.6.7
Last Updated: Sep 03, 2026
Requires WP: 5.8+
Tested Up To: 7.0.8
PHP Version: 7.4 or higher
Author: algorisys

Support & Rating

Rating: ☆ ☆ ☆ ☆ ☆ 0
Reviews: 0
Support Threads: 0
Resolved: 0%

Keywords

cleanup security spam trash users

Upgrade to Pro

Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.

Upgrade Now

Similar Plugins

Adminify – White Label, Admin Menu Editor, Login Customizer

6K+ installs

#2,757

Master Addons for Elementor – Elementor Addons, Widgets, Mega Menu Builder, Popup Builder, Widget Builder & Template Kits

Akismet Anti-spam: Spam Protection

5M+ installs

Wordfence Security – Firewall, Malware Scan, and Login Security

5M+ installs

#11

Really Simple Security – Simple and Performant Security (formerly Really Simple SSL)

Limit Login Attempts Security - Login Security, 2FA, Firewall, Brute Force Prevention

View all Security-and-spam-protection plugins

Frequently Asked Questions

Common questions about Algo Spam User Wiper

No. Matching users are moved to a plugin User Trash first. Permanent delete happens only when you Empty Trash or permanently delete selected trash rows.

Soft-delete removes roles and blocks login. On permanent delete, WordPress wp_delete_user() runs. By default that also removes content owned by the user. On the Trash screen you can choose an administrator to reassign posts to instead.

No. Empty Trash is permanent. Restore users from Trash before emptying if unsure.

Under Block domains, list domains (one per line). When blocking is enabled, new signups using those email domains are rejected on the default WordPress registration form, multisite user signup, and WooCommerce registration (if active). Existing accounts are unchanged — use Find + Trash to clean those up.

No. Algo Spam User Wiper does not phone home. It only stores trash markers, blocklist settings, and optional reassignment settings in your WordPress database. No user data is sent to Algorisys or third-party servers. On uninstall, plugin meta is cleared and soft-trashed users have their roles restored when possible (users are not permanently deleted by uninstall).

In wp-config.php, either keep WP_DEBUG true for local development, or add: define( 'ASUW_ENABLE_TEST_TOOLS', true );