Supply ChainPublished Mar 5, 2026

.cursorrules contains outdated model pins that steer to deprecated GPTs

LowAARM tierConfirmed
Seen73times across10customers
jiffy-ti-2026-000071

Summary

.cursorrules hardcodes "always use gpt-3.5-turbo" for code reviews. The pinned older model is prone to missing modern vulnerability patterns. Not a direct exploit — a steering attack against downstream safety.

Severity & confidence

Severity
Low

Low

Hygiene-grade issue with limited direct impact. Fix opportunistically; monitor in case context changes (new exploit, new dependency, etc.).

Confidence
Confirmed

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)model\s*:\s*"?gpt-3\.5|claude-instant

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_000071
{
    meta:
        source = "jiffy-intel"
        severity = "low"
        description = "Auto-generated from Jiffy Intel indicators"
    strings:
    $content_pattern_0 = "(?i)model\\s*:\\s*\"?gpt-3\\.5|claude-instant"
    condition:
        $content_pattern_0
}

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

Affected tools

ToolVersionsStatus
Cursor*vulnerable
Claude Code*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.

  • .cursorrules (repo: legacy-saas)IDE rules
    Still live
    Source
    GitHub (public repo)
    First observed
    Feb 21, 2026
  • .cursorrules (repo: old-ruby-app)IDE rules
    Still live
    Source
    GitHub (public repo)
    First observed
    Feb 25, 2026

    Prior to agent maturity; still shipping.

How to remediate

  1. 01Keep model pins current.
  2. 02Review legacy rule files when inherited from old templates.

Timeline & sources

Timeline

  1. First observedFeb 21, 20261 month ago
  2. Last updatedApr 18, 2026today
  3. PublishedMar 5, 20261 month ago

Sources

scanner

References

Scan for patterns like this

Point Jiffy at your GitHub org, IDE config, or a single artifact. Get a scored report in under a minute.

Start a free scan