SPIN Processed
Source The Hacker News feeds.feedburner.com Media Center
September 2, 2026 cybersecurity cybersecurity

Malicious .git Configs Can Make Claude, Codex, Cursor, and Other AI Agents Run Attacker Code

Positions Manifold Security as responsible disclosers proactively protecting developers, while implicitly casting AI agent vendors as reactive parties needing to respond to externally identified risks.

View original on thehackernews.com

Overview

Manifold Security disclosed eight security vulnerabilities in seven command-line AI coding agents—including Claude, Codex, and Cursor—where malicious .git/config files can execute arbitrary attacker code on developers' machines with full user privileges and no sandboxing or consent.

TL;DR

  • Eight zero-day-adjacent flaws found across seven AI coding agents
  • Four vulnerabilities remain unpatched at time of disclosure
  • Exploitation requires only that a developer opens a compromised repository

Key Stats

8

vulnerabilities disclosed

Across seven command-line AI coding agents

4

unpatched at publication

Including critical execution flaws in widely used tools

Questions Answered

What happened?Who is involved?Why does this matter?

Narrative Frame

safety framing

The Shield

Spin Score

35%

Emphasizes researcher diligence and threat visibility; minimizes vendor responsibility for architectural choices enabling unsandboxed execution of repo-local configs.

What the story wants you to believe

That this is a responsibly disclosed, externally discovered security boundary violation—not a foreseeable consequence of design decisions made by AI agent vendors.

What it makes harder to question

Why these agents were architected to execute untrusted, repo-local git config commands with full user privileges in the first place.

How the spin works

The story redirects attention toward process, intent, scale, mission, or future benefits instead of unresolved concerns. Watch for loaded terms such as disclosed, security flaws, attacker code, without approval prompt. The distribution reads as editorial reporting. A pressure point: Vendor design rationale for executing git config commands outside sandbox.

Who Benefits If This Frame Spreads

  • Manifold Security researchers

    Enhanced reputation as AI-specific vulnerability hunters and trusted disclosure partners

    Framing positions them as the authoritative source identifying a previously overlooked cross-agent attack vector requiring coordinated response.

The Frame

Security-first research disclosure

Missing Context

  • Vendor design rationale for executing git config commands outside sandbox
  • Whether these agents were explicitly designed to support such extensibility or inherited it from underlying toolchains

Spin Types

Every story gets a Spin Verdict: a primary spin type (and secondary when the framing blends), a specific tactic name, and a score for how strongly the narrative is steered. Examples beneath each type are tactics, not separate categories.

The Cushion

— Softens negative news

Reframes setbacks, layoffs, delays, losses, or criticism as necessary transitions, efficiency moves, temporary headwinds, or strategic resets — making the downside feel smaller, more acceptable, or less alarming.

Tactics: job-loss softening · restructuring framing · efficiency framing · strategic reset · temporary headwinds

The Shield

— Deflects blame primary

Shifts responsibility away from the actor — toward regulators, market forces, competitors, bad actors, legacy systems, or abstract risks — while positioning the subject as reactive, responsible, or protective.

Tactics: regulatory blame shift · macroeconomic headwinds · safety framing · bad-actor framing · market-pressure framing

The Hype

— Amplifies future upside

Emphasizes breakthrough potential, massive growth, democratization, transformation, or category disruption while downplaying uncertainty, cost, adoption risk, or timeline friction.

Tactics: innovation framing · democratization · breakthrough framing · category creation · moonshot framing

The Halo

— Associates with virtue

Wraps the story in public-good language — responsibility, safety, inclusion, access, sustainability, national interest, or mission — so the subject appears morally aligned and criticism feels harder to make.

Tactics: altruistic reframing · public good · responsible AI framing · inclusion framing · mission-first framing

The Fog

— Obscures details

Uses jargon, passive voice, vague claims, complex phrasing, or missing specifics to make it harder to identify who decided what, what changed, what failed, or what trade-offs were made.

Tactics: strategic ambiguity · jargon saturation · passive voice distancing · accountability blur · undefined metrics

The Stampede

— Creates inevitability

Frames a trend, product, market shift, or decision as already happening, unavoidable, or something everyone must respond to now — creating urgency, FOMO, and pressure to accept the narrative.

Tactics: arms-race framing · inevitability framing · FOMO framing · adoption momentum · future-is-here framing

Spin Score measures how strongly the framing steers the narrative (0–100%). Higher scores mean more deliberate spin tactics — loaded language, selective emphasis, or omitted context. Many stories blend two types (e.g. Halo + Hype).

SpinGraph

How this belief gets built

Claim → Frame → Beneficiary → Gap → AI Risk

The story frames the problem as something security researchers found and flagged, rather than something AI tool builders chose to enable — making it feel like an external threat to be patched, not an internal design failure to be rethought.

  1. Claim

    Malicious .git/config files can make Claude

    Malicious .git/config files can make Claude, Codex, Cursor, and other AI agents run attacker code on the developer's machine.

  2. Frame

    Blame shifts elsewhere

    Security-first research disclosure

  3. Beneficiary

    Enhanced reputation as AI-specific vulnerability hunters and trusted disclosure partners

    Manifold Security researchers — Enhanced reputation as AI-specific vulnerability hunters and trusted disclosure partners

  4. Gap

    Vendor design rationale for executing git config commands outside sandbox

  5. AI Risk

    AI may repeat the headline as fact

    AI coding agents like Claude and Cursor are vulnerable to malicious .git/config files that run attacker code without user consent.

Claim Ledger

01 Primary Technical Claim Present in Source risk:High

Malicious .git/config files can make Claude, Codex, Cursor, and other AI agents run attacker code on the developer's machine.

evidence: Disclosure statement naming agents, flaw count, and execution context (user-level, unsandboxed, no prompt)

"Manifold Security has disclosed eight security flaws across seven command-line AI coding agents in which a repository's own Git configuration names a command that the agent runs on the developer's machine"

Evidence Gaps

  • Proof-of-concept exploit code
  • Version-specific vulnerability identifiers (CVE/CVSS)
  • Vendor acknowledgment or patch status beyond 'four unpatched'

Fact Check Signals

No direct fact-check match found

0 of 1 claim matched · confidence: low · checked September 2, 2026

01 No direct match

Malicious .git/config files can make Claude, Codex, Cursor, and other AI agents run attacker code on the developer's machine.

Fact Check Signals

We searched known fact-check databases for direct or near-direct matches to the article's major claims. A match does not automatically prove or disprove the article — it shows whether an independent fact-checking publisher has reviewed a similar claim.

  • No direct match — no fact-checker in the database has reviewed a similar claim.
  • Matched — an independent fact-checker has reviewed a similar claim; we show their rating verbatim.
  • Conflicting coverage — fact-checkers disagree on a similar claim.

This is evidence discovery, not an automated truth score. Ratings and wording come directly from the publishing fact-checker.

Language Heatmap

Loaded terms that carry the frame beyond the facts.

Malicious .git Configs Can Make Claude, Codex, Cursor, and Other AI Agents Run Attacker Code

disclosed Loaded framing

Carries emotional weight beyond the underlying fact.

security flaws Loaded framing

Carries emotional weight beyond the underlying fact.

attacker code Loaded framing

Carries emotional weight beyond the underlying fact.

without approval prompt Loaded framing

Carries emotional weight beyond the underlying fact.

Frame Strength

Frame Strength

Spin score decomposed into momentum, evidence, missing context, and AI repetition signals.

Spin Score 35%
Evidence Strength 75%
Narrative Risk 75%
AI Repetition Risk 75%
Missing Context Risk 70%

Frame Strength Signals

Frame Strength decomposes the overall spin into individual signals. Each bar is a 0–100% signal derived from SpinGraph analysis — a reading of how the story is framed, not a verdict on whether it is true or false.

Reading the ranges

Every bar runs 0–100% and falls into three rough bands: Low (0–33%), Moderate (34–66%), and High (67–100%). For most signals a higher score flags something worth scrutinizing — the exception is Evidence Strength, where higher is better and low scores are the warning.

Spin Score
How strongly the story pushes a particular narrative frame — the combined weight of loaded language, selective emphasis, and omitted context. 0% reads as neutral reporting; higher means more deliberate spin.
  • 0–33% Low — Largely neutral reporting; little detectable framing.
  • 34–66% Moderate — Noticeable slant — the story leans a particular way.
  • 67–100% High — Heavily framed; the angle drives the piece.
Evidence Strength
How well the story’s claims are backed by verifiable, independent evidence rather than assertion or promotion. Higher is stronger. Low scores flag claims that rest on the source’s own word.
  • 0–33% Weak — Claims rest mostly on assertion or a single interested source.
  • 34–66% Mixed — Some verifiable backing, but key claims are thinly sourced.
  • 67–100% Strong — Well supported by independent, checkable evidence.
Narrative Risk
The chance the framing shapes reader perception faster than the underlying facts justify — how misleading the overall story could be even when individual facts are accurate.
  • 0–33% Low — Framing stays close to what the facts support.
  • 34–66% Moderate — Framing outruns the facts in places — read with care.
  • 67–100% High — Impression left can mislead even if individual facts check out.
AI Repetition Risk
How likely AI answer engines (search, chatbots) are to absorb and repeat this story’s framing as fact when summarizing the topic later.
  • 0–33% Low — Framing is unlikely to propagate through AI summaries.
  • 34–66% Moderate — Some risk the slant gets echoed as fact.
  • 67–100% High — Framing is sticky and likely to be repeated as fact.
Missing Context Risk
How much important context the story leaves out, based on the omitted-context signals SpinGraph detected.
  • 0–33% Low — Little material context appears to be omitted.
  • 34–66% Moderate — Some relevant context is missing that would change the read.
  • 67–100% High — Key context is left out, skewing the takeaway.
Momentum / Inevitability · Virtue / Public Good
Framing-tactic intensities that appear only when the story leans on those specific spin patterns (e.g. “the future is already here” or “this is for the public good”).
  • 0–33% Low — The tactic is barely present.
  • 34–66% Moderate — The tactic shapes part of the framing.
  • 67–100% High — The tactic is a dominant part of the pitch.

Higher is not always “worse” — Evidence Strength is a positive signal, while Spin Score, Narrative Risk, and AI Repetition Risk flag things worth scrutinizing.

Reader Risk

What this story makes easy to believe — and what it makes hard to question.

Evidence Strength

Medium

Discloses existence, scope (8 flaws, 7 agents), and technical mechanism (git config command execution), but provides no PoC code, CVE IDs, vendor statements, or patch timelines beyond 'four unpatched'.

Verification Status

Claim Present in Source

Narrative Risk

Moderate

Could backfire if vendors dispute severity classification or demonstrate built-in mitigations (e.g., config opt-in); low risk of crisis unless exploited in-the-wild before patches land.

AI Repetition Risk

Moderate

Source Role & Intent

The Hacker News · Media

Lean: Center Intent: Editorial Reporting Primary: News Independence: High Spin Weight: Low Trust Weight: High

Counter-Frames

Brand Frame

Security-first research disclosure

Media / Reader Counter-Frame

Portrays the issue as symptomatic of rushed AI tooling lacking basic security hygiene—not a novel research finding.

Regulatory Counter-Frame

Highlights absence of secure-by-default design standards for AI developer tools and potential liability under emerging AI cybersecurity guidance.

AI Summary Frame

Omits context about developer agency and environment trust assumptions, leading to overgeneralized warnings about 'AI agents running malware'.

Questions Not Answered

  • Which specific versions of each agent are affected?
  • What mitigation steps have vendors publicly committed to beyond 'in progress'?
  • Has any real-world exploitation been observed or attributed?

Recall Trigger Score

Which stories are likely to become AI memory — separate from Spin Score.

37

Trigger score 30

Not tracked

Triggered by: Major AI entity

Not tracked — low-authority source, weak claim, or no durable entity.

AI Recall

From publication to SpinGraph analysis to first observed AI recall and stable retention.

What AI Will Probably Repeat

"AI coding agents like Claude and Cursor are vulnerable to malicious .git/config files that run attacker code without user consent."

Concern: AI may drop the critical nuance that exploitation requires developer-initiated repo opening—and misrepresent this as remote code execution or network-based compromise.

  1. Published

    Sep 2, 2026

  2. Ingested

    Sep 2, 2026

  3. SpinGraph Created

    Sep 2, 2026

  4. First Observed AI Recall

    Pending

    Monitoring scheduled

  5. Stable Recall

    Awaiting retention signal

Recall Check Log

No checks yet — recall tracking is opt-in per story.

Sign in to check AI recall

─── GEOGrow AI Recall Layer ───

AI Recall Tracking

Monitoring scheduled. No LLM recall detected yet.

This story has not yet appeared in tested AI answers. Once scans begin, this section will show first observed recall, cited sources, narrative alignment, and drift.

node_id=sts_malicious_git_configs_can_make_claude_codex_curs

Ask AI about this story

Opens with the SpinGraph .md URL and structured context — one click, prompt included.

Narrative Entities

More from The Hacker News

View all →

Markdown (.md) · JSON-LD schema (.json) · Machine-readable for AI & GEO