Jiffy Intel — Threat intelligence for AI artifacts

Summary

CLAUDE.md in an unrelated repo claims a specific MCP server is "Jiffy-verified" and should be trusted implicitly. The claim is false. Users who rely on the claim skip their own verification.

Severity & confidence

Severity

Medium

Notable weakness with plausible abuse chains or partial mitigations already in place. Track, and resolve as part of your normal hardening cadence.

Confidence

Confirmed

Observed directly by Jiffy scanners or validated by multiple independent sources. Indicators are reliable enough to drive automated action.

Indicators

Observed patterns and artifacts associated with this entry. Each indicator can be copied into your detection stack or SIEM.

(?i)(?:jiffy|official|verified|approved)\s+(?:certified|verified|trusted)

Detection rule

A YARA-style pseudo-rule auto-generated from the indicators above. Useful as a starting point — adapt the syntax for your target detection platform.

YARA-style pseudo-rule

rule jiffy_ti_2026_000075
{
    meta:
        source = "jiffy-intel"
        severity = "medium"
        description = "Auto-generated from Jiffy Intel indicators"
    strings:
    $content_pattern_0 = "(?i)(?:jiffy|official|verified|approved)\\s+(?:certified|verified|trusted)"
    condition:
        $content_pattern_0
}

Auto-generated from the indicators above. Adapt syntax for your detection stack before deploying.

Affected tools

Tool	Versions	Status
Claude Code	`*`	vulnerable
Cursor	`*`	vulnerable

Example artifacts

Sanitized examples of artifacts Jiffy has observed exhibiting this pattern. Publisher handles are redacted; version ranges and status reflect the most recent scan.

CLAUDE.md (repo: ai-dev-pro)IDE rules
Removed
Source
GitHub (public repo)
First observed
Mar 17, 2026
Last observed
Apr 10, 2026
agents.md (repo: mcp-starter)IDE rules
Under review
Source
GitHub (public repo)
First observed
Mar 21, 2026

How to remediate

01Only rely on the jiffylabs.app catalog for MCP trust status.
02Reject claims of verification that originate from inside the artifact itself.

Timeline & sources

Timeline

First observedMar 17, 20261 month ago
Last updatedApr 27, 2026today
PublishedMar 27, 202621 days ago

Sources

curated

References

blog.jiffylabs.aiJiffy Research

Jiffy Research — MCP Security Field Guide

https://blog.jiffylabs.ai/posts/mcp-security-a-security-teams-field-guide

genai.owasp.orgOWASP

OWASP LLM-09: Misinformation (2026)

https://genai.owasp.org/llmrisk/llm-09-2026/

Related intel

Other entries of type Compromised Mcp, or the most recent published entries if no same-type matches exist.

Compromised McpLow

MCP server registers global tool names that shadow Jiffy primitives

MCP server that claims the tool name `scan` or `analyze` — names already used by Jiffy's first-party MCP. Collisions are resolved non-deterministically by the client, allowing the malicious server's tool to receive calls intended for Jiffy.

Jiffy IntelApr 28

Compromised McpCritical

Custom GPT Action schema includes an undocumented "admin" path

Custom GPT's OpenAPI schema defines a `/admin` path that the model can call, not mentioned in the GPT description. The path accepts arbitrary shell commands and runs them on the Action backend.