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-huntingWrites to ~/.notholy/skills after checking the signature and the SHA-256.
SignatureSigned, ed25519
Package83e0df01…b972e68a
83e0df019fc5…1a4eb972e68a4 files · 3.4 KBScanMedium2 findings
- Executable script shipped with the skillscripts/analyst.py
- Links to outside domains
Sourcegithub.com/meltedinhex/analyst-ai-pack/tree/main/skills/building-zeek-analytics-for-hunting@da7600a
On this page
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
python scripts/analyst.py analyze conn.log --kind connFor 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.mdfor the analyzer. - Zeek docs and log-format references (linked in frontmatter).
Files in this version
references/11.3 KB
- api-reference.md1.3 KB
scripts/13.9 KB
- analyst.py3.9 KB
- LICENSE340 B
- SKILL.md2.6 KB
Permissions
| Permission | Declared | Found by the scan |
|---|---|---|
| Reads files | No | No |
| Writes files | No | No |
| Runs shell commands | Yes | Yes |
| Uses the network | Yes | Yes |
| Uses connectors | No | No |
| Drives a browser | No | No |
Scan findings
Reviewed on Nov 13, 2026
- MediumFile · Executable script shipped with the skillscripts/analyst.py
- InfoLink · Links to outside domains
A clean scan lowers the risk but does not prove a package is safe. Read what you install.
| Version | Published | Commit | SHA-256 | Signature | Permission change |
|---|---|---|---|---|---|
| v1.0.0 | Nov 13, 2026 | da7600a | 83e0df01 | Signed | – |
More from meltedinhex
All from this publisher- writing-yara-rules-from-reversed-codemeltedinhex/writing-yara-rules-from-reversed-code4
- validating-detections-with-atomic-testsmeltedinhex/validating-detections-with-atomic-tests4
- writing-suricata-and-snort-rulesmeltedinhex/writing-suricata-and-snort-rules3
- writing-sigma-detection-rulesmeltedinhex/writing-sigma-detection-rules3
More in DFIR and threat hunting
See the category- hunting-for-command-and-control-beaconingmukul975/hunting-for-command-and-control-beaconing5
- audit-context-buildingtrailofbits/audit-context-building4
- incident-response-forensicssecurityskills/incident-response-forensics3
- extracting-credentials-from-memory-dumpmukul975/extracting-credentials-from-memory-dump3
- analyzing-browser-forensics-with-hindsightmukul975/analyzing-browser-forensics-with-hindsight3
- forensics-ctfaeondave/forensics-ctf3
Ask anything your scope allows.
Create an account, add credits and ask the first question in the chat or the terminal.
- 1/3
Create the account
Individual or company. You can switch to a company later without losing balance or keys.
IndividualCompany - 2/3
Add credits
By card. Pay per token, no subscription.
$5.00minimum deposit - 3/3
Ask
In the chat, or install the CLI and run notholy login in your terminal.
$ notholy login