harish282

NiyiGuard hardens WordPress at the application layer: login abuse, accountability, file integrity, browser security headers, optional rate limits, and WooCommerce-specific threats. It complements your host firewall, CDN, or WAF — it does not replace them.
Source code and issue tracker: https://github.com/harish282/securepress
<h4>Why install NiyiGuard?</h4>
<ul>
<li>Self-hosted — security data stays on your server; no NiyiGuard account and no usage telemetry to the author.</li>
<li>One dashboard — enable or disable modules (authentication, audit log, integrity, headers, rate limits, WooCommerce protection).</li>
<li>For store owners — reduce fake checkouts, cart and coupon abuse, registration spam, and Store API abuse when WooCommerce is active.</li>
<li>For developers — protect custom <code>admin-post</code> handlers, forms, and REST routes with the Security SDK (CSRF, rate limits, signed URLs, route guards).</li>
<li>Fully free — no license key, beta trial, or paywalled module in 0.1.0.</li>
</ul>
<h4>What makes it different?</h4>
Many security plugins offer two-factor auth, lockouts, headers, or malware scanning. NiyiGuard does not claim to be the only plugin with those features. It stands out in three ways:
<ol>
<li>Developer SDK — middleware-style helpers for your code paths, not only wp-admin toggles.</li>
<li>WooCommerce abuse pipelines — checkout, cart, registration, and Store API protection in the same package as audit logging and login hardening.</li>
<li>Privacy-first — no license server and no analytics to the author (see Privacy section below).</li>
</ol>
Longer positioning notes and reusable marketing copy: <code>docs/WHY_NIYIGUARD.md</code>.
<h4>Features included (0.1.0)</h4>
<ul>
<li>Authentication hardening — login lockouts (IP and username), TOTP and email two-factor authentication, recovery codes, session tracking with remote revoke, and new-device suspicious-login email alerts.</li>
<li>Security headers — HSTS, Content-Security-Policy, X-Frame-Options, Referrer-Policy, Permissions-Policy, and X-Content-Type-Options (each header can be toggled).</li>
<li>Audit log — logins, plugin changes, role changes, selected option changes, file editor use, and WooCommerce-related actions. Admin list UI, detail view, retention, and scheduled pruning.</li>
<li>File integrity monitoring — WordPress.org core checksum comparison, plugin manifest diff scans, suspicious PHP heuristics, and optional themes/uploads scopes (scheduled scans).</li>
<li>Rate limiting — optional global throttling for front-end, AJAX, wp-login, and REST API traffic (wp-admin dashboard loads excluded by default).</li>
<li>WooCommerce Protection — checkout, cart, registration, and Store API pipelines (velocity limits, honeypots, disposable-email checks, fraud scoring, coupon abuse). Requires WooCommerce.</li>
<li>CSRF middleware and SDK — nonce verification for custom routes, forms, and REST handlers you register.</li>
<li>Signed URLs — time-limited HMAC links for downloads, invites, and sensitive actions.</li>
<li>Login URL disguise — optional custom login path instead of <code>wp-login.php</code> (off by default; test on staging first).</li>
<li>Safe mode — emergency bypass via <code>NIYIGUARD_SAFE_MODE</code> in <code>wp-config.php</code> without changing saved settings.</li>
<li>Health diagnostics — hooks, database tables, and module state on an admin screen.</li>
<li>MU loader helper — optional must-use loader for earlier bootstrap in the request lifecycle.</li>
</ul>
The NiyiGuard → Dashboard includes optional links to leave a WordPress.org review or support development (Ko-fi). Neither is required.
<h4>Developer APIs</h4>
The <code>Security</code> facade provides route guards, CSRF fields, rate limiters, signed URLs, and related helpers. Documented in <code>docs/USAGE.md</code>. Middleware applies to routes you protect — it is not automatic site-wide protection for every WordPress hook. Before production, follow <code>docs/STAGING_TEST_PLAN.md</code>.
<h4>Requirements</h4>
<ul>
<li>WordPress 6.4+</li>
<li>PHP 8.2+</li>
<li>MySQL 5.7+ or MariaDB 10.3+ (standard WordPress database)</li>
</ul>
<h3>Privacy</h3>
NiyiGuard processes security-related data on your WordPress server (IP addresses, user agents, user IDs, audit events, session metadata, and similar fields when features are enabled). It does not sell personal data or include advertising trackers.
Third-party service
<ul>
<li>WordPress.org Core Checksums API (<code>https://api.wordpress.org/core/checksums/1.0/</code>) — used for core file integrity checks (WordPress version and locale only; responses may be cached about 12 hours).</li>
</ul>
Email
Optional security emails (two-factor codes, suspicious-login alerts) use WordPress <code>wp_mail()</code> and your site’s mail configuration.
Optional donations
If you use the dashboard Ko-fi link, payment and any data you provide are handled by Ko-fi under their terms, not by NiyiGuard.
Full details: <code>docs/PRIVACY.md</code> in the plugin folder, and the Privacy section below.

NiyiGuard

Self-hosted WordPress security: 2FA, lockouts, audit log, integrity, headers, rate limits, WooCommerce protection, and SDK. Free.

BaseCloud

BaseCloud Shield is a lightweight yet powerful security plugin that enforces Two-Factor Authentication (2FA) on your WordPress login page. Unlike other bloat-heavy plugins, BaseCloud Shield focuses on reliability and flexibility in OTP delivery.
Key Features:
<ul>
<li>Plug & Play: Works immediately using standard WordPress email delivery.</li>
<li>Multi-Recipient System: Send OTPs to the logging-in user, a manager email, or selected users.</li>
<li>Multi-Channel Delivery: Choose multiple delivery methods simultaneously (Email, SendGrid, WhatsApp, SMS, Webhook).</li>
<li>WhatsApp Integration: Send OTPs directly via WhatsApp using Twilio API.</li>
<li>SMS Integration: Deliver OTPs via SMS using Twilio API.</li>
<li>SendGrid API V3: Native integration for high-deliverability emails.</li>
<li>Webhook Support: Connect to custom webhooks for advanced automation flows.</li>
<li>Secure OTPs: 6-digit one-time passwords that expire automatically.</li>
<li>Browser Trust: “Remember this device” functionality to reduce friction for authorized users.</li>
<li>Advanced Attack Protection (v1.4.2): Credential stuffing detection, progressive delays, username enumeration protection.</li>
</ul>
<h3>External Services</h3>
This plugin may connect to external third-party services depending on your configuration. Below is a detailed explanation of what services are used, what data is sent, and when:
SendGrid Email API (Optional)
If you select “SendGrid API” as your delivery method in the plugin settings, this plugin will send data to SendGrid’s email service to deliver one-time password (OTP) codes.
<ul>
<li>Service: SendGrid by Twilio</li>
<li>What it’s used for: Sending two-factor authentication codes via email with improved deliverability</li>
<li>When data is sent: Every time a user attempts to log in and 2FA is enabled</li>
<li>Data sent:
<ul>
<li>Recipient email address (user’s email or manager email if configured)</li>
<li>Sender email address (configured in plugin settings)</li>
<li>Site name</li>
<li>Username attempting to log in</li>
<li>6-digit one-time password code</li>
<li>Email subject and HTML body</li>
</ul>
</li>
<li>API Endpoint: https://api.sendgrid.com/v3/mail/send</li>
<li>Terms of Service: https://www.twilio.com/legal/tos</li>
<li>Privacy Policy: https://www.twilio.com/legal/privacy</li>
</ul>
Important: You must have a SendGrid account and API key to use this feature. You are responsible for complying with SendGrid’s terms of service and ensuring proper data handling practices.
Twilio API for WhatsApp & SMS (Optional)
If you select “WhatsApp” or “SMS” as delivery methods, the plugin will send data to Twilio’s API to deliver one-time password codes.
<ul>
<li>Service: Twilio</li>
<li>What it’s used for: Sending two-factor authentication codes via WhatsApp and/or SMS</li>
<li>When data is sent: Every time a user attempts to log in and 2FA is enabled with WhatsApp/SMS selected</li>
<li>Data sent:
<ul>
<li>Recipient phone number (from user meta field ‘billing_phone’)</li>
<li>Sender phone number (WhatsApp number or SMS number configured in settings)</li>
<li>Site name</li>
<li>Username attempting to log in</li>
<li>6-digit one-time password code</li>
<li>Message body</li>
</ul>
</li>
<li>API Endpoint: https://api.twilio.com/2010-04-01/Accounts/{AccountSid}/Messages.json</li>
<li>Terms of Service: https://www.twilio.com/legal/tos</li>
<li>Privacy Policy: https://www.twilio.com/legal/privacy</li>
</ul>
Important: You must have a Twilio account with WhatsApp and/or SMS capabilities enabled. Phone numbers must be stored in user meta (field: ‘billing_phone’). You are responsible for complying with Twilio’s terms of service.
Custom Webhook (Optional)
If you select “Webhook” as a delivery method, the plugin will send login notification data to a webhook URL you configure.
<ul>
<li>Service: Custom webhook endpoint (configured by you)</li>
<li>What it’s used for: Sending login notifications to external systems for custom processing</li>
<li>When data is sent: Every time a user attempts to log in and 2FA is enabled</li>
<li>Data sent:
<ul>
<li>Site name</li>
<li>Username attempting to log in</li>
<li>User email address</li>
<li>6-digit one-time password code</li>
<li>Recipient information array</li>
<li>Timestamp of login attempt</li>
</ul>
</li>
<li>Endpoint: User-configured webhook URL</li>
</ul>
Important: When using the webhook option, you are responsible for the security and privacy compliance of the endpoint you configure. Ensure your webhook endpoint uses HTTPS and follows proper data protection practices.
Standard WordPress Email (Default)
By default, this plugin uses WordPress’s built-in <code>wp_mail()</code> function, which does not involve any external services unless your WordPress installation is configured to use a third-party SMTP service.

BaseCloud Shield

Enterprise-grade Two-Factor Authentication (2FA) with support for Email, SendGrid API, Webhooks, WhatsApp, and SMS delivery.

NiyiGuard vs BaseCloud Shield