PHP code example of keepsuit / laravel-threat-blocker
1. Go to this page and download the library: Download keepsuit/laravel-threat-blocker library. Choose the download type require.
2. Extract the ZIP file and open the index.php.
3. Add this code to the index.php.
<?php
require_once('vendor/autoload.php');
/* Start to develop here. Best regards https://php-download.com/ */
keepsuit / laravel-threat-blocker example snippets
use Keepsuit\ThreatBlocker\Middleware\ProtectAgainstThreats;
Route::post('contact', [ContactController::class, 'submit'])->middleware(ProtectAgainstThreats::class);
return [
/**
* This option enables or disables the Threat Blocker protection.
*/
'enabled' => env('THREAT_BLOCKER_ENABLED', true),
/**
* HTTP methods checked by the detectors (names or HttpMethod cases), '*' means any method.
* Each detector can override it with its own 'methods' option.
* Detectors that inspect the request body (FormHoneypotDetector, AiSpamDetector,
* EmailReputationDetector) only support POST, PUT and PATCH, other methods are ignored.
*/
'methods' => ['POST'],
/**
* Storage driver to use for caching detectors data.
*/
'storage_driver' => env('THREAT_BLOCKER_STORAGE_DRIVER', 'cache'),
'storage' => [
'cache' => [
'store' => env('THREAT_BLOCKER_CACHE_STORE', env('CACHE_STORE', env('CACHE_DRIVER', 'file'))),
'prefix' => env('THREAT_BLOCKER_CACHE_PREFIX', 'threat_blocker'),
],
],
/*
* The responder class that will be used to respond to detected threats.
* You can create your own responder by implementing the Keepsuit\ThreatBlocker\Contracts\ThreatResponder interface.
*/
'responder' => \Keepsuit\ThreatBlocker\Responders\BlankPageResponder::class,
/**
* The following list of "detectors" will be used to identify threats.
* You can enable or disable each detector individually and configure their settings.
*/
'detectors' => [
/**
* Block requests coming from IPs listed in the AbuseIPDB database.
*/
\Keepsuit\ThreatBlocker\Detectors\AbuseIpDetector::class => [
'enabled' => env('THREAT_BLOCKER_ABUSE_IP_DETECTOR_ENABLED', true),
// Source url for AbuseIP data, it can be a custom url or one of the predefined sources (provided by https://github.com/borestad/blocklist-abuseipdb)
'source' => \Keepsuit\ThreatBlocker\Enums\AbuseIpSource::Days60->url(),
'blacklist' => [
// These IPs will always be blocked by the AbuseIpDetector
],
'whitelist' => [
// These IPs will never be blocked by the AbuseIpDetector
'127.0.0.1',
],
],
/**
* Block registrations using disposable or undeliverable email domains.
*/
\Keepsuit\ThreatBlocker\Detectors\EmailReputationDetector::class => [
'enabled' => env('THREAT_BLOCKER_EMAIL_REPUTATION_DETECTOR_ENABLED', true),
// Source URL for the disposable email domain list, one domain per line.
'source' => \Keepsuit\ThreatBlocker\Enums\EmailReputationSource::DisposableEmailDomains->url(),
// Empty fields disable this detector. `email` also matches nested terminal fields;
// use patterns such as `contacts.*.email` for a specific nested path.
'fields' => ['email'],
'check_mx' => true,
'mx_cache_ttl' => 86400,
'blacklist' => [],
'whitelist' => [],
],
/**
* Block POST requests that look like automated form submissions based on their headers.
*/
\Keepsuit\ThreatBlocker\Detectors\BotSignatureDetector::class => [
'enabled' => env('THREAT_BLOCKER_BOT_SIGNATURE_DETECTOR_ENABLED', true),
'rules' => [
'missing_user_agent' => true,
'known_bot_user_agents' => true,
'missing_accept_language' => false,
'invalid_referer' => false,
],
// Replace the defaults, or use array_merge() to extend them.
'user_agent_patterns' => \Keepsuit\ThreatBlocker\Detectors\BotSignatureDetector::DEFAULT_USER_AGENT_PATTERNS,
],
/**
* Block requests that contain form submissions with honeypot fields filled out.
* This detector
use Illuminate\Http\Request;
use Keepsuit\ThreatBlocker\Contracts\ThreatResponder;
class RedirectResponder implements ThreatResponder
{
public function respond(Request $request, \Closure $next): mixed
{
return redirect()->back()->withErrors('Your request could not be processed.');
}
}