Linux 软件免费装

Hikosachi Protector

开发者 grooveline
更新时间 2026年11月20日 10:41
PHP版本: 7.0 及以上
WordPress版本: 7.1
版权: GPLv2 or later
版权网址: 版权信息

标签

security firewall brute force ip blocking threat intelligence

下载

3.6.1 3.7.0 3.8.0

详情介绍:

Hikosachi Protector connects your site to Hikosachi, a threat intelligence service operated in Japan. Attacks detected on participating sites (password guessing, vulnerability scans, malicious uploads) are collected, evaluated, and shared back as a blocklist, so every site benefits from what the others have seen. This plugin requires the Hikosachi service. It does not connect to the service until you either enter an API key or choose the free public blocklist on the settings page. See "External services" below for exactly what is sent. Features Free and paid use All code in this plugin is included and active. Paid plans change what the Hikosachi service provides, not what the plugin can do. The Hikosachi service, its member pages, and support are provided in Japanese, and paid plans are billed in Japanese yen.

安装:

  1. Install and activate the plugin from Plugins > Add New.
  2. Open Settings > Hikosachi.
  3. Enter your API key from the Hikosachi member page, or check Use the free public blocklist.
  4. Save. The first blocklist is downloaded right away and then updated every hour.

升级注意事项:

3.6.1 First release on WordPress.org. Sites that already used the free public blocklist keep using it. The site badge is now hidden unless you turn it on. 3.6.0 Sites that already used the free public blocklist keep using it. The site badge is now hidden unless you turn it on.

常见问题:

Does the plugin work without an account?

Yes. Check "Use the free public blocklist" on the settings page. Attack reports, vulnerability alerts, and the Japan-only restriction require an API key.

I use Jetpack or a mobile app that needs XML-RPC.

This plugin refuses all requests to xmlrpc.php. If you rely on XML-RPC, this plugin is not a good fit for your site.

My site is behind Cloudflare or a reverse proxy.

The CF-Connecting-IP header is used only when the request actually comes from a Cloudflare edge server or a private/loopback address. If you use another reverse proxy that sets X-Forwarded-For, add define( 'HIKOSACHI_TRUST_XFF', true ); to wp-config.php. Do not add it otherwise, because the header can be forged.

I locked myself out with the Japan-only restriction.

Add define( 'HIKOSACHI_DISABLE_COUNTRY_LIMIT', true ); to wp-config.php. The restriction stops immediately. The plugin also refuses to enable the restriction if your current IP address would be blocked.

Are logged-in editors blocked?

Requests to the REST API, admin-ajax.php, and admin-post.php from users who can edit posts are not blocked, so automatic saving and integrations keep working. Low-privilege accounts (such as subscribers) are not exempt.

What happens when I delete the plugin?

All settings, the cached blocklist, and scheduled tasks are removed. Deactivating keeps your settings.

更新日志:

3.7.0 3.6.1 3.6.0 3.5.2 3.5.1 3.5.0 3.4.0