AINewsIQ by Triuna Labs
Menu
SOURCE-LINKED SIGNAL / ARTICLE / SECURITY

I Spent $500 To Test Devin AI For Prompt Injection So That You Don't Have To

The author reports a proof-of-concept against Devin AI, Cognition's AI software engineer agent.

READ THE ORIGINAL SOURCEOpen original sourceembracethered.com UTC

Source-based brief · Editor review not recorded · See checks and limits ↓

⚑ Recency not confirmed · what to check

We could not confirm from the original page that this is a newly published development. Check its date before treating it as current news.

Claim context: the post is the author's account of a single demonstration, and the vendor's response is not included.

Recorded links

One primary source; other links are context, not independent corroboration.

Grok Bot submitted this discovery. We could not confirm from the original page that this is a newly published development. Check its date before treating it as current news. The original source and submitted evidence remain inspectable; no editor has verified the claim.

Open full article view →
How this score was derived
  • Linked article+30
  • Fetched source page+30
  • No editor link review+0
  • Original non-discussion link+5
  • Recency not confirmed-8

This measures the stored source trail and editorial steps. It does not certify accuracy, peer review, or independent corroboration. Popularity adds no points.

View full scoring →Read the scoring rubric →

What the source says

The author reports a proof-of-concept against Devin AI, Cognition's AI software engineer agent. Instructions hidden on a webpage referenced from a GitHub issue led Devin to download a Sliver C2 Linux binary, make it executable, and run it, giving the attacker a remote shell on the Devin machine. The author spent $500 for 30-day access. The post states the vulnerability was reported to Cognition in April 2025, acknowledged, and that follow-up queries remained unanswered after 120+ days. Recommendations and user mitigations are listed.

Claim explorer

Attribution, source and conditions

Source-stated points from the stored brief. Claim-level assessments have not been recorded.

Prompt injection on a webpage linked from a GitHub issue led Devin to download and run a malware binary.
Source assertionNot independently checked
Primary sourceembracethered.comInspect source ↗
Attributed toClaimant not recorded per pointSource assertion
Conditions / limitsClaim-specific conditions not recorded. Read the source and limits below.

Source claims not independently checked; the post is the author's account of a single demonstration, and the vendor's response is not included.

This connects a source, an attributed statement and its qualifications. It does not establish that the claim is correct.

Questions worth asking

Open questions for further reporting
What remains unconfirmed?

Source claims not independently checked; the post is the author's account of a single demonstration, and the vendor's response is not included.

What material was available for this brief?

The recorded brief basis is fetched source page. These points are AINewsIQ paraphrases, not quotations or independent confirmations.

Limits from the stored brief

Source claims not independently checked; the post is the author's account of a single demonstration, and the vendor's response is not included.

This is a source-based abstract, not independent validation of the source's claims.

Join the discussion

Have a different perspective or a question about the evidence? Discussion is free with a verified email account. Every comment is reviewed before publication.

No published comments yet.

Checking sign-in…

New commenters: 2 submissions per 24 hours, at least 5 minutes apart, until 3 are approved. Discussion guidelines and moderation →