← Back to all free security checks
OPEN SOURCE SPOTLIGHT — depalmar/ai-dfir-toolkit · APACHE 2.0

AI DFIR detection pack: your SIEM watches malware — does it watch AI attacks? — a cybersecurity news detection check

The AI DFIR detection pack is a free set of 161 vendor-neutral detection rules across 9 AI attack classes — prompt injection, MCP tool poisoning, poisoned models, RAG attacks. This cybersecurity news check finds which ones your stack is blind to.

Key figure: The global average cost of a data breach was $4.44 million in 2025 (IBM, Cost of a Data Breach Report 2025).

— Ingenious AI security check.

Does your SIEM see AI attacks in this cybersecurity news era?

If you cannot name a detection for prompt injection, MCP config tampering, or a poisoned model file in your environment, your AI footprint is flying blind. These attacks do not look like normal intrusions. The check below maps the pack's 161 rules to your stack and shows the gaps in 60 seconds.

What is AI DFIR?

Digital forensics and incident response for AI systems — detecting and investigating attacks that target models, prompts, agents, and the AI supply chain instead of traditional malware.

Prompt injection, MCP tool poisoning, poisoned AI models, RAG attacks, agents used as command-and-control — these don't look like "normal" intrusions, and most detection stacks are blind to them. The AI DFIR Toolkit answers with 161 free, vendor-neutral detection signatures (Sigma, YARA, Suricata) across 9 AI attack classes. Five questions to check whether your stack can see any of it.

Short answer: if you can't name a detection for prompt injection, MCP config tampering, or a poisoned model file in your environment, your AI footprint is flying blind. The pack's rules deploy anywhere via open formats — no vendor lock-in — and its artifact catalog tells responders exactly where AI agents leave forensic traces. Check your coverage below.

The 60-second AI-Attack Detection Check

Answer for the environment you defend.

Share your result:

What the pack actually contains (verified from the repo)

Attack classSignaturesExamples
LLM prompt injection10Jailbreaks, indirect injection, system-prompt extraction
MCP attacks14Tool poisoning, config tampering, rug pulls
Model supply chain23Pickle exploits, HuggingFace implants, dependency confusion
AI infrastructure31ShadowRay, Triton, MLflow, GPU abuse
Copilot / assistant abuse19M365 Copilot, GitHub Copilot, Claude, Cursor misuse
RAG / vector DB17Vector-DB exposure, RAG poisoning
Runtime AI malware16Malware calling LLM APIs at runtime
Agentic orchestration12Agent-as-operator, AI service API as C2
Agent memory forensics5Memory as persistence, context poisoning
Endpoint (cross-tool)14Agent behaviour on host + osquery inventory pack

Sources: depalmar/ai-dfir-toolkit (GitHub) · browseable artifact catalog

Three things to know before you deploy it

1. Rules err toward signal — tune them anyway

Every rule ships with documented false-positive scenarios and severity levels; the recommended rollout is 7 days in a test index, triage, tune, then promote high+ to production.

2. Keyword rules need the right field mapping

On Elastic, matched content fields must be analyzed text, not keyword — a keyword mapping matches case-sensitively and silently misses capitalized attacker input.

3. Detection is half the battle — collection is the other

The catalog's triage scripts (PowerShell/bash) and Velociraptor/KAPE commands answer the "which hosts have this" question Sigma rules can't. Pair detection with the collection plan.

FROM INGENIOUS AI
Agent Flight Recorder is SHA-256 hash-chained agent logging — tamper-evident forensic evidence of everything your AI agents did, ready for incident response.
All 11 platforms: DisclosureGuard  ·  ModelMinder  ·  TermsWatch  ·  Vibe-Code Audit  ·  Rogue-Agent Defense  ·  BreachHunter  ·  ChatBreaker  ·  Agent Flight Recorder  ·  Agent Auth Gateway  ·  DomainGuard  ·  ContentCraft AI
Our platforms are being upgraded and return November 1 — get early access now:
Get early access on WhatsApp →
Share this check: XLinkedInReddit

Frequently asked questions

FAQ

What is the AI DFIR Toolkit?

A public, Apache-2.0-licensed collection (depalmar/ai-dfir-toolkit on GitHub) of 161 vendor-neutral detection signatures — Sigma, YARA, and Suricata rules — covering nine AI attack classes: LLM prompt injection, MCP attacks, model supply-chain compromise, AI infrastructure abuse, Copilot/assistant abuse, RAG and vector-database attacks, runtime AI malware, agentic orchestration, and agent memory forensics.

Which AI attack classes does the pack cover?

Prompt injection and jailbreaks, MCP tool poisoning and config tampering, poisoned pickle models and HuggingFace supply-chain attacks, ShadowRay-style AI infrastructure compromise, M365/GitHub Copilot abuse, vector-database exposure and RAG poisoning, malware that calls LLM APIs at runtime, AI services used as command-and-control, and memory/context poisoning as persistence.

How do you deploy vendor-neutral Sigma rules?

Convert them to your SIEM's query language with pySigma backends (e.g. sigma-cli to Lucene for Elastic/Kibana).

Related checks