SPECIALIZED DEFENSE ENGINES

Hackergate embeds 6 autonomous, zero-allocation defense engines directly into the edge dataplane. Each engine addresses a critical attack vector without incurring central database round-trips or third-party cloud dependencies.

01

Decentralized Threat Gossip Mesh

Sub-50ns Peer Synchronization • HMAC-SHA256 Signed Packets

Traditional fleet security relies on polling a central database (Redis/Postgres), introducing latency spikes and single points of failure. Hackergate implements a peer-to-peer threat gossip protocol running over encrypted HTTP/2 multiplexed streams.

PROTOCOL WORKFLOW:

  1. Local Detection: Node A detects an automated scanner or SQLi payload and records a ban in its local lock-striped shard.
  2. Cryptographic Signing: Node A serializes a ThreatEvent payload (IP, CIDR, reason, TTL) and signs it using a shared 256-bit symmetric key (X-Hackergate-Signature: HMAC-SHA256).
  3. Non-Blocking Broadcast: The signed event is dispatched asynchronously over persistent HTTP/2 sessions to all registered mesh peers in gateway.toml.
  4. Lock-Striped Ingestion: Peer nodes verify the HMAC signature and write the ban into their local 64-shard memory cache in less than 50 nanoseconds, simultaneously queueing a kernel nftables rule.
POST /__hg/gossip HTTP/2.0
X-Hackergate-Signature: sha256=d7a8fbb307d7809469ca9abcb0082e4f8d5651e46d3cdb762d02d0bf37c9e592
Content-Type: application/json
{"event_id":"evt_8831b","origin":"node-ams-01","action":"ban_cidr","target":"198.51.100.0/24","ttl_sec":7200}
02

Stateless Cryptographic PoW Challenges

Zero-Friction Client Verification • Proof-of-Work HMAC SHA-256

Legacy CAPTCHAs alienate legitimate users and degrade conversion rates. Hackergate replaces intrusive puzzles with a lightweight cryptographic Proof-of-Work (PoW) challenge executed transparently in the client's browser background.

CHALLENGE ALGORITHM:

When a client exhibits suspicious entropy (BotScore between 20 and 45), the edge returns a 200 HTTP challenge page with a dynamic nonce:
SHA256(Nonce + Secret + Timestamp + Counter) < TargetDifficulty
Standard desktop and mobile browsers solve this puzzle in ~50 milliseconds. Scripted attack bots, headless crawlers, and DDoS botnets suffer unsustainable CPU exhaustion when attempting to execute millions of challenges. Successful solutions receive a signed __hg_clearance cookie valid for 2 hours.

Challenge Difficulty: 16 (Leading zeros) • Client solve time: ~48ms • Zero backend storage
03

BOLA / IDOR Anomaly Shield

OWASP API Top 10 #1 • 64-Shard Sequential Step Tracking

Broken Object Level Authorization occurs when an authenticated user iterates over entity IDs belonging to other tenants. Because each individual request is structurally valid, traditional WAFs pass the traffic completely unhindered.

DETECTION MATHEMATICS:

Hackergate extracts resource path parameters (e.g. /api/v1/users/:id) and tracks ID transitions per principal session inside a sliding 5-minute ring buffer:
Δ = |ID_current - ID_previous|
If a single session triggers |Δ| ≤ 2 across 5 or more consecutive queries within a 30-second window, or accesses more than 20 unique numeric IDs in 60 seconds, Hackergate classifies the behavior as sequential scraping and enforces a progressive 403 block.

Resource: /api/v1/users/:id • Delta: |100482 - 100481| = 1 • Action: Enforce rate-limit & drop
04

LLM & GenAI Prompt Injection Shield

Inline Payload Sanitization • Jailbreak & Delimiter Protection

Generative AI backends (such as OpenAI-compatible /v1/chat/completions APIs) are vulnerable to prompt injection, system directive overrides, and delimiter boundary escapes that force models to leak confidential training instructions.

INSPECTION VECTORS:

  • Delimiter Escapes: Strips or blocks injection tokens like </system>, <|im_end|>, [INST], and ```system.
  • System Instruction Overrides: Detects heuristic phrasing ("Ignore all previous directives", "DAN mode enabled", "Print your hidden instructions verbatim").
  • Context Flooding: Flags and rejects recursive repeating character arrays designed to exhaust context token windows and trigger denial-of-wallet.
Target: /v1/chat/completions • Action: Drop with 403 and X-LLM-Shield-Violation: delimiter_escape
05

Bot Detection & 2-Phase DNS Crawler Validation

Cloudflare-Parity BotScore (1..99) • Anti-Impersonator Cryptographic DNS

Scrapers frequently spoof Googlebot or Bingbot User-Agents to evade basic rate limits. Hackergate implements a strict 2-phase forward-confirmed reverse DNS (FCrDNS) engine combined with multi-signal heuristics.

2-PHASE VALIDATION FLOW:

  1. Phase 1 (Reverse PTR Query): Queries the client IP address to obtain the authoritative domain (e.g. crawl-66-249-66-1.googlebot.com).
  2. Phase 2 (Forward A/AAAA Query): Queries the resulting hostname against authoritative DNS. If the forward IP does not exactly match the originating client socket IP, the client is flagged as a malicious impersonator and dropped instantly.
Reverse: 66.249.66.1 → googlebot.com • Forward: googlebot.com → 66.249.66.1 [VERIFIED 2-PHASE DNS]
06

Zero-Allocation ML Tree Ensemble Scorer

16-Dimensional Feature Vector • Sub-Microsecond Go Runtime

Traditional signature rules cannot detect novel zero-day attack mutations. Hackergate embeds an ultra-optimized TreeEnsembleScorer that executes pre-compiled decision trees in native Go without calling external Python or CGO processes.

FEATURE VECTOR ATTRIBUTES:

Evaluates 16 extracted telemetry signals on every request: Shannon entropy of path and query, ratio of non-alphanumeric characters, header casing irregularity, standard deviation of request cadence, HTTP method cardinality, and TLS cipher suite order. Operates with exactly 0 heap allocations on the hot path.

Input: 16-element float32 vector • Execution time: 640ns • Allocation: 0 bytes
TEST ENGINES IN LIVE SIMULATOR →