Agentic Detection Lookups

io.github.detection-forgePublished by GitHub account detection-forgev0.1.0Updated Oct 24, 2026

LOLBAS, GTFOBins, and process parent-child lookups for detection engineering agents.

The publisher's own server: agentic.no

VerifiedSTDIODesktop onlySecurity & MonitoringData & Analytics

Overview

AI-generated overview

Lets an assistant look up LOLBAS and GTFOBins binaries and check process parent-child relationships for detection engineering.

What you can do
Provides read-only lookups over bundled CSV data: LOLBAS Windows binaries, GTFOBins Linux binaries, and expected or suspicious process parent-child baselines. Tools include detection_lookup_binary for risk, categories and MITRE ATT&CK IDs, detection_check_parent_child for triage guidance, plus category, technique and free-text search tools and a listing of available lookup files. The same CSV files can be uploaded to SIEM platforms for enrichment.
When to use it
Useful for detection engineering, threat hunting and SOC triage work where an assistant needs quick context on whether a binary is commonly abused or whether a process parent-child pair is suspicious. Also relevant when preparing SIEM lookup tables for CrowdStrike, Splunk, Elastic or Sentinel.
Requirements
Runs locally over stdio as a Python package: Python 3.10 or newer, a virtual environment, and installation from the project source. The README also mentions VS Code with GitHub Copilot for MCP integration. No accounts, API keys or network access are declared.
Before you install
The data is reference material for triage, not a verdict; risk scores and parent-child baselines are curated and may lag real environments. The server is read-only and asks for no credentials, but it is desktop-only and must be pointed at a local checkout path.

Installation

In SourceWeft

  1. Open Agentic Detection Lookups in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Agentic Detection Lookups

Machine-readable detection lookups for SIEM enrichment and AI agents. MCP-native.

Stop regex-matching 200+ binaries. Enrich in one match() call.
Feed it to your SIEM, your SOAR, your agent, or your LLM.

What is this?

A collection of structured CSV lookup files purpose-built for:

  • SIEM enrichment — one match()/lookup/join replaces entire rule categories
  • AI agent tooling — MCP server included, agents query detection context in real-time
  • Detection automation — consistent schema, CI-updated, deploy-ready

Lookup Files

FileEntriesOSDescription
lolbas_binaries.csv234WindowsLiving Off The Land Binaries and Scripts — risk-scored, categorized, MITRE-mapped
gtfobins.csv477LinuxGTFOBins Unix binaries — shell escape, priv-esc, file ops, MITRE-mapped
parent_child_baselines.csv98BothExpected/suspicious process parent→child relationships for Windows and Linux

Schema Contract

Every lookup file follows:

  1. First column = match key (the field you join on)
  2. Always includes risk or risk_if_unexpected column
  3. Always includes MITRE ATT&CK technique mapping
  4. No nested data — flat columns, pipe-delimited for multi-value
  5. UTF-8, no BOM, Unix line endings, header row always present

Quick Start

SIEM (copy-paste)

CrowdStrike NG-SIEM:

cql
#event_simpleName=ProcessRollup2| binary := lower(FileName)| match(file="lolbas_binaries.csv", field=binary, column=filename, include=[categories, mitre_ids, risk])| risk="high"

Splunk:

spl
index=crowdstrike event_simpleName=ProcessRollup2| rex field=FileName "(?<binary>[^\\\\]+)$"| lookup lolbas_binaries.csv filename AS binary OUTPUT categories mitre_ids risk| where risk="high"

Elastic (ES|QL):

esql
FROM logs-endpoint.events.process-*| WHERE event.action == "start"| ENRICH lolbas-policy ON process.name = filename WITH categories, risk| WHERE risk == "high"

Microsoft Sentinel:

kql
DeviceProcessEvents| extend binary = tolower(FileName)| join kind=inner (_GetWatchlist('lolbas_binaries')) on $left.binary == $right.filename| where risk == "high"

See queries/ for full query libraries per platform.

MCP Server (AI agents)

json
{  "servers": {    "detection-lookups": {      "type": "stdio",      "command": "python",      "args": ["-m", "mcp_server"],      "cwd": "/path/to/agentic-detection-lookups"    }  }}

Then your agent can:

→ detection_lookup_binary("certutil.exe")← {source: "lolbas", risk: "medium", categories: ["Download"], mitre_ids: ["T1105"]}
→ detection_lookup_binary("python")← {source: "gtfobins", risk: "high", categories: ["shell", "reverse-shell", ...], mitre_ids: ["T1059"]}
→ detection_check_parent_child("winword.exe", "cmd.exe")← {expected: false, risk_if_unexpected: "critical", mitre_id: "T1204.002"}

MCP Tools

ToolInputOutput
detection_lookup_binaryfilenameRisk, categories, MITRE IDs, source (lolbas/gtfobins)
detection_check_parent_childparent, child, os_filterExpected/suspicious, risk level, triage guidance
detection_list_by_categorycategory, limit, offsetPaginated binaries in that abuse category (cross-platform)
detection_list_by_mitretechnique_id, limit, offsetPaginated binaries mapped to that technique (cross-platform)
detection_searchquery, limitMatches across all lookup data with total/has_more
detection_list_lookups—All files with row counts and columns

Data Sources

LookupSourceUpdate Frequency
LOLBAS binariesLOLBAS ProjectWeekly (automated)

Installation

Prerequisites

  • Python 3.10+
  • VS Code with GitHub Copilot (for MCP integration)

Install

bash
git clone https://github.com/detection-forge/agentic-detection-lookups.gitcd agentic-detection-lookupspython -m venv .venv# Windows:.venv\Scripts\activate# Linux/macOS:source .venv/bin/activatepip install -e .

Configure MCP Client (VS Code)

Add to your VS Code User settings (Ctrl+Shift+P → "Preferences: Open User Settings (JSON)") or ~/.vscode/mcp.json:

json
{  "servers": {    "detection-lookups": {      "type": "stdio",      "command": "/absolute/path/to/.venv/bin/python",      "args": ["-m", "mcp_server"],      "cwd": "/absolute/path/to/agentic-detection-lookups"    }  }}

Windows example:

json
{  "servers": {    "detection-lookups": {      "type": "stdio",      "command": "C:\\Code\\.venv\\Scripts\\python.exe",      "args": ["-m", "mcp_server"],      "cwd": "C:\\Code\\agentic-detection-lookups"    }  }}

Reload VS Code: Ctrl+Shift+P → "Reload Window"

Verify

In Copilot Chat (Agent mode):

Is certutil.exe a LOLBAS binary?

✅ Returns risk, categories, and MITRE mappings = working!

Run standalone (CLI)

bash
detection-lookups

This starts the MCP server on stdio transport (useful for piping JSON-RPC or connecting other MCP clients).

Upload to your SIEM

  • CrowdStrike NG-SIEM: Upload via API or UI (Settings → Lookup Files)
  • Splunk: Settings → Lookups → Lookup table files → Add new
  • Elastic: Create enrich index + ingest pipeline
  • Sentinel: Configuration → Watchlist → Add new

Project Structure

agentic-detection-lookups/├── lookups/                    # The data (CSV files)│   ├── lolbas_binaries.csv│   ├── gtfobins.csv│   └── parent_child_baselines.csv├── queries/                    # Copy-paste detection queries│   ├── crowdstrike_ngsiem.md│   ├── splunk.md│   ├── elastic.md│   └── microsoft_sentinel.md├── mcp_server/                 # MCP server for AI agents│   ├── server.py│   └── __init__.py├── scripts/                    # Update/maintenance scripts├── LICENSE                     # Apache 2.0├── NOTICE└── pyproject.toml

Contributing

PRs welcome. See CONTRIBUTING.md for guidelines.

To add a new lookup file:

  1. Follow the schema contract (match key first, include risk + MITRE columns)
  2. Include at least one query example per SIEM platform
  3. Add a tool to the MCP server

License

Apache 2.0 — See LICENSE and NOTICE.


Built by Gene Kazimiarovich | Part of Detection Forge

Source: README.md at commit 2dfb659

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Agentic integrations