BOTSCORE 1..99 & CRYPTOGRAPHIC BROWSER PoW

Eliminate malicious automated scrapers, credential stuffers, and scanner botnets without frustrating legitimate users with third-party visual captcha puzzles or invasive advertising cookies.

Multi-Layered Heuristic Classification

Hackergate assigns every inbound client request a real-time BotScore ranging from 1 (unambiguous malicious automated bot) to 99 (confirmed verified human or verified search engine spider).

Score 1 – 15: Definite Bot

Automated headless drivers (Selenium, Puppeteer without stealth plugins), known scanner signatures (Nikto, SQLMap, Nuclei), or fake User-Agents failing FCrDNS verification.

Action: Immediate TCP reset or kernel drop

Score 16 – 35: Suspicious

Clients displaying unusual JA3/JA4 TLS cipher fingerprints, missing standard Sec-CH-UA browser headers, or originating from datacenter VPN/proxy ranges.

Action: Issue Cryptographic Browser PoW

Score 36 – 70: Neutral

Standard web visitors whose fingerprint shows minor anomalies (such as privacy-hardened extensions) but no active attack payload.

Action: Transparent pass-through with monitoring

Score 71 – 99: Verified Human

Confirmed browser sessions exhibiting natural navigational entropy, valid PoW clearance tokens, or verified Googlebot/Bingbot crawler IP addresses.

Action: Unimpeded high-speed dispatch

2-Phase Forward-Confirmed Reverse DNS (FCrDNS)

More than 60% of automated credential stuffers spoof their User-Agent header to claim they are Googlebot or Bingbot to bypass basic firewalls. Hackergate defeats this using strict two-phase cryptographic DNS confirmation:

2-PHASE FCrDNS VERIFICATION FLOW
Client claims User-Agent: "Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)" Client IP: 66.249.66.1 [ Phase 1: Reverse PTR Lookup ] Query: PTR for 1.66.249.66.in-addr.arpa Result: crawl-66-249-66-1.googlebot.com Check: Host suffix matches official domain (.googlebot.com or .google.com) -> VALID [ Phase 2: Forward A Lookup ] Query: A for crawl-66-249-66-1.googlebot.com Result: 66.249.66.1 Check: Resolved IP exactly equals inbound client IP -> CONFIRMED VALID CRAWLER Action: BotScore set to 99 • Cache result for 86,400 seconds [ Spoofed Attack Scenario ] Client IP: 198.51.100.89 claims Googlebot Phase 1: Reverse PTR returns "host-89.generic-vps.com" OR fails Action: Immediate BotScore 1 • Ban IP across mesh • Drop via nftables

Cryptographic Browser Proof-of-Work (PoW) Interstitial

When an unclassified client requests protected endpoints, Hackergate returns an interstitial challenge page without third-party tracking scripts. The browser calculates a cryptographic hash puzzle in a background Web Worker or WebAssembly module.

Frictionless User Experience

No distorted letters, crosswalk image selection, or audio puzzles. The browser resolves the puzzle in approximately 40 to 60 milliseconds with zero user interaction, automatically refreshing into the destination page.

Economic Asymmetry for Attackers

While 50ms of CPU compute is unnoticeable for one human visitor, it imposes an insurmountable financial and hardware barrier on botnets attempting to submit millions of credentials or scrape entire product databases.

HMAC Clearance Token

Upon successful puzzle resolution, Hackergate issues an authenticated HMAC-SHA256 clearance token. Validated tokens allow subsequent requests to skip challenges for the duration of the TTL.

POW CHALLENGE MATHEMATICAL SPECIFICATION
1. Server Issues Challenge: Challenge String = HMAC-SHA256(cluster_secret, client_ip || timestamp || epoch_slot) Target Difficulty = 20 bits (leading 20 bits of hash must be zeros) 2. Client Browser Computes: Find integer "nonce" such that: SHA-256(Challenge String || ":" || nonce) starts with 0x00000... (20 zero bits) 3. Verification on Dataplane: Dataplane computes single SHA-256 hash (<1 microsecond). If hash matches target difficulty and timestamp is within 60 seconds: Return HTTP Cookie: hg_pow_clearance = Base64(HMAC-SHA256(secret, client_ip || expires_at))

Declarative Virtual Host Bot Defense Configuration

Bot defense parameters are tuned inside each virtual host YAML specification:

/etc/hackergate/vhosts.d/app.example.com.yaml [bot_defense]
name: app.example.com domains: - app.example.com bot_defense: enabled: true min_pass_score: 36 # Scores 36-99 allowed without challenge pow_challenge_threshold: 35 # Scores 16-35 receive cryptographic PoW pow_algorithm: sha256 # sha256 | argon2 pow_difficulty_bits: 20 # ~50ms solve time on modern mobile/desktop pow_token_ttl: 7200 # Clearance token validity (2 hours) fcrdns_verification: true # Strictly verify Googlebot/Bingbot IPs allowed_verified_crawlers: - googlebot - bingbot - applebot - duckduckgo backend: driver: proxy target: http://10.0.0.20:3000
← PREV: THREAT GOSSIP & NFTABLESNEXT: BOLA & GENAI LLM SHIELD →