Initial release: F2B Control Center v1.0
Fail2Ban + Nginx Proxy Manager dashboard in a single Docker container. Features: - Auto-ban via badbot, http-errors, npm-probe, manual-bans, recidive jails - Web dashboard: live ban grid, log scanner, per-IP access log viewer - iptables-nft banning (DOCKER-USER + INPUT chains) - Optional Cloudflare WAF banning - Optional AbuseIPDB threat scoring - Two-tier IP management: whitelist (trusted) vs exempt (reviewed) - Auto log-file detection via logwatch (no restart needed for new NPM hosts)
This commit is contained in:
19
fail2ban/filter.d/npm-probe.conf
Normal file
19
fail2ban/filter.d/npm-probe.conf
Normal file
@@ -0,0 +1,19 @@
|
||||
[Definition]
|
||||
|
||||
# ── NPM access log format (current) ──────────────────────────────────────────
|
||||
# [DD/Mon/YYYY:HH:MM:SS +0000] - STATUS STATUS - METHOD SCHEME HOST "PATH"
|
||||
# [Client REAL_IP] [Length N] [Gzip N] [Sent-to IP] "UA" "REFERER"
|
||||
#
|
||||
# fail2ban strips the timestamp before applying failregex, leaving:
|
||||
# " - STATUS STATUS - METHOD SCHEME HOST "PATH" [Client IP] ..."
|
||||
#
|
||||
# Bans IPs probing for well-known vulnerable paths.
|
||||
# Default jail: 3 hits in 30 minutes → 48h ban (very aggressive, intentionally).
|
||||
#
|
||||
# Test against your logs:
|
||||
# fail2ban-regex /nginx-logs/proxy-host-1_access.log /etc/fail2ban/filter.d/npm-probe.conf
|
||||
# ─────────────────────────────────────────────────────────────────────────────
|
||||
|
||||
failregex = - \d+ \d+ - \S+ \S+ \S+ "/(?:\.env[^"]*|\.git[^"]*|wp-login\.php[^"]*|wp-admin[^"]*|xmlrpc\.php[^"]*|phpmyadmin[^"]*|pma/[^"]*|adminer[^"]*|admin\.php[^"]*|config\.php[^"]*|setup\.php[^"]*|install\.php[^"]*|actuator[^"]*|console[^"]*|manager/html[^"]*|invoker/[^"]*|solr/[^"]*|geoserver/[^"]*|boaform/[^"]*|HNAP1[^"]*|cgi-bin/[^"]*|shell\.php[^"]*|cmd\.php[^"]*|eval-stdin\.php[^"]*)[^"]*" \[Client <HOST>\]
|
||||
|
||||
ignoreregex =
|
||||
Reference in New Issue
Block a user