Lumiverse Security Watchdog Lite

No. Lumiverse Security Watchdog Lite is a monitoring, detection, hardening and traffic protection plugin. It helps detect suspicious files, suspicious changes, malware indicators, login attacks and abusive traffic so you can respond quickly. It does not automatically delete or clean infected files.

Lite uses safe fixed defaults designed for normal WordPress and WooCommerce websites. Live Watch tracks up to 3000 files and runs every 30 minutes. Traffic Shield and Login Guard limits are intentionally locked to reduce false positives. Advanced cleanup, quarantine, rollback, Early WAF, IP Control Center and deeper PRO workflows are planned for the PRO version.

The Scanner performs deeper checks for suspicious files, malware indicators, new plugins, new admin users and other security signals. Live Watch is a lightweight file-change monitor that checks file metadata such as path, modified time and size, so it can detect new, modified or deleted files without running a full scan every few minutes.

The normal scanner can run every 6, 12, or 24 hours depending on your settings. Live Watch, when enabled, runs a lightweight metadata check every 30 minutes.

Live Watch is designed to be lightweight. It uses metadata-based checks instead of repeatedly reading every file. In the Lite version, Live Watch tracks up to 3000 files.

Traffic Shield is a smart behavior-based protection layer for WordPress traffic. It watches dynamic request pressure, WooCommerce cart/wishlist actions, XML-RPC requests, dynamic 404s, suspicious query strings and internal abuse scores. It is designed to react to abusive patterns instead of treating every page load, image, CSS or JavaScript file as an attack. It does not use a geolocation or country-blocking database.

No. Traffic Shield helps with abusive WordPress-level traffic and request patterns. Large network-level attacks should still be handled by your hosting provider, server firewall or CDN-level protection.

Traffic Shield Lite uses safe locked defaults and internal abuse scoring to reduce false positives on normal WordPress and WooCommerce websites. Static assets such as CSS, JavaScript, images, fonts, maps and media files are ignored by dynamic traffic counters, and Emergency Mode requires suspicious request pressure instead of raw traffic alone.

Yes. Traffic Shield includes WooCommerce-aware protection for common cart and wishlist abuse patterns, including add-to-cart and add-to-wishlist request floods. It also gives more weight to repeated cart/wishlist actions and suspicious cart/wishlist behavior, while avoiding automatic blocking of normal category-page Add to Cart usage.

Emergency Mode temporarily tightens Traffic Shield limits only when site-wide dynamic traffic pressure is high and suspicious request pressure is also detected. This helps protect busy stores without cutting normal traffic just because many real shoppers are online. In the Lite version, Emergency Mode runs for 30 minutes and uses 60% of the locked per-IP limits. Temporary Traffic Shield blocks expire after 90 minutes.

The Emergency threshold is site-wide, not per IP. In Lite, Emergency Mode can activate when total non-static dynamic requests across the site reach 400 requests in one minute and suspicious request pressure is also detected. Individual IP blocking uses separate per-IP limits.

Lite uses locked safe defaults: 120 dynamic requests per IP per minute, 30 real cart/wishlist actions per IP per minute, 20 404 requests per IP per minute, 90-minute temporary blocks, and a site-wide Emergency threshold of 400 dynamic requests per minute combined with suspicious request pressure. During Emergency Mode, dynamic request limits tighten while cart/wishlist protection stays conservative to avoid blocking real shoppers.

Yes. Traffic Shield Lite includes a Whitelisted IPs field. Add one trusted IP per line for office, developer, monitoring or administrator addresses that should not be temporarily blocked by Traffic Shield.

No. Traffic Shield Lite also uses internal abuse scoring to better separate normal shoppers from abusive request patterns. Normal dynamic page views receive a very low score, while repeated cart/wishlist actions, dynamic 404s, suspicious query strings, missing referrers on cart/wishlist actions and repeated URL hits add more pressure. This means a real customer browsing products is treated differently from a bot repeatedly hitting cart, wishlist, 404 or suspicious URLs.

Login Guard helps protect the WordPress login form from repeated failed login attempts. It can also help protect XML-RPC login attempts and block login attempts using the username "admin".

No. Lite uses fixed safe defaults: 3 failed attempts, a 30-minute failure window and a 90-minute lockout duration.

It blocks login attempts using the username "admin". This helps reduce common brute-force attacks against WordPress sites that still receive automated login attempts for the default admin username.

It helps detect and limit failed login attempts made through XML-RPC, which is commonly targeted by automated attacks.

It prevents administrator password reset requests through the default WordPress password reset flow. This can help reduce password reset abuse against administrator accounts.

No. Email alerts are sent only when suspicious findings or important security events are detected, depending on your settings.

Email delivery depends on your WordPress mail configuration and hosting environment. The plugin records wp_mail success or failure in logs to help you confirm whether WordPress attempted to send the message.

Yes. Lumiverse Security Watchdog Lite is designed to complement other security tools. However, if another plugin also blocks XML-RPC, login attempts or abusive traffic, review your settings to avoid overlapping behavior.

The plugin is designed to be lightweight. Scans run in the background, Live Watch uses metadata-based checks, and Traffic Shield ignores static assets such as images, CSS, JavaScript and fonts.

No. Traffic Shield is behavior-based and does not rely on country blocking or geolocation databases.

No. The plugin monitors and reports suspicious changes. It does not modify WordPress core files as part of normal operation.

No. Scanner findings should be reviewed carefully before deleting anything. Some findings may require manual investigation, especially on websites with custom code or complex plugins.

Review the reported files, compare them with clean backups or original plugin/theme files, remove confirmed malware carefully, update all plugins/themes/core, change administrator passwords, review admin users, and consider a professional cleanup if you are unsure.

No single plugin can guarantee full security. Lumiverse Security Watchdog Lite adds monitoring, hardening, login protection and traffic protection, but you should also keep WordPress updated, use strong passwords, maintain clean backups, secure your hosting account and use server/CDN-level protection when needed.

Visitor Protection Headers add safe browser-level security headers from the Hardening tab. Lite can send X-Content-Type-Options, X-Frame-Options and Referrer-Policy. Permissions-Policy and HSTS are optional and should be tested before enabling. HSTS should only be enabled when the entire site and all subresources work correctly over HTTPS.

It can block selected, obvious automated user agents from Traffic Shield. One switch targets known scraper-style crawler user agents, and the other targets obvious vulnerability scanner/probing tools such as WPScan, sqlmap, Nikto, Nmap, masscan and nuclei. It does not use broad “bot” matching and does not block major search engines.

A PRO version is in development. The Lite plugin includes a contact link where you can ask to be notified when it becomes available.