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/establishing-telemetry-baselinesNetwork, wireless and telecom

establishing-telemetry-baselines

⁨Establishes behavioral baselines from historical telemetry (process, network, or⁩

v1.0.03 installs+3 in 7 days24 StarsApache-2.0synced 10 hours ago

Install

No NotHoly CLI yet? Install it first.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install meltedinhex/establishing-telemetry-baselines

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

SignatureSigned, ed25519
tor3A/5L2x…8nEwHiAg==The CLI checks the SHA-256 and the signature before it writes a file.
Packagea3c1ce1d…b21dfcf4
a3c1ce1de3b7…043fb21dfcf44 files · ⁦3.0 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/establishing-telemetry-baselines@da7600a

When to Use

  • You want to hunt for rare or first-seen behavior (uncommon process names, parent/child pairs, destinations) by comparing current activity to a historical baseline.
  • You are reducing noise by establishing what "normal" looks like before alerting on outliers.

Do not use a baseline built from a compromised period as "normal" — seed it from a known-good window. This skill computes statistics from telemetry and executes nothing.

Prerequisites

  • Historical telemetry (CSV/JSON) with a categorical field to baseline (e.g., process name, parent-child pair, destination host).

Workflow

Step 1: Build the baseline

bash
python scripts/analyst.py baseline history.csv --field Image

Computes per-value counts, frequency (stacked-rank), and the set of values seen, saved as a JSON baseline.

Step 2: Score new activity against the baseline

bash
python scripts/analyst.py compare new.csv --field Image --baseline baseline.json

Flags values not present in the baseline (first-seen) and values below a rarity threshold.

Step 3: Triage outliers

Investigate first-seen and rare values; many will be benign-but-new — corroborate with context.

Step 4: Maintain

Refresh the baseline on a rolling known-good window to avoid drift.

Validation

  • The baseline captures counts and the value set from the historical window.
  • First-seen values in new data are correctly identified as absent from the baseline.
  • Rarity thresholds are explicit and tunable.

Pitfalls

  • Baselining a compromised window, normalizing malicious activity.
  • Too-short baseline windows making common items look rare.
  • High-cardinality fields (full command lines) needing normalization before baselining.

References

  • See references/api-reference.md for the baseliner.
  • The ThreatHunting Project and ATT&CK hunting resources (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, 2026da7600aa3c1ce1dSigned–

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