Skip to content
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
meltedinhex/building-zeek-analytics-for-huntingDFIR and threat hunting

building-zeek-analytics-for-hunting

⁨Builds Zeek-based network hunting analytics by writing scripts and analyzing Zeek logs⁩

v1.0.02 installs+2 in 7 days24 StarsApache-2.0synced 11 hours ago

Install

No NotHoly CLI yet? Install it first.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install meltedinhex/building-zeek-analytics-for-hunting

Writes to ⁦~/.notholy/skills⁩ after checking the signature and the SHA-256.

SignatureSigned, ed25519
TeMJw3gRx7…k7EzhBBg==The CLI checks the SHA-256 and the signature before it writes a file.
Package83e0df01…b972e68a
83e0df019fc5…1a4eb972e68a4 files · ⁦3.4 KB⁩
ScanMedium2 findings
  • Executable script shipped with the skillscripts/analyst.py
  • Links to outside domains
See the full scan
Sourcegithub.com/meltedinhex/analyst-ai-pack/tree/main/skills/building-zeek-analytics-for-hunting@da7600a

When to Use

  • You have Zeek logs (conn.log, dns.log, http.log, ssl.log, files.log) and want to build hunting analytics: long-lived connections, rare JA3 fingerprints, suspicious file downloads, and beaconing.
  • You want repeatable detections expressed as Zeek scripts or log-analysis queries.

Do not use Zeek to actively probe hosts — it is passive analysis of captured/sensor traffic.

Prerequisites

  • Zeek logs in TSV or JSON (or a running Zeek sensor). The script analyzes exported logs.

Workflow

Step 1: Analyze a Zeek log for anomalies

bash
python scripts/analyst.py analyze conn.log --kind conn

For conn, surfaces long-duration and high-byte connections; for ssl, counts JA3 rarity; for http, flags executable/script downloads and rare user-agents; for dns, flags long/high-entropy queries.

Step 2: Express the logic as a Zeek script (optional)

Translate a confirmed pattern into a Zeek script using the appropriate event (connection_state_remove, ssl_established, http_reply).

Step 3: Confirm

Corroborate anomalies with destination reputation and other logs (pivot by uid).

Step 4: Operationalize

Stage the Zeek script or scheduled log query as a durable detection.

Validation

  • The analyzer parses both TSV (#fields) and JSON Zeek logs.
  • Surfaced anomalies match the chosen log kind's fields.
  • JA3 rarity and long-connection logic are computed correctly.

Pitfalls

  • TSV header (#fields) parsing — column order varies by deployment.
  • Backups/updates producing benign long/large connections.
  • JA3 collisions across legitimate clients.

References

  • See references/api-reference.md for the analyzer.
  • Zeek docs and log-format references (linked in frontmatter).

Files in this version

Permissions

PermissionDeclaredFound by the scan
Reads filesNoNo
Writes filesNoNo
Runs shell commandsYesYes
Uses the networkYesYes
Uses connectorsNoNo
Drives a browserNoNo

Scan findings

Reviewed on Nov 13, 2026

  1. MediumFile · Executable script shipped with the skillscripts/analyst.py
  2. InfoLink · Links to outside domains

A clean scan lowers the risk but does not prove a package is safe. Read what you install.

VersionPublishedCommitSHA-256SignaturePermission change
v1.0.0Nov 13, 2026da7600a83e0df01Signed–

Ask anything your scope allows.

Create an account, add credits and ask the first question in the chat or the terminal.

  1. 1/3

    Create the account

    Individual or company. You can switch to a company later without losing balance or keys.

    IndividualCompany
  2. 2/3

    Add credits

    By card. Pay per token, no subscription.

    $5.00minimum deposit
  3. 3/3

    Ask

    In the chat, or install the CLI and run notholy login in your terminal.

    $ notholy login